URL Status Checker
The URL Status Checker sends a live GET or HEAD request to any public URL and reports exactly what the server returned: the HTTP status code, status text, response time, and every response header. It does not follow redirects, so a 301 or 302 shows up as-is rather than being silently resolved to its final destination. Use it to verify deploys, debug broken links, or confirm a CDN or load balancer is responding the way you expect.
How it works
Browsers block a page's own JavaScript from reading the response of a request to a different origin unless that origin explicitly allows it with CORS headers, which most sites do not set for arbitrary cross-origin callers. To get around that, this tool does not fetch the target URL from your browser at all. Instead your browser sends the URL you enter to our edge proxy, a small Worker running close to you on Cloudflare's network, and the proxy performs the actual GET or HEAD request on your behalf.
The proxy times the request from the moment it opens the connection to the moment the first byte of the response arrives, records the numeric status code and status text the server returned, and copies every response header it received. It deliberately does not follow redirects — a redirect response is captured and shown exactly as sent, with its Location header intact, rather than being chased to a final destination. That distinction matters when you are debugging a redirect that should not be firing, or verifying that a deploy actually returned a 200 instead of a cached 304.
Only the URL you submit is sent to the proxy for the duration of that one request; it is not logged, stored, or associated with you, and the proxy never fetches anything you have not explicitly asked it to.
Frequently asked questions
Why does the URL Status Checker show a 301 instead of the final page?
The tool intentionally does not follow redirects, so you see the exact status code the server first returned. Use the Redirect Chain Tracer if you want to follow the full chain to its final destination.
Does this tool work on localhost or internal URLs?
No. The edge proxy can only reach publicly routable hosts, so localhost, private IP ranges, and internal-only domains will fail to resolve.
Is my URL stored or logged?
No. Only the URL you submit is sent to our edge proxy to perform the single request, and it is not stored or associated with you afterward.
What's the difference between GET and HEAD in this tool?
GET downloads the response body along with headers; HEAD requests only the headers and status line, which is faster and useful when you only care about metadata.
Why is the response time higher than what I see in my own browser?
The request runs from our edge location rather than your device, and includes the round trip to the proxy itself, so timings will differ from a direct browser request or curl.