Chrome’s “This Site Can’t Be Reached” message usually means the browser cannot complete the connection to the website you are trying to open. The cause can be as simple as a bad internet connection, or it can involve DNS, proxy, firewall, or browser settings.
The good news is that you can usually narrow it down quickly by testing whether the problem affects one site, several sites, or your whole connection.
1. Check Whether the Problem Is With One Website or Your Connection
Before changing browser settings, find out whether Chrome is the only thing failing. Try opening a different website, or open the same site in another browser. If other sites work, the issue is more likely with the specific website, its DNS record, or your local browser/network configuration.
- If only one site fails, the site may be temporarily down or misconfigured.
- If every site fails, the problem is more likely your internet connection, DNS, proxy settings, or firewall.
- If the site opens on your phone using mobile data but not on your PC, the problem is probably on the computer or router side.
2. Flush Chrome’s DNS and Clear the Browser Cache
Chrome stores DNS lookups and cached data to speed up browsing, but stale entries can prevent a site from loading correctly. Clearing that data can force Chrome to request fresh connection information.
- Open Chrome and type chrome://net-internals/#dns in the address bar, then press Enter.
- Click Clear host cache.
- Next, open chrome://net-internals/#sockets.
- Click Flush socket pools.
- Close and reopen Chrome, then try the site again.
3. Change or Reset Your DNS Server
If Chrome cannot resolve the website name into an IP address, you may see the “This Site Can’t Be Reached” message. Switching to a reliable DNS provider often fixes this faster than waiting for your current DNS server to recover.
- Open your network adapter settings in Windows.
- Open the properties for your active connection.
- Find Internet Protocol Version 4 (TCP/IPv4).
- Set the DNS server manually and try a trusted public DNS service such as Google DNS or Cloudflare DNS.
- Save the change and reload the website.
4. Turn Off Proxy Settings or VPN Temporarily
Proxy servers and VPNs can cause connection failures if they are misconfigured, overloaded, or blocked by the destination site. Disabling them temporarily helps you tell whether they are the cause.
- If you use a VPN app, disconnect it and test the site again.
- Open Windows proxy settings and make sure no unwanted proxy is enabled.
- If your browser has a proxy extension, disable it temporarily.
- Reload the page after each change so you can identify which setting caused the problem.
5. Reset Your Network Stack in Windows
If Windows networking components have become corrupted or stuck, Chrome may be unable to reach websites even when the connection appears normal. Resetting the network stack can clear these issues.
- Open Command Prompt as an administrator.
- Run ipconfig /flushdns.
- Run netsh winsock reset.
- Run netsh int ip reset.
- Restart the computer after the commands complete.
6. Check Firewall, Antivirus, and Router Restrictions
Security software and router features can block Chrome from reaching certain sites, especially if the site is flagged incorrectly or if web filtering is enabled. A strict firewall rule can also stop outbound traffic even when the internet connection itself is working.
- Temporarily pause antivirus web protection if you trust the site and want to test.
- Check whether Windows Defender Firewall has blocked Chrome or the site’s port.
- Look for parental controls, content filters, or safe browsing features in your router.
- Test the site on another network, such as a phone hotspot, to see whether your home network is the cause.
When the Error Is Actually a Website Problem
Sometimes the fix is not on your computer at all. If a site is down, its DNS records are broken, or its server is refusing connections, Chrome may show “This Site Can’t Be Reached” no matter what you do locally.
- The site is unreachable in every browser and on every device.
- Online status tools show the site is down.
- The site only fails for certain regions or internet providers.
- The site recently changed domains or hosting and may still be propagating DNS changes.
If you suspect the website is the problem, wait and try again later, or contact the site owner if possible.
Which Fix Should You Try First?
If you want the fastest path, start with checking whether the site works elsewhere, then clear Chrome’s DNS cache, then try a different DNS server. If the error affects many sites, move on to proxy settings, network resets, and firewall checks. That order solves the most common causes without making unnecessary changes.
