How to use the Website Down Checker
- Type the website address, e.g.
example.com— or click one of the popular sites. - Press Check status. Our server requests the page from its own network, independent of your connection.
- Read the verdict: up means the site answered us, so the problem is likely on your side; down means it failed for us too.
- If it’s just you, work through the tips (DNS cache, VPN, browser extensions). Use Check again to retry after a minute.
Is the website down for everyone or just me?
When a site won’t load, the first question is whether the server is broken or something between you and it is. This checker requests the page from our server, which uses a different network, DNS resolver and location than you. If we get a normal response but you don’t, the site is up and the problem is local — your connection, DNS cache, browser, VPN or a network filter. If we can’t reach it either, it’s very likely down for everyone.
What the results mean
| Result | Meaning |
|---|---|
| 2xx / 3xx | The site is up and serving pages normally (redirects are followed). |
| 401 / 403 / 429 | The server is up but refused our automated request — common with bot protection such as Cloudflare. Real visitors are usually unaffected. |
| 404 / other 4xx | The server works, but that specific page doesn’t exist or the request was rejected. |
| 500–504 | The server or its backend is failing — the site is down or partially down. |
| Timeout / connection error | No response at all: the server is offline, overloaded, or DNS points nowhere. |
The response time is the full time to download the page from our server; TTFB (time to first byte) shows how quickly the server started answering. A TTFB above one second suggests an overloaded server or slow backend. For a deeper performance analysis run the Page Speed Test.
What to do if it’s just you
- Reload without cache: Ctrl+Shift+R (Cmd+Shift+R on Mac) or try a private window.
- Flush your DNS cache:
ipconfig /flushdnson Windows,sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderon macOS. A recently migrated site may still resolve to the old server for you. - Switch networks: disable your VPN or proxy, or try mobile data instead of Wi-Fi — corporate and school networks often block sites.
- Disable extensions: ad blockers and privacy extensions can break pages.
- Restart your router if many sites are failing.
If you run the site
Check your hosting status page and server logs, confirm DNS still points to the right server with the DNS Lookup, and make sure the certificate hasn’t expired with the SSL Checker — an expired certificate makes a site “down” for every browser even though the server responds.
Tools that pair well with the Website Down Checker
- HTTP Header Checker — Fetch any URL and see exactly what the server sends back — status code, redirect chain and every response header, with a plain-English explanation of the ones that matter for SEO, caching and security.
- Redirect Checker — Follow a URL hop by hop to see every redirect, its status code and timing, and check that the http, https, www and non-www versions of your domain all end at one canonical address.
- What Is My IP — Your public IP address and everything your browser reveals to the websites you visit — user agent, screen, language, timezone and request headers.
- User Agent Parser — Decode any User-Agent string into browser, engine, operating system and device — and find out whether it belongs to a search engine, AI crawler or script.