KNOW WHAT YOU’RE LOOKING AT
Signals, not guesswork.
Each instrument answers a different question: did the website answer, how long did our check take, and when was it observed?
The colors tell you where to look.
Responding
The homepage answered this request successfully from our measurement point. This does not test sign-in, checkout, every page, or every country.
Your next step: If it still fails for you, compare a private browser window and another connection.
Restricted or incomplete
The site answered, but a protection rule or an unfinished redirect prevents a complete answer. We follow up to five safe HTTPS redirects. A successful destination gives a green result; a blocked or unsafe destination remains uncertain. Yellow means “look closer,” not “broken.”
Your next step: Open it in your browser. Owners should review access rules or the redirect destination.
A problem in this check
The request received an error, its address could not be resolved, or a secure connection failed. Red identifies an observed problem; it is not proof of a global outage.
Your next step: Read the specific explanation, check spelling and consult the provider’s status information.
Not enough evidence
A time limit or a problem with our measurement prevented an answer. We do not turn missing evidence into a claim that another website is down.
Your next step: Compare in your browser and try again later.
Is the website fast?
This check cannot answer that. It measures our combined address lookup, connection and response-header time. It does not inspect page contents or measure how quickly it becomes usable on your device.
The main result says “under a second” or “about two seconds,” rather than making you interpret milliseconds. Exact duration remains available in the technical details.
What the comparison bars mean
After two fresh checks of the same domain, with the same outcome and measurement point, the bars compare their observed duration. They exist only in this tab. A shorter bar means less time for this check. It is not an industry ranking, a normal-speed threshold, or proof of lasting improvement. Cached checks are excluded.
If a later check takes longer, possible causes include a different resolved address, network conditions, server load, or name-lookup delay. This tool does not separate those causes yet. For page speed, use a real page-loading test such as Google PageSpeed Insights. This is an ordinary helpful link, not an affiliate link.
How current is the result?
The timestamp records when the observation happened. A recent result may be reused for up to one minute to avoid repeatedly requesting the same website. The result says when this happens. Reusing a result does not mean the website has become faster.
This tool does not monitor continuously. No historical uptime percentage, global outage percentage or live user count is invented.
Why are there still codes in the details?
They help a website owner or support team investigate a specific request. The plain-language result comes first.
| Technical clue | Human meaning | Useful next step |
|---|---|---|
| 200–299 | This request succeeded. | Check the function that actually failed for you. |
| 300–399 | The server returned a redirect. | We follow standard safe HTTPS redirects. If we stop, the main result explains why. |
| 401 / 403 | Sign-in or access is restricted. | Compare your browser and access rules. |
| 404 | The requested page was not found. | Check the address and homepage. |
| 405 | This type of automated request is not allowed. | A normal browser request may still work. |
| 429 | The site is limiting requests. | Wait; do not repeatedly retry. |
| 500–599 | The server reported an error for this request. | Check provider information, error logs and recent changes. |
What do the three steps show?
- Find the address: whether the domain was resolved to public network addresses.
- Connect securely: confirmed when a response was received through the verified HTTPS connection. Otherwise it remains failed or unconfirmed.
- Read the response: the server’s answer to our homepage request. We do not read page contents. We follow up to five safe HTTPS redirects within the overall time limit; each destination must pass the same public-address and certificate checks.
These are observations from one check, not three independently timed tests. For exact data and limits, see the method and API.
Why do websites send us elsewhere?
A site may move from its short name to www, or choose a language page. A redirect is normal. Our result describes the final response we actually tested, including errors or access restrictions.
We stop if the destination uses an insecure link, a private network address, a loop, a missing destination or more than five redirects. A stopped check does not establish that the destination is broken. The explanation gives the reason and a practical next step. Some servers reject the usual HEAD request; for a 404, 405 or 501 response we can retry with a header-only GET request. Neither request inspects page contents.
Copy a report or repeat a check
Copy report gives you a readable support summary with the observation, limits and next step. Technical data remains in the expandable details. If clipboard access is blocked, a selectable report appears below the button.
The latest five distinct domains are shown only in the memory of this page. Tap one to repeat its check. Clear removes the visible history; reloading also removes it. It is not uploaded as a public history. Optional usage events never contain the entered domain.
For an exact match to GitHub, OpenAI, ChatGPT or Cloudflare, the result also links to the provider’s verified official status page. These links do not load or imply live provider status. We do not guess status pages for other domains.
When would a paid tool help?
Start with free troubleshooting. A website owner who needs ongoing alerts may benefit from monitoring. A person blocked by one website does not automatically need a VPN, a new hosting plan or paid support. No affiliate relationship is active.