Feature
Content & keyword checks
A site can return a cheerful HTTP 200 and still be completely broken. These are the checks that look at what the page actually says.
What it does
The worst outages are the ones that pass an uptime check. A failed deploy that renders an empty template, a database error swallowed into a blank page, a plugin that replaced the homepage — all of them answer 200 and all of them are invisible to a status-code check.
A keyword check fixes that by asserting on content: text that must be present, or text that must never appear. The absence of your product name, or the sudden presence of the word “error”, is the signal.
Two related checks run alongside it. Redirect detection catches a site that has started sending visitors to a domain that is not yours, and content-integrity (defacement) detection hashes the page so an unexpected rewrite is flagged even when every individual keyword still matches.
- Keyword must-be-present and must-be-absent assertions
- Unexpected redirects to foreign domains
- Page-defacement detection via content hashing
- SEO-file checks (robots.txt, sitemap) so a deploy cannot quietly remove them
- Broken-link crawling across the site
Works alongside
Uptime & performance
HTTP/HTTPS checks around the clock — down to every 30 seconds. Status codes, response time (TTFB), payload size, plus ICMP ping and TCP-port checks per site.
Read moreSSL, domain & security
Certificate-expiry and domain (WHOIS) expiry alerts days in advance, SSL chain validity, and a security-headers audit (HSTS, CSP, X-Frame-Options).
Read moreDNS & network
DNS resolution with A/AAAA/MX/NS change detection — the signal that a domain has been hijacked — plus TCP port and ICMP reachability checks.
Read moreFAQ
About content & keyword checks
What exactly is the “white screen of death”?
A page that returns HTTP 200 with no usable content — usually a fatal error that was caught and hidden. Uptime checks call it healthy; a keyword check calls it broken.
Will a normal content edit trigger a defacement alert?
The check is tuned to flag wholesale rewrites rather than ordinary copy changes. For pages you edit constantly, a keyword check is the better fit.
Can I check a page behind a login?
Checks run unauthenticated, so they see what an anonymous visitor sees. For protected areas, point the check at a public health endpoint instead.