How to Check Whether Your Site Is Really Down or Just Blocked on Your Network
A site that will not load is not always down. Run these checks in order to find out whether it is the site, your network, or a block.
You click a link, the page spins, and then nothing. Or an error page. Your first thought is that the site is down, and sometimes it is. But a site can also be perfectly healthy while your network, your DNS, your VPN, or the site's own firewall keeps you out. Treating every failed load as an outage wastes your time, and if it is your own site, it can send you chasing a server problem that does not exist. There is a short sequence of checks that settles the question in about two minutes, and it works whether the site belongs to someone else or to you.
Start with a check that is not you
The fastest way to separate "down" from "down for me" is to ask a computer on a different network. Our Uptime Monitor has an instant check that requests the page from Cloudflare's network and reports the status code and response time. If it says the site answered, the site is up, and the problem sits somewhere between you and it. If it fails there too, the site is very likely down for everyone.
Your phone is the second opinion. Turn off Wi-Fi so the phone uses mobile data, then open the same page. If it loads, your home or office network is the suspect. If it fails on mobile data too, and the outside check also failed, stop troubleshooting your own setup. The site is down, or something close to it is.
One warning: if your phone and your laptop both route through the same VPN or the same DNS filter, the two tests can agree for the wrong reason. Switch the VPN off for one test, or the result tells you nothing.
Read what the error actually says
The browser's error message is a clue, not decoration. A 500, 502, 503 or 504 means you reached the site's front door and something behind it failed. That is their side, almost always. A 403 or a 429 is different, and this is the mistake I see most often: people read "Forbidden" as "down". A 403 proves the server answered you and decided not to serve you. The site is up. Something about your request, your IP address, or your location got blocked. A 429 means you asked too often and got rate limited, which is also proof the server is alive.
DNS errors sound different again. "Server not found", "DNS_PROBE_FINISHED_NXDOMAIN", or "ERR_NAME_NOT_RESOLVED" mean your computer could not turn the name into an address at all. That can be your DNS, or the site's domain settings. Run the name through our DNS Records Lookup and compare what it returns with what your own computer resolves. If the lookup tool finds the records and your machine does not, your DNS is the problem.
A worked example, with real numbers
Here is what the sequence looks like on a healthy site. I ran our Uptime Monitor instant check on https://example.com this morning. It came back with a 200 status code in 12 milliseconds. That is the whole answer: the site is up, it answered quickly, and anyone who cannot reach it has a local problem. If the same check had returned a 503, or timed out, I would have believed the site was down instead.
Now flip it. Say the same check returns 200 in 12 ms, but your browser still shows an error. You now know the site is fine, so every fix you try is on your side. That one fact saves you from rebooting a server, filing a ticket with a host, or waiting for an outage that is not happening.
If it is just you, work through the fixes in this order
First, open the page in a private or incognito window. Extensions and stale cookies cause a surprising number of failed loads, and a private window rules both out in seconds. If the page loads there, disable your extensions one at a time until you find the culprit.
Second, switch off your VPN and any ad blocker or security software that filters traffic, then try again. Some sites block VPN exit addresses outright, and a VPN server can have its own outage while your connection looks fine.
Third, change your DNS. Point your computer at 1.1.1.1 or 8.8.8.8 and reload. If the page appears, your ISP's DNS was serving a stale or wrong answer. You can leave the public DNS in place or report the fault to your ISP.
Fourth, flush your local DNS cache. On Windows that is ipconfig /flushdns, and on a Mac it is sudo dscacheutil -flushcache. Then restart the browser, not just the tab.
Finally, restart your router. It sounds like a joke, and it fixes more of these than anyone admits. If the site loads after the restart, the router's cached DNS or its connection state was the block.
The edge case: blocked, not broken
Sometimes a site is up, your network is fine, and you still cannot get in. The site may block your country, your IP range, or your ISP. I have seen this with sites that geo-block whole regions, and with office firewalls that block categories of sites without telling anyone. The giveaway is the pattern: the outside check says 200, your phone on mobile data loads the page, but your office or home connection gets a 403 every time. Run our IP Location Lookup on your own address to see what the site sees, your country and your ISP, and ask the site's owner or your network admin whether that range is blocked. If it is your own site doing the blocking, check your firewall rules and any country blocking in your security settings before you touch the server.
What to do first, next time a site will not load
Do not start by rebooting things or refreshing the same tab twenty times. Run the outside check first, then the phone on mobile data. Those two answers tell you which side of the problem you are on, and everything after that is just working down the list on the right side. If you run a site of your own, set up the monitoring before the next outage. Our post on knowing your website is down before your customers tell you shows how to get the alert before your visitors do.
A new post lands here every day. If there is a topic you want covered, email ask@websmartstudios.com.