What Does 'This Site Can't Be Reached' Mean?
'This site can't be reached' is Google Chrome's generic error shown when the browser cannot open a page and load its content. It usually means the connection failed before the site's server could respond, not that the site's design is broken. Common causes include no internet connection, a mistyped or expired domain, DNS problems, a firewall or VPN block, or the server being down. Chrome normally adds a specific code such as ERR_CONNECTION_TIMED_OUT, ERR_NAME_NOT_RESOLVED, or ERR_CONNECTION_REFUSED that points to the exact cause.
- What it is
- Chrome's generic error when it cannot establish a connection to load a page
- Common sub-codes
- ERR_NAME_NOT_RESOLVED, ERR_CONNECTION_TIMED_OUT, ERR_CONNECTION_REFUSED (Chromium network error list)
- Most frequent cause
- DNS resolution failure or the origin server being offline (Chrome network diagnostics)
- Where the fault lies
- Often the visitor's network or DNS, sometimes the website's host
- Fast isolation test
- Load the site on mobile data or another device to separate local from server issues
What this Chrome error actually means #
'This site can't be reached' is the standard message Google Chrome displays when it tries to open a web page but never receives a usable response from the server. The important detail is that the failure usually happens during the connection stage, before any of the site's content loads, so it rarely means the website's design or code is broken. Instead, something interrupted the path between your browser and the server: your device may be offline, the domain may not resolve to an address, a firewall may be blocking the request, or the host may be down. Chrome shows the same friendly headline for many underlying problems, then prints a specific technical code beneath it, which is the fastest way to narrow the cause. If the site is your own, a persistent version of this error points to a hosting or DNS fault worth investigating quickly, sometimes with hands-on help like our /services/website-rescue page for sites that have gone dark.
Reading the exact error code Chrome shows #
Chrome almost always prints a short code under the headline, and that code tells you where to look before you try random fixes. Each one maps to a different stage of the connection, so matching yours narrows the problem from dozens of possibilities down to one or two. Compare your code against the common ones below.
ERR_NAME_NOT_RESOLVED -> DNS cannot find the domain
ERR_CONNECTION_TIMED_OUT -> server too slow or unreachable
ERR_CONNECTION_REFUSED -> server actively rejected the request
ERR_ADDRESS_UNREACHABLE -> no network route to the server
ERR_INTERNET_DISCONNECTED -> your device has no connection
DNS_PROBE_FINISHED_NXDOMAIN-> domain does not exist or expiredIs it your device or the website? #
Before assuming a website is broken, work out whether the fault is on your side. The quickest check is to open the same address on a second device using a different network, such as your phone on mobile data instead of Wi-Fi. If it loads there, the problem is local to your first device or its network, not the site. If it fails everywhere, the website or its host is more likely at fault. You can confirm with an independent monitor rather than trusting one browser; our /tools/website-down-checker reports whether a site responds from outside your connection. Local causes include a dropped connection, an outdated cached DNS entry, an over-aggressive VPN, or browser extensions interfering with requests. Server-side causes include an expired domain, misconfigured DNS records, or an offline host. Sorting the two apart in the first minute saves you from restarting a router when the real issue is a lapsed domain renewal, or the reverse.
DNS problems: a leading cause #
DNS, the system that translates a domain name into a server IP address, is one of the most common reasons Chrome cannot reach a site. If the domain does not resolve, you often see ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN. Causes range from a stale local DNS cache to a misconfigured or missing record at the domain's provider, an expired domain registration, or a nameserver that recently changed and has not propagated. As a visitor, flushing your DNS cache, switching to a public resolver like 1.1.1.1 or 8.8.8.8, and retrying usually helps. As a site owner, you should confirm your A and CNAME records point to the correct host and that your registration has not lapsed. DNS changes can take up to 48 hours to spread worldwide, so a recent migration may explain intermittent failures. Getting records and nameservers configured correctly is exactly the kind of work covered on our /services/domains-dns-email page, where a single wrong record can take a whole site offline.
Server and hosting causes #
When the fault is genuinely on the website's side, the server is often the culprit. The host may be overloaded, crashed, undergoing maintenance, or refusing connections because a service like the web server or PHP has stopped. In these cases Chrome may show ERR_CONNECTION_REFUSED or ERR_CONNECTION_TIMED_OUT, because the request reaches the network but no application answers on the expected port. Shared hosting that runs out of resources, an expired SSL certificate forcing a broken redirect, or a firewall rule that blocks your region can all produce the same headline. Cheap, oversold hosting is a frequent offender, which is why steady uptime is a core reason businesses move to a managed environment like our /services/managed-hosting page describes. If your own site throws this error only sometimes, it usually signals a capacity or configuration problem rather than a total outage, and reviewing server logs is the reliable way to see which service failed and when it happened.
Firewall, VPN, and antivirus blocks #
Sometimes nothing is wrong with the website at all, and a piece of software on your side is silently blocking the connection. Corporate firewalls, school networks, some antivirus suites, and VPN clients can all intercept requests and prevent Chrome from reaching certain domains, producing the same 'this site can't be reached' screen. Overzealous security extensions and ad blockers occasionally do the same. To test this, temporarily disable your VPN, pause the antivirus web shield, or try the site in an incognito window with extensions turned off. If it suddenly loads, you have found the blocker and can add an exception. On managed work networks, the block may be an intentional policy you cannot change from your device. This category matters because owners sometimes assume their site is broken when a single visitor's security tool is the only thing failing. When your own audience reports blocks, hardening and correctly configuring protections, as covered on our /services/website-security page, prevents legitimate traffic being caught in the net.
How to fix it as a visitor #
If you are just trying to open someone else's site, a short checklist clears most cases. First, confirm your own connection by loading a different, well-known site; if that also fails, restart your router. Next, reload the page and try it in an incognito window to rule out cache and extensions. Then flush your DNS by restarting the browser or your device, or switch to a public DNS resolver. Disable any VPN or proxy and retry, since these reroute traffic and can break specific domains. Double-check the address for typos, and make sure you are using https where expected. If the site still fails, test it from your phone on mobile data to see whether the problem follows you. When it loads elsewhere, the issue is local; when it fails everywhere, the site itself is down and there is little you can do but wait. A quick look at /tools/website-down-checker confirms which of the two you are facing.
How SSL certificate problems trigger this error #
An expired or misconfigured SSL certificate is an underrated cause of this screen, especially when your site forces secure connections. If the certificate has lapsed, does not match the domain, or the secure handshake fails, the browser may refuse to complete the connection and show 'this site can't be reached,' sometimes alongside a certificate warning first. Modern sites redirect all traffic to https, so a broken certificate effectively blocks the whole site rather than a single page. As a visitor you cannot fix this; only the site owner can renew or repair the certificate. As an owner, keep certificates on auto-renewal so they cannot silently expire, and confirm the certificate covers every hostname you serve, including the www and non-www variants. Because a valid certificate is now essential rather than optional, certificate management is part of the protection our /services/website-security page maintains, ensuring a lapsed certificate never quietly takes a working site offline and leaves visitors staring at an error they cannot resolve themselves.
What to do if it's your own website #
When the site throwing the error is yours, treat it as a potential outage and move methodically. Start by confirming it is truly down for everyone using an external monitor rather than your own browser, then check the specific Chrome code, since ERR_NAME_NOT_RESOLVED points to DNS or a domain lapse while ERR_CONNECTION_REFUSED points to the server. Verify your domain has not expired and that its DNS records and nameservers are correct, then check your hosting dashboard for resource limits, crashes, or a stalled maintenance window. Review server error logs to see which service failed. If your SSL certificate expired, renew it, because a broken secure redirect can also trigger this screen. Recurring outages usually mean underpowered hosting or a fragile configuration rather than bad luck. Our /services/website-rescue page exists for exactly these emergencies, and moving to steadier infrastructure plus proactive monitoring, which you can scope with a /free-website-audit, is the durable fix rather than repeatedly restarting a struggling server.
FAQ
Why does Chrome say 'This site can't be reached'?
Because the browser could not establish a working connection to the server before loading any content. The cause is usually a network drop, a DNS failure, an expired or mistyped domain, a firewall or VPN block, or the host being down. The small code beneath the headline, such as ERR_CONNECTION_TIMED_OUT, tells you which.
Is 'This site can't be reached' a problem with my computer or the website?
It can be either. Test by opening the same address on another device using a different network, like your phone on mobile data. If it loads there, the fault is local to your first device or network. If it fails everywhere, the website or its host is down.
How do I fix 'This site can't be reached' quickly?
Reload the page, then try an incognito window to rule out cache and extensions. Restart your router, disable any VPN, and switch to a public DNS resolver like 8.8.8.8. Check the address for typos. If it still fails, test from another network to confirm whether the site itself is down.
Does this error mean my website is hacked?
Not usually. It most often signals a connection, DNS, or hosting problem rather than a compromise. However, an expired SSL certificate, a malicious redirect, or a blocked server can produce it. If you see it alongside strange redirects or warnings, run a security review before assuming it is only a routine outage.
Can an expired domain cause 'This site can't be reached'?
Yes. If your domain registration lapses, its DNS stops resolving and browsers cannot find the server, typically showing ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN. Renewing the domain and confirming the nameservers and records are correct restores access, though DNS changes can take up to 48 hours to propagate fully across the internet.
Why does the site load on my phone but not my computer?
That points to a local issue on the computer or its network, not the website. Likely culprits include a stale DNS cache, a VPN or proxy, a firewall or antivirus block, or an interfering browser extension. Flush DNS, disable the VPN, try incognito mode, and switch networks to find the specific cause.
How Local Web Advisor checks this for you
Is your own website getting web tech right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for web tech and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?