🔎 Free · private · in-browser
Free website status checker — status code, latency & headers
Check any URL from the edge: status, response time, redirects, headers.
Response headers
Check any website's status in a second
When a site "goes down" the first question is always the same: what is the server actually returning? This website status checker fetches your URL from Cloudflare's global edge and shows you the raw answer - the HTTP status code, the response time in milliseconds, the final URL after redirects, and every response header. No browser CORS errors, no signup, no guessing.
What the status code tells you
- 2xx - success. The origin handled the request and returned content.
- 3xx - a redirect. Follow the final URL to see where visitors actually land.
- 401 / 403 - the resource exists but is protected or forbidden.
- 404 - the path is wrong or the page was removed.
- 5xx - the origin errored. Your app or server is failing, not the network.
- A failed request - no response at all within ten seconds: DNS, TLS, or the origin being fully down.
Response time and redirects
The response time is measured from our edge, so it is a clean read on origin performance without your local connection getting in the way. A slow number here points at the server, a CDN miss, or a heavy backend. The final URL matters too: a chain of redirects adds latency and can quietly break canonical URLs, sitemaps, and analytics. Seeing the resolved destination in one shot saves a lot of back-and-forth.
From one-off check to always-on monitoring
A single check is perfect for triage. When you want to know the moment a site goes down - not the next time you happen to look - add it to the Uptime Monitor to run scheduled checks from the edge and publish a clean public status page. To dig into the headers you see here, the HTTP Header Inspector grades them against security best practices.
Frequently asked questions
What does the website status checker do?
It fetches any URL from Cloudflare's edge and reports the HTTP status code, how long the response took, the final URL after any redirects, and the full set of response headers - instantly, with no signup.
Why does it run server-side instead of in my browser?
Browsers block cross-origin requests and hide most response headers for security. Running the check from our edge sidesteps CORS entirely, so you see the real status code and every header the server returns.
Can I check a site on my local network?
No. For safety the checker blocks localhost and private network addresses. Point it at a publicly reachable URL. To watch a public site continuously, set up an Uptime Monitor instead.
Is there a timeout?
Yes - requests time out after 10 seconds. If a site does not respond in that window it is reported as a failed request, which is usually a sign the origin is down or very slow.