Download websites that use SiteGuard WP Plugin

About SiteGuard WP Plugin

A security plugin succeeds partly by making a site look boring. Renaming the login path, adding a challenge to the form, refusing suspicious uploads, hiding the version string: the work is subtractive, and the better it is done, the less remains for an outside observer to notice. SiteGuard WP Plugin belongs to that awkward class of Security software, which makes counting installs harder than counting a plugin that wants to be seen.

The plugin hardens WordPress installations against the traffic every such install attracts soon after it appears online: automated login attempts against a login path that is identical on millions of sites, probes for known plugin vulnerabilities, upload attempts aimed at the editor. Our catalogue records the publisher as EG Secure Solutions, and the code ships under GPL v2, so it can be taken and modified freely and no purchase record exists anywhere to count against.

As of October 2026 we see the plugin on 18 sites, and the number understates the install base more than most entries do. Detection depends on artefacts the plugin has no need to expose: a renamed login route with a recognisable pattern, a challenge image path, an asset served from the standard plugin directory. An administrator who follows the hardening advice thoroughly removes several of those artefacts, which biases our visible population towards the least carefully configured deployments and away from the ones doing the job properly.

Written in PHP and available since 2013, the plugin nonetheless carries an unusual amount of information about the site behind it. A site running a dedicated hardening layer is typically self hosted rather than on a managed platform, is maintained by someone who has either been attacked already or expects to be, and often belongs to a portfolio where an agency repeats the same stack across every client it manages. Clusters of identical plugin sets across otherwise unrelated domains usually point back to a single maintainer.

For a researcher the list answers questions a lookup cannot reach. How much of a market runs any hardening layer at all, which hosting networks the deployments concentrate in, whether a plugin's install base is expanding or being replaced by a competitor, and which unpatched neighbours sit on the same infrastructure. Security vendors sizing a market, hosts planning a bundled offering and researchers studying content platform hygiene all need the set of domains rather than a verdict on one of them, and the export is where the set lives.