Errors / Network errors

This site can't be reached

Chrome could not connect to the website at all, so it shows its own page instead.

Nobody reaches the site; Chrome shows its grey error page.

Seeing it on someone else’s site?

Read the small code under the message: it says which of these it is.
DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED: the address does not exist, or your network cannot look it up. Check the spelling, then try another network.
ERR_CONNECTION_REFUSED or ERR_CONNECTION_TIMED_OUT: the site's server is down or unreachable from where you are.
If other sites work and this one does not from any network, the site is down; if nothing works, it is your connection.

Why it happens, if it is your site

The domain expired, or its DNS records were changed or deleted.
The server is down, or a firewall drops connections to it.
A DNS change still spreading: some networks see the new address, others the old one.

How to fix it

Check the domain's registration and its DNS records (dig yourdomain.com).
Check the server is up and its firewall lets web traffic in (ports 80 and 443).
After a DNS change, wait for the old record's TTL to pass; lower TTLs before a planned move.

Whose problem it is

Either the site's own code or a third party's, depending on where it comes from.

Does your site have it?

Free, no account. We open your page and four more in a clean Chrome and list every error like this one, with the page and the click that caused it. How the free page check works.

Often seen with

ERR_NAME_NOT_RESOLVEDThe page asked for something on a web address that does not exist, or no longer does.
ERR_CONNECTION_REFUSEDThe server at that address exists but refused to take the connection.
ERR_CONNECTION_TIMED_OUT / ERR_TIMED_OUTThe server took too long to answer, and the browser gave up.