Is this website down, or is it just me?
When a page will not load, the first question is always the same: is this website down for everyone, or is something wrong on my end? This checker answers it by requesting the address from a server on Cloudflare’s network — a different connection from yours — and reporting what came back: the HTTP status code, how long the server took to answer, every redirect and the web server software, when the site reveals it.
The result is a plain verdict rather than a wall of numbers. Up means the site answered normally, so a problem is probably local to you. Down means the server is unreachable or returning a server error, which usually affects everyone. In between are the honest cases: a site that blocks automated checkers, a page that no longer exists on a working site, or a redirect loop. Every address you test is kept in a short history on your device for one-click re-checks. For a hop-by-hop view of several URLs, use the HTTP status checker; to see whether a domain still resolves, try the DNS lookup.
How to use the Is This Website Down? Checker
- Type or paste the address into Website address. A bare domain is checked over https://.
- Press Check now or hit Enter. The request goes out from Cloudflare’s network, not your device.
- Read the verdict at the top of the card, then the status code, response time, redirect count and server name underneath. What the checker saw lists each redirect hop.
- Press Check again to retry during an outage, or click any address under Recently checked on this device to repeat it.
Is This Website Down? Checker features
Clear up / down verdict
Each result is classified as up, up with issues, down or unreachable, with a sentence explaining what that means.
Status code and timing
Shows the final HTTP status, the time to first response for each hop, and labels the total fast, normal or slow.
Redirect chain
Follows up to ten redirects and lists every hop with its code and destination, so loops are obvious.
History on this device
The last 20 addresses with their verdict, status and time stay in your browser’s local storage for one-click re-checks; nothing is sent anywhere and Clear history removes it.
Honest about limits
When the checker itself cannot be reached, the page says so instead of reporting the site as down. No page content is downloaded.
How to read the result
| What the checker got | Verdict | Most likely cause |
|---|---|---|
| 200–299 | Up | The site works from outside. If it fails for you, suspect your DNS, VPN, firewall or ISP. |
| Redirects ending in 200 | Up | Normal redirect, for example http → https or to www. The final page answered. |
| 404 / 410 | Up, with issues | The server works but this exact page is missing or was removed. |
| 401 / 403 / 429 | Probably up | The server answered but refused the checker: a login wall, bot protection or a block on data-centre traffic. |
| 500 / 501 | Down | The application behind the site is failing. Usually affects everyone. |
| 502 / 503 / 504, Cloudflare 52x | Down | A proxy or CDN is up but the origin server is down, overloaded or unreachable. |
| No response | Unreachable | DNS failure, connection refused, TLS error or timeout — down for everyone, or blocking our network. |
| Ten redirects without a page | Up, with issues | A redirect loop: the server is online but no browser reaches the page. |
What a server-side check can and cannot tell you
This check comes from one place: Cloudflare’s network. That makes it a good second opinion — if your browser fails but the checker gets a 200, the site is almost certainly fine and the problem sits between you and it. It is not proof that the site works for everybody: availability differs by country, network and minute, and a site in a partial outage can answer one request and fail the next, so re-check before drawing conclusions.
The checker only reads response headers. It cannot tell whether a page that answers 200 shows the right content, whether a JavaScript app loads, or whether a login works. Private and intranet addresses are refused, and only ports 80 and 443 are used.
The site is up but not for me — what to try
- Reload with the cache bypassed (Ctrl + Shift + R, or Cmd + Shift + R on a Mac) or try a private window to rule out a cached error page.
- Switch from Wi-Fi to mobile data. If the site loads, the block is on your router, ISP or office firewall.
- Change your DNS resolver to 1.1.1.1 or 8.8.8.8, or flush the DNS cache; a stale record can point you at a dead server for hours.
- Turn a VPN or proxy off (or on). Some sites block VPN ranges; some networks block certain sites.
- If you see a certificate warning, run the SSL certificate checker — an expired certificate stops browsers while a status check still succeeds.
- Confirm your own connection with What is my IP, then check again in a few minutes.
Is This Website Down? Checker FAQ
How do I check if a website is down for everyone or just me?
Enter the address and press Check now. The request comes from Cloudflare’s network rather than your connection: if the site answers 200 here but not in your browser, the problem is on your side; if it answers a 5xx error or nothing at all, it is down for others too.
Why does the checker say the site is up when it does not load for me?
Your route to the site is different from the checker’s. A bad DNS answer, a VPN, a firewall at work, an ISP block, an expired certificate or a cached error page can all stop your browser while the server is fine.
Why does it say “probably up” or 403?
Some sites block data-centre networks or require a browser challenge first. They answer 403 or 429 to automated checkers while loading normally for people, so the server is online but the checker cannot see the page.
What does “unreachable from our checker” mean?
The domain did not resolve, the connection was refused, the TLS handshake failed or nothing came back within 15 seconds. That usually means the site is down for everyone, though a few sites drop traffic from cloud networks on purpose.
What happens if the checker itself is unavailable?
The page says plainly that the checking service could not be reached, rather than reporting the website as down — for example when the site runs without its server functions or an ad-blocker blocks the request.