Where does it fail?
Pick the closest match for a useful next step.
Check a website above, or choose your situation here. These steps are guidance, not extra measurements.
Website not loading?
Check if a website responds, understand the result, and find your next step.
For website owners: inspect public text and bot rules. Optional files are explained, without an invented readiness score.
✓ Responding! Restricted! Error? Unclear
WEBSITE SIGNAL
✓Waiting
One measurement pointCHECK FEEDBACKNot checkedNo comparison yet.
Check time is not page-load speed.
This check
Previous
Find the addressNot checked
Connect securelyNot checked
Read the responseNot checked
This readable summary includes the result, its limits and your next step.
Technical details & measurement limits
Server response—
Total check time—
Checked at—
One observation cannot prove a worldwide outage. This checks response headers, not logins or checkout. We follow up to five safe HTTPS redirects within the check’s time limit. Some sites still restrict automated requests.
Understand every measurement →Can agents read this page?
Static evidence from one location. Published bot rules are not proof that a particular bot can connect. No scripts or agent actions are run.
Evidence and measurement limits
A LITTLE HELP GOES A LONG WAY
Let’s get you unstuck.
Understand the warning.
For when your browser gives you a number instead of an answer.
Response received. The homepage answered this request. It does not prove every feature is working.
Signals, codes & check times →A few useful answers.
Does a green result mean the whole website works?
It means the tested response answered successfully from one location. Sign-in, checkout and other countries may behave differently. If it still fails for you, compare a private window and another connection.
What happens when a website redirects?
We follow up to five safe HTTPS redirects within the overall time limit. The result describes the last destination we tested. A loop, private address or unsafe link stops the check with an explanation.
Is check time the same as page-load speed?
No. The quick check includes finding the address, connecting and reading response headers. It does not inspect page contents. The separate agent-readability check reads bounded public documents only when requested. See what the comparison means.
Why can a check be blocked when the site works for me?
A login, protection rule or request limit can block automated checks. Yellow means that more evidence is needed. Try the website in your own browser before calling it an outage.
Is my recent-check history public?
No. The five recent domains stay only in this page’s memory. Clear or reload to remove them. Optional usage measurement records step names, never the domain you entered. Read the privacy details.
Evidence, with its limits.
One location. One observation. No invented outage percentage.
An answer you can use.
Practical next steps, including when a result is uncertain.
Useful for your tools, too.
The same result through our API & browser-agent tools.