Is that website down?
Check any site’s pulse in seconds — status, response time, SSL health and a live screenshot showing exactly what visitors see right now.
A screenshot is captured even when the site is down — a 500 page or a parked domain is exactly what you need to see.
Continuous monitoring
Your monitors
Add a URL and we keep checking it in the background, building up real uptime history. No account needed — monitors are tied to this browser’s network address, so use the same connection to see them again.
Methodology
Nine checks, because “200 OK” is not enough
Plenty of monitors only watch the status code. A site can return a perfectly healthy 200 while showing a database error — so we look at the response body, the certificate and the redirect chain too.
Did the server accept our connection at all?
A 2xx is healthy; a 5xx means your application is erroring for every visitor.
Catches the "soft down": a 200 response showing a database error, a blank page or a suspension notice.
How long the complete response took, from DNS lookup to last byte.
Is the certificate present, valid and trusted by browsers?
How many days until it expires — an expired certificate takes a site down instantly.
How quickly the domain resolves. Slow DNS delays every single visit.
How many hops before the real page, and whether it loops.
Do visitors end up on HTTPS, and is HSTS set?
Up is the baseline, not the goal
Once a site stays up reliably, speed and search visibility are what decide whether it actually performs.