Is the site down for everyone, or just for you? Here is how to find out
A page will not load. You refresh, you clear the cache, you restart the router, you restart the laptop, and twenty minutes later you still do not know whether the problem is your machine, your network, your provider or the website itself.
The fix is to stop guessing and test one layer at a time. There are five, they take about a minute each, and once you know which one is broken the answer is usually obvious.
First, read the error properly
The browser is telling you more than people notice, and the message narrows the problem immediately.
- A DNS error, usually shown as the server address could not be found, means your device could not turn the name into a number, which is a lookup problem rather than a website problem
- Connection timed out means the lookup worked and nothing answered, which points at a network path, a firewall or a server that is genuinely offline
- Connection refused means something answered and said no, which usually means the service is stopped rather than the machine being unreachable
- A 403 is the site deliberately denying you, and a 429 is it telling you that you have made too many requests
- A 503 is the site itself saying it is overloaded or in maintenance, which means everyone else is seeing it too
- A 451 is unusual and worth knowing: it means the content is blocked for legal reasons in your jurisdiction
A 5xx code is the strongest evidence that the problem is not yours. Anything in the 4xx range means the site received you and made a decision about you.
Test the five layers in order
Start closest to you and work outwards, because each step rules out everything before it.
Layer one is the device. Open the same page on a phone or another computer on the same wifi. If it works there, the problem is your machine: an extension, a stale cache, a security tool, or a hosts file entry left over from something.
Layer two is the network. Turn wifi off on your phone and load the page over mobile data. If it loads on mobile and fails on wifi, the router, its DNS, or something on your home network is responsible. Restarting the router at this point is finally a sensible thing to do rather than a ritual.
Layer three is DNS. Switch your device or router to a public resolver, then try again. If it starts working, your provider’s DNS was the culprit, which happens more often than most people realise and is also the mechanism behind many provider level blocks. A quick way to confirm the diagnosis is that the site loads by name after the change but you saw a lookup error before it.
Layer four is the provider or the country. Some blocks are applied at that level, and the signature is that the site works fine for people elsewhere, resolves correctly, and simply never answers for you. Layer five is the site itself, which you check by looking for its status page and its social account, since a genuine outage is almost always announced somewhere.
The test that settles it
When the layers above have not produced a clear answer, the definitive check is to load the page from a connection somewhere else entirely. Third party is it down services do this in a rough way and are worth trying first, though they only tell you whether their machine reached the site, which is not always the same question as whether a normal visitor can.
For a proper answer people buy proxies and load the page through a connection in another country, then compare. If it loads from there and not from home, the problem is regional and no amount of restarting your router will change it. If it fails from everywhere, the site is down and the only useful action is waiting.
This also separates two things that look identical from the sofa: a site that blocks visitors from your country, and a site that is simply broken. The first one loads perfectly from a different address. The second one fails no matter where you ask from.
What to do once you know
- If it is your device, disable extensions one at a time and try a different browser profile before anything more drastic
- If it is your network, restart the router properly by leaving it off for thirty seconds, and check whether a parental control or security feature is filtering the domain
- If it is DNS, switching resolvers is a permanent fix and takes two minutes
- If it is regional, there is nothing to repair, and the site owner is usually unaware their audience in your country cannot reach them
- If it is the site, check the status page and stop refreshing, since repeated attempts during an outage occasionally get your address rate limited into the bargain
One habit worth keeping: note the exact error message and the time before you start changing things. If you end up contacting support, that single line moves you past the first three questions they were going to ask.
FAQ
Why does a site load on mobile data but not on wifi?
The two connections use different networks and usually different DNS. It points at your router, your provider’s DNS or something filtering on your home network.
Does clearing the cache actually help?
Occasionally, for a page that changed and is being served from an old copy. It does nothing for DNS problems or for a site that is genuinely down.
What does error 451 mean?
The content is being withheld for legal reasons in your jurisdiction. It is deliberately distinct from a 403, which is a plain refusal.
Is a site down checker reliable?
It tells you whether its own server reached the site. That is useful, but it is not the same as whether a normal visitor in your country can.
