Checks a site from our server and compares it against a live check from your own browser, so you can tell the difference between "actually down" and "not reachable from your network."

Why check from two places?

A domain can resolve just fine and still be completely broken - DNS working doesn't mean the server behind it is healthy. And a single check from one location only tells you about that one network path. This tool runs two independent checks:

From our server - a real HTTP request from Cloudflare's network, reporting the actual status code the site returned, or a genuine timeout/connection failure. This reflects whether the site itself is up, from a neutral network.
From your browser - a live connection attempt from your current device and network. This can only tell us whether a connection succeeded, not the actual status code, but it reflects your specific network path.

If our server reaches it fine but your browser can't, that's a strong signal the issue is on your network specifically - not that the site is down. If both fail, it's more likely genuinely down or broken. Curious about network-level blocking specifically? Our DNS Lookup tool has a similar reachability comparison focused on DNS.

Known limitations: our server's check runs from Cloudflare's network, which can behave differently than an ordinary residential connection (some sites treat traffic from cloud/hosting IP ranges differently). And on your side, an ad blocker, browser extension, or a very brief blip can produce a false "unreachable." Treat this as a strong diagnostic signal, not a certainty.

Is This Site Down?

Why check from two places?