Website health monitoring
Every site you manage, checked every minute: uptime, certificates, headers and the files that should never be public. One dashboard for the whole list.
Nothing to install. No code change. No access to your server. Guardr reaches the site the same way a visitor does, from outside, so it works on a site you manage for somebody else just as well as on your own.
An A to F grade in about five seconds, every finding in plain words and the exact change that clears it. Where a fix is a line of configuration, Guardr gives you the line for your platform rather than a link to go and read about it.
Guardr re-checks uptime every minute and scans the whole site every 6 hours. You hear from it when something changes: a site that stops answering, a grade that drops, a certificate with a week left. The rest of the time it stays quiet.
One domain in, a grade and a list of fixes out. No audio.
Everything above runs on every site, on both plans. There is no feature to unlock. An agent such as Claude Code or Cursor reads the same results through the MCP endpoint.
Guardr reads what any visitor can read. It does not log in to your site, it does not install an agent, it does not read your code and it does not change anything. That is the trade: setup takes one field rather than an afternoon. In return Guardr sees the outside of your site rather than the inside of it. For the things that break quietly after a deploy, the outside is where they show.
Guardr runs its own status page on the same checks it runs for you. It is public and nothing on it is typed by hand. The uptime figure, the response times and the incident history are all produced by the checks your own sites get.
Guardr also ships a WordPress plugin, listed on WordPress.org, which puts the same grade and uptime figure inside a site owner's own admin screen.
Guardr status pageOne price for each site. No annual lock-in. No tier to outgrow. The free plan is the whole product on one site, so the only question a paid plan answers is how many sites you keep.
One site
Every site you manage
Uptime from 3 global regions, certificate expiry, response headers, DNS records including DNSSEC and CAA, files that should never be public such as .git and .env, cookie settings and API keys left in your JavaScript bundles. Every check runs from outside your site. Nothing runs on your server.
Uptime every minute. A full scan every 6 hours. Both plans run at the same cadence on every site.
Everything Guardr does, on one site, for as long as you want it. No card. The only thing a paid plan adds is more sites.
An outage is confirmed from 3 global regions before Guardr sends anything. A single region that cannot reach your site is not an outage.
No. Enter a domain. Guardr checks it the way a visitor reaches it.
Yes. Guardr only reads what any visitor can read, so the sites you manage for other people work exactly the same way.
Guardr sends the alert by email or to a webhook, whichever you set up. The dashboard shows what changed. A downtime alert names the site and the response it got. A grade alert names the finding that moved the grade. Every alert is one you can act on without opening a second tool.
Yes. Every site can have a public status page. Any scan can be exported as a PDF with your own logo on it. Both are on the free plan as well as the paid one.
An agent reads every file in the repository. It cannot see the certificate a browser
receives, the response header a CDN dropped or the DNS record that did not propagate.
Guardr checks all of that from outside, grades it from A to F and hands back a fix for
every finding. Connect a client once at
https://api.guardr.io/mcp
and it calls Guardr as tools.
check_site A fresh check of one domain list_sites The sites your account watches get_site One watched site in detail Add the rest when you are ready.