How this check works
We request response headers over HTTPS and HTTP, preferring an available HTTPS response. The report separates the final status, a point-in-time availability observation and the time to headers. An inconclusive network probe cannot establish a permanent outage.
A response is not always a page
A 200 usually indicates success, while 403 may indicate filtering and 503 often indicates temporary unavailability. Some websites deliberately return different responses to automated clients.
Measure the right thing
Our timing includes DNS, connection setup and redirects up to response headers. It does not measure image downloads, rendering or Core Web Vitals, and it is not an uptime percentage.
Common questions
Why does my browser work when the check fails?
Network location, rate limits, firewalls and bot protection can change the result. Compare the result with hosting logs and another ordinary connection.
Is one successful check proof of reliable uptime?
No. Historical uptime requires repeated observations over a defined period. This report describes one point in time.