Why website checkers report false "down" results — and how to read them
You open a popular website and it loads perfectly. Then you run it through an "is it down?" checker and get a big red DOWN, with a 403 or 404 error. Both can't be right. Here's what's really going on, why simple checkers get it wrong, and how to read a status result with confidence.
A website that answers is a website that's up
A website check boils down to one question: did the server respond? If it sent back any HTTP reply, the server is online. The trouble starts when a checker treats every unwelcome reply — 403 Forbidden, 404 Not Found — as proof of an outage. Those codes mean the server is running and made a decision about the request. That's the opposite of down.
Five reasons working sites look broken to checkers
1. Bot protection blocks automated visitors
Large websites face a constant stream of scrapers, spam bots and attacks, so many put a protection layer in front of their servers — Cloudflare, Akamai, Imperva, DataDome and others. When a request looks automated, these services answer with a challenge ("checking your browser…") or a flat refusal, usually as 403, 429 or sometimes 503. A real browser passes the challenge in the background and you never notice. A basic checker gets stuck on it and calls the site down.
Cloudflare even labels these replies: its challenge responses carry a cf-mitigated: challenge header, which is a reliable sign that the site is up and simply guarding the door.
2. The request doesn't look like a browser
Browsers send a rich set of details with every request — what kind of browser it is, which languages and content types it accepts, and so on. Many quick checkers send almost none of this, or use a lightweight HEAD request that asks for headers only. Some servers and content-delivery networks reply to these stripped-down requests with 404, 400 or 405, even though the same page works for people.
3. Redirects and cookies aren't handled properly
Big portals often bounce first-time visitors through a redirect that sets a cookie — for a region, a language or a consent choice — and expect the cookie back on the next request. A checker that doesn't carry the cookie forward can end up on an error page, or stuck in a loop.
4. Data-centre traffic is treated differently
Checkers run on servers in data centres, not on home connections. Some websites restrict or rate-limit traffic from data-centre networks, or from particular countries, because that's where most bot traffic comes from. The site is fine for you; it's just wary of the checker.
5. One slow moment becomes a verdict
A single timeout or one brief 502 error can be a blip rather than an outage. A checker that tries once and reports the first failure will cry wolf.
How CheckIfSiteDown avoids false alarms
- We ask like a browser. Every check is a full
GETrequest with the same headers a current desktop browser sends. - We follow redirects and keep cookies, re-checking each hop for safety, just as a browser would.
- We recognise protection pages. Challenge pages from Cloudflare, Akamai, Imperva, DataDome, AWS WAF and others are reported as Up — protected, even when they arrive as a 503.
- We treat 4xx as up and tell you why the server said no, so you can decide whether it matters.
- We double-check failures — retrying, and trying the
www.and plainhttp://versions where it makes sense — before we report a site as down. - We only say DOWN for real failures: domains that don't resolve, refused or dropped connections, timeouts, broken HTTPS, and genuine 5xx server errors (including Cloudflare's 52x origin errors).
How to read a result
| You see | What it means |
|---|---|
| Up Up and responding | The page loaded normally for our server. |
| Up Protected by Cloudflare (or similar) | Online; the site challenged our automated visit. People get through normally. |
| Up Answered with 403 / 404 / 429 | Online; the server refused or redirected our checker. The page should still load in your browser. |
| Down Server error 5xx | The server is reachable but failing to serve pages. |
| Down Domain not found / Connection refused / Timed out | Nothing answered. A genuine outage — or the address is wrong. |
The honest limits of any single check
No checker is perfect. A check shows what one server saw at one moment. A site can be up for us and broken in your region, or block our network while working for you. If the result doesn't match what you're seeing, press Check again, follow our "down or just me" guide, and if you think we got it wrong, tell us — that feedback directly improves the checker.
If you run a website
For monitoring your own site around the clock, choose a service that checks from several locations, confirms failures before alerting you, lets you set which status codes count as healthy, and supports a lightweight health-check address on your site. And if you use bot protection, allow-list your monitoring service so it isn't challenged like a stranger.