**By Piyush** | November 2026 | 7 min read
—
Google Chrome displays the “This site can’t be reached” error when the browser fails to establish a Transmission Control Protocol (TCP) connection or resolve a domain through the Domain Name System (DNS). The issue commonly stems from corrupted internal browser host caches, stale operating system DNS records, or conflicting transport layer protocols.
Chrome maintains an independent internal network cache separate from Windows or macOS network stacks. Standard page refreshes fail to clear these internal socket pools, leaving users stranded on error codes like `DNS_PROBE_FINISHED_NXDOMAIN` or `ERR_NAME_NOT_RESOLVED`.
This comprehensive troubleshooting guide delivers 6 verified solutions to clear Chrome’s internal network state, flush system resolver caches, and restore connectivity in under five minutes.
—
Chrome Network Diagnostics: Common Error Codes & Causes
The table below outlines the primary error codes linked to site unreachable errors alongside their exact root causes:
| Chrome Error Code | Technical Root Cause | Primary Resolution Vector |
|---|---|---|
| **DNS_PROBE_FINISHED_NXDOMAIN** | Domain does not exist or DNS resolver failed | Flush DNS cache & switch to Public DNS |
| **ERR_NAME_NOT_RESOLVED** | IP address could not be mapped from hostname | Clear Chrome Host Cache & restart DNS Client |
| **ERR_CONNECTION_TIMED_OUT** | Web server took too long to acknowledge TCP SYN packet | Reset Winsock catalog & disable QUIC protocol |
| **ERR_CONNECTION_REFUSED** | Target server rejected connection request | Disable local firewall/antivirus filtering |
| **ERR_SSL_PROTOCOL_ERROR** | Handshake failed due to certificate or cipher mismatch | Synchronize system clock & clear SSL state |
—
6 Proven Ways to Fix “This site can’t be reached”
Follow these diagnostic steps sequentially to isolate and resolve the underlying network failure:
1. **Clear Chrome’s Internal DNS Host Cache and Flush Sockets**: Open a new tab in Google Chrome, navigate to `chrome://net-internals/#dns`, and click the **Clear host cache** button. Next, click on the **Sockets** tab on the left sidebar (or go directly to `chrome://net-internals/#sockets`), click **Flush socket pools**, and restart your browser.
2. **Disable Experimental QUIC Protocol in Chrome Flags**: Type `chrome://flags` into Chrome’s address bar and press Enter. Search for **Experimental QUIC protocol** in the top search field, set its dropdown status from *Default* to **Disabled**, and click the blue **Relaunch** button at the bottom of the screen.
3. **Flush Operating System DNS and Reset Winsock via Command Prompt**: Press the Windows Key, type `cmd`, right-click **Command Prompt**, and select **Run as administrator**. Execute `ipconfig /flushdns`, followed by `netsh winsock reset` and `netsh int ip reset`. Reboot your computer to apply the TCP/IP stack reinitialization.
4. **Switch to High-Speed Public DNS Servers**: Press `Win + R`, type `ncpa.cpl`, and press Enter. Right-click your active Wi-Fi or Ethernet adapter, select **Properties**, double-click **Internet Protocol Version 4 (TCP/IPv4)**, and select **Use the following DNS server addresses**. Set Preferred DNS to `8.8.8.8` (Google) or `1.1.1.1` (Cloudflare), set Alternate DNS to `8.8.4.4` (Google) or `1.0.0.1` (Cloudflare), and click **OK**.
5. **Disable Secure DNS (DNS-over-HTTPS) Conflicts**: Open Chrome Settings by navigating to `chrome://settings/security`. Scroll down to the Advanced section and toggle **Use secure DNS** to **Off**. Incompatible third-party firewalls and enterprise proxies frequently intercept encrypted DoH packets, creating artificial connection timeouts.
6. **Purge Browser Cookies and Cached Web Data**: Press `Ctrl + Shift + Delete` on Windows or `Cmd + Shift + Delete` on Mac to open the Clear Browsing Data dialog. Select **All time** as the time range, check **Cookies and other site data** and **Cached images and files**, and click **Clear data**.
—
Video Tutorial: Step-by-Step Chrome Network Repair
Watch the complete video walkthrough below demonstrating how to flush internal socket pools and reset Windows network adapters:
—
Advanced Troubleshooting: When Specific Sites Still Fail
If one specific web domain remains unreachable while other sites load effortlessly:
* **Inspect Windows Hosts File**: Open `C:\Windows\System32\drivers\etc\hosts` in Notepad as administrator. Ensure malicious software or obsolete staging entries have not redirected the target domain to `127.0.0.1`. * **Restart the DNS Client Service**: Press `Win + R`, execute `services.msc`, locate **DNS Client**, and ensure the status indicates *Running*. * **Disable Third-Party VPNs & Proxy Extensions**: Ad-blockers and proxy extensions often intercept web requests and fail silently when external routing nodes experience downtime.
For readers troubleshooting mobile connectivity and cellular network data dropouts, examine our guide on fixing Jio 5G network errors and Standalone APN setup.
—
Frequently Asked Questions (FAQs)
Why does Chrome say ‘This site can’t be reached’ but other browsers work?
Chrome maintains an internal socket pool and DNS cache separate from the OS; if these internal buffers become corrupted, Chrome fails while Edge or Firefox continue functioning.
Does clearing Chrome host cache delete my browsing history?
No. Clearing the host cache via chrome://net-internals only purges resolved IP address records; your bookmarks, browsing history, and saved passwords remain untouched.
What is the fastest way to fix DNS_PROBE_FINISHED_NXDOMAIN?
The fastest fix is changing your adapter DNS settings to Cloudflare (1.1.1.1) or Google Public DNS (8.8.8.8) and executing ipconfig /flushdns in Command Prompt.
Why does disabling the QUIC protocol fix connection errors?
QUIC runs over UDP; certain consumer routers, ISP filters, and corporate firewalls throttle or drop UDP web traffic, causing premature connection timeouts.
—
*Did flushing Chrome’s socket pools resolve your connection error? Share your browser version or diagnostic code in the comments below.*