Chrome This Site Can’t Be Reached: How to Fix It

Yes—Chrome’s “This site can’t be reached” error is often fixable by checking the address, connection, browser settings, or DNS. Start with the quick checks below; if other websites work but one site does not, the problem may be with that site or its network rather than Chrome.

What the error means

Chrome displays “This site can’t be reached” when it cannot establish a connection to the requested website. The message is a broad symptom, not a diagnosis: possible causes include a mistyped web address, a lost internet connection, a DNS lookup failure, a proxy or VPN problem, a firewall rule, or a website that is temporarily unavailable.

Look at any smaller text below the main message. Chrome may show a clue such as “DNS_PROBE_FINISHED_NXDOMAIN,” “ERR_CONNECTION_TIMED_OUT,” or “ERR_CONNECTION_REFUSED.” These names point toward different kinds of failures, but they do not prove a particular cause. For example, a timeout can result from a slow or unreachable server, a network filter, or an unstable connection.

Try these quick checks first

Check the address. Look for misspellings, extra punctuation, or an incorrect domain ending. If you followed a link, try entering the site’s main address yourself.
Open another site. If several unrelated sites fail, suspect the device or internet connection. If only one fails, the website, its address, or a network restriction may be responsible.
Reload and wait briefly. A temporary interruption can clear on its own. Avoid repeatedly refreshing a site that is already responding slowly.
Check your connection. Confirm Wi-Fi is connected or an Ethernet cable is seated. If available, try another device on the same network and the affected device on a different trusted network.
Restart the browser and device. Close Chrome fully, reopen it, and restart the computer or phone if the problem persists. Restarting can clear a temporary software or network state.

These checks help separate a browser problem from a connection problem. If every device on the same home network fails to reach the same site, changing Chrome settings is unlikely to be the first useful step.

Work through Chrome and network fixes

If the quick checks do not help, try these steps in order. Menu labels can vary slightly by operating system and Chrome release.

Use an Incognito window. Open Chrome’s menu and choose New Incognito window, then visit the site. If it works there, an extension or stored site data may be involved. Incognito is a diagnostic check, not a guarantee of privacy from websites or network administrators.
Temporarily disable extensions. Open Extensions from Chrome’s menu, or enter chrome://extensions in the address bar. Turn off extensions and test again. Re-enable them one at a time to identify a conflict. Do not disable security tools permanently.
Clear data for the affected site. In Chrome settings, open Privacy and security and look for site data or browsing data controls. Removing cookies and cached files can sign you out or reset preferences, so clear only what is needed and understand the prompts before confirming.
Check VPN and proxy settings. If you use a VPN or proxy, disconnect it briefly if you are allowed to do so, then test the site. On a managed work or school device, ask the administrator before changing proxy settings; they may be required for access.
Update Chrome. Open the Chrome menu and select Help > About Google Chrome. Install an available update and relaunch the browser. If the page still fails, test another browser to see whether the issue is specific to Chrome.
Restart the router if the network seems at fault. If multiple devices have connection trouble, restart the router using its normal power procedure, then allow it to reconnect. Do not reset it to factory settings unless you are prepared to configure the network again.

DNS, firewall, and security software

DNS translates a domain name, such as example.com, into the network address needed to connect. A DNS error can occur if the domain is typed incorrectly, the DNS service is having trouble, or the device or network has stale or unsuitable DNS settings. Restarting the device or router may refresh the connection. Some operating systems also provide a way to clear the DNS cache, but the command and steps differ; use instructions for your exact operating system rather than copying commands from an unrelated guide.

Firewall, antivirus, parental-control, and workplace filtering software can block a site or its connection. Check whether the software reports a block, and use its normal settings or contact its administrator. Do not turn off protection broadly as a routine fix, and do not add an unfamiliar site to an allowlist just to make the warning disappear. A site can be unreachable for a legitimate security or policy reason.

Chrome’s “This site can’t be reached” message is not the same as a certificate warning or a malware warning. If Chrome displays a security warning, read and follow that warning rather than treating it as an ordinary connection failure. Do not bypass security warnings to access a page that handles passwords, payments, or private information.

How to tell whether the website is down

Try the site on another device and, if practical, a different network. If it fails everywhere while other sites work, the service may be offline, the domain may have changed, or access may be restricted in your region or organization. Check the site owner’s official status page or announcements if available. A third-party outage checker can offer another clue, but it may be outdated or unable to test the same route your connection uses.

If the site works on mobile data but not on your home Wi-Fi, investigate the router, DNS, or network filtering. If it works in another browser but not Chrome, focus on Chrome extensions, stored site data, or browser configuration. These comparisons narrow down the cause without assuming that the website itself is broken.

When to contact support

Contact the website’s support team if only its service fails across devices and networks, especially if you can provide the exact address, the time of the problem, and the full error details. Contact your internet provider if many sites fail across devices on the same connection after basic restarts. For a work or school network, contact the administrator instead of changing managed settings.

When reporting the issue, include the Chrome error text and whether the site works in another browser, on another device, or on another network. Avoid sending passwords, one-time codes, or private account information in a support request.

Frequently Asked Questions

Why does Chrome say “This site can’t be reached” when my internet works?
Internet access can be working while a particular domain, DNS lookup, route, or site server is unavailable. Check other websites and devices, then compare the affected site on another network.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?
Chrome could not find a DNS record for the domain it tried to visit. Check the spelling and domain ending first; if the address is correct, the DNS information or domain may be unavailable.

Why does the site work in Incognito but not in a normal window?
An extension or stored browser data may be affecting the normal session. Disable extensions one at a time and consider clearing data for that site, noting that this may sign you out.

Can I fix this error by changing DNS?
Sometimes DNS is the cause, but changing DNS is not a universal fix. First check the address, connection, and whether the issue affects other devices. On managed networks, consult the administrator before changing network settings.

Is “This site can’t be reached” proof that a website is unsafe?
No. It means Chrome could not connect, not that it has judged the site safe or unsafe. Treat separate certificate, malware, or deceptive-site warnings seriously and do not bypass them.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →