Free agency tools / HTTP Request Inspector
Is it up - and is it the edge or the origin?
Check availability the way support does: apex & www over HTTP and HTTPS, from multiple regions, with Cloudflare-vs-origin errors (520-526), WAF/bot blocks and redirect chains called out - then the full response headers, timing and a copy as curl.
Results for
Availability - apex & www × HTTP/HTTPS
By region
Full request details
Redirect chain
Response headers
How it works
- 1Enter a domain - we probe apex and www over both HTTP and HTTPS, and resolve its IPv4/IPv6.
- 2The same URL is checked from multiple regions, so a 'works here, down there' problem shows up. Cloudflare-vs-origin errors (520-526), WAF/bot blocks and redirect chains are interpreted for you.
- 3Below that, the full request details: status, redirect chain, response headers and edge timing, with copy-as-curl.
Frequently asked
What does a Cloudflare 5xx (520-526) mean?
Those are Cloudflare telling you the edge is up but the origin isn't cooperating: 521 = origin refused the connection, 522 = connection timed out, 523 = origin unreachable, 524 = origin too slow, 525/526 = TLS/cert problem with the origin. They point you at the origin server, not Cloudflare.
How do you tell edge from origin?
We flag whether Cloudflare (or another CDN) is answering, and surface the CF 52x codes which are raised at the edge about the origin. A true origin fetch is only possible when the origin isn't hidden behind the proxy - the 52x codes cover the hidden case.
What is 'works in one region but not another'?
We run the same request from several regions via edge probes. If some report reachable and others don't, it's usually regional DNS, a geo-block/WAF rule, or a routing issue - which the per-region view makes obvious.
Why no DNS / TCP / TLS timing breakdown?
This runs on Cloudflare's edge, whose fetch() exposes time-to-headers and time-to-body, not per-phase timing. The numbers are honest about that.