Free website health check
One page, checked once, right now: whether it answers, what its certificate says, when the domain lapses, which links are dead, and what Google reads off it. No account and no card.
The checks a monitored site gets on a schedule, run once against this one.
02 / limits
What the check looks at
Five checks against one page, in the order they run. Monitoring a site runs the same checks on a schedule: uptime on every poll, the others on slower clocks set by the plan, and domain expiry from Pro up. What runs here is the product itself.
Whether it answers
We request the page and record the status code and how long it took.
The TLS certificate
Whether it is trusted, who issued it, and how many days are left.
The domain
Registrar and expiry date from the registry itself, over RDAP or WHOIS. A lapsed domain is the outage nobody sees coming. Some registries publish no expiry date, and we say so rather than leaving a blank.
The links
Up to 25 links on the page, followed to see which ones no longer answer. A server that turns us away is listed as one we could not check, not as broken.
The meta tags
Title, description, social share image and mobile viewport.
And nothing else
One page, once. No crawl of the rest of the site, no account, and no record kept afterwards, not even a shareable link to this result.
03 / after the scan
What one check cannot tell you
Everything on this page is true of the site at the second you press the button. Most of the problems that cost an agency a client start at three in the morning, when nobody is running a check.
Was it down last night?
A one-shot check has no history to compare against. Monitoring keeps one, and shows it as a trace.
Who gets told when it breaks?
Nobody. This page has no idea who you are. Monitoring emails you, and posts to Slack, Teams, Discord or Google Chat.
What about the certificate in six weeks?
We can read the expiry date today. Being warned before it passes is the part that needs somebody watching.
And the other forty client sites?
Checking them one at a time, by hand, is the problem. Billing is per site, so the fortieth costs the same as the first.