Guardr

Guardr connects this site to your Guardr account and shows its security grade, uptime percentage and response time right in wp-admin.

Guardr scans externally, from Cloudflare’s edge network, not from an agent installed on your server. There is nothing running on your site beyond this plugin’s own wp-admin screens: no background agent, no code injected into your theme or front end, no access to your server’s file system or database beyond the two settings this plugin itself stores.

If a scan finds your site down, Guardr confirms the outage across 3 separate global regions before treating it as down, to avoid false positives from a single location’s network issue.

This plugin covers one site. If you manage more than one site with Guardr, the full fleet view, including every site on your account, lives on the Guardr dashboard at guardr.io/dashboard – you do not need to install this plugin on every site to get value from Guardr.

What this plugin does not do (yet)

• No public “Secured by Guardr” badge – planned for a later release.
• No incident-based email alerting from the plugin itself – handled today through your Guardr account’s existing notification settings.
• No MainWP integration – planned as a possible future release.

Privacy

This plugin sends this site’s domain name to Guardr’s API (api.guardr.io) over HTTPS so it can be scanned and monitored. No page content, no post or user data, no files, and no visitor information ever leaves this site through this plugin.

Every request also includes your Guardr API key (stored in this site’s own options table), to authenticate as your account, and a generic identifier of the plugin itself and its version (sent via the standard HTTP User-Agent header, e.g. “Guardr-WordPress-Plugin/0.1.3”) so Guardr can tell plugin traffic apart from dashboard or direct API traffic. This plugin explicitly sets that header itself – it does not use WordPress’s own default, which would otherwise include this site’s URL and WordPress version on every request, including ones that have no other reason to disclose it.

No data from this plugin is sent to any third party other than Guardr itself. See Guardr’s privacy policy at guardr.io/privacy and terms of service at guardr.io/terms for how Guardr handles the domain and scan data it receives and the terms governing the underlying Guardr account this plugin connects to.