Is this your problem?
- The site times out or shows "this site can't be reached" for you only
- It loads on your phone over mobile data, or for colleagues and customers
- A down-checker such as "is it down right now" reports the site as up
- It stopped loading for you after the site moved host or changed its address
- Only one device or one browser of yours fails, the rest are fine
What usually causes it
How to tell: Your computer or router remembers the old server address for a while after a move, and keeps going there.
How to tell: A cached error, a broken extension, or corrupt site data stops the page loading in that one browser.
How to tell: The router is holding an old address, or your internet provider is having a local wobble.
How to tell: Antivirus, a firewall, a VPN, parental controls, or an edited hosts file is blocking or misdirecting the address.
How to tell: A security plugin or firewall temporarily blocked your address after failed logins or unusual activity.
Before you touch anything
- Prove it is your end: open the site on your phone over mobile data, not your wifi. If it loads there, the site is fine and the fix is on your device or network.
- Note whether it fails on every browser and device, or only one. One browser points at the browser; everything points at DNS or the network.
How to fix it, step by step
-
1
Check it is really up
Use a down-checker site, or ask someone elsewhere. If it is up for them, do not touch the site; fix your end with the steps below.
-
2
Try another browser and a private window
If it works in a private window or a different browser, the cause is your normal browser: clear its cache for the site, and disable extensions one by one.
-
3
Flush your DNS cache
On Windows, open Command Prompt and run ipconfig /flushdns. On a Mac, run sudo dscacheutil -flushcache in Terminal. This clears the old address so your computer looks it up fresh.
-
4
Restart your router
Power the router off for thirty seconds and back on. It clears the router cache and a stuck connection, and picks up the current address.
-
5
Switch DNS or network to test
Set your device DNS to a public resolver such as 1.1.1.1 or 8.8.8.8, or try a different network. If it loads, your provider or router DNS was the problem.
-
6
Turn off VPN and antivirus web-shield, and check the hosts file
Disable any VPN and the web-protection part of antivirus, then retry. If an entry for the domain is in your hosts file, left over from testing a site move, remove it.
-
7
If you were blocked, wait or ask
If a security tool blocked your address after failed logins, it usually clears within an hour, or the site owner can allow-list you.
Stop and get help if
- The checks say the site is genuinely down for everyone, not only you. Then it is a server or hosting problem, not your end.
- It just moved host and will not load for anyone yet, which is usually DNS still spreading and can take up to a day.
- You share the site with a team and none of you can reach it, which points back at the server.
Stop it happening again
- After moving a site, expect your own machine to lag; flush DNS rather than assume it is broken.
- Remove test entries from your hosts file as soon as a migration is done.
- Keep one clean browser with no extensions for checking whether a problem is the site or your setup.
Questions people ask
Does this mean my site was hacked?
No. A site that is up for others and not for you is a connection problem on your side, not a break-in.
How long does DNS take after a move?
Usually minutes to a few hours, sometimes up to a day. Flushing your own DNS fixes your machine; the rest of the world updates on its own.
It is only my office that cannot reach it. Why?
An office network or firewall may cache DNS or block the address. Ask whoever runs the network to flush DNS or check the firewall.