How to Fix “This Site Can’t Be Reached” in Chrome & More

What Does “This Site Can’t Be Reached” Mean?

The message means your browser tried to connect to a website but failed before the page could load. Chrome may show the main message along with a smaller error code, and that little code is often the real clue.

Common Chrome Error Codes You May See

DNS_PROBE_FINISHED_NXDOMAIN usually means the browser cannot find the domain name. This can happen when the URL is typed incorrectly, the DNS resolver is having trouble, or the website’s DNS records are missing or misconfigured.

ERR_NAME_NOT_RESOLVED also points to a DNS lookup problem. In plain English, Chrome asked, “Where does this website live?” and DNS shrugged.

ERR_CONNECTION_TIMED_OUT means Chrome waited for the website to respond, but the response took too long. The site may be down, your connection may be unstable, or a firewall could be blocking the request.

ERR_CONNECTION_REFUSED means the server rejected the connection. This can happen when a website is offline, misconfigured, or blocking certain traffic.

ERR_INTERNET_DISCONNECTED is the least mysterious of the bunch. Your device is not connected to the internet, or the connection is too broken to be useful.

Quick Checklist Before You Change Settings

Before diving into DNS commands and browser settings, start with the simple stuff. It may feel too easy, but the internet has a proud tradition of being fixed by turning things off and on again.

1. Check the URL

Look carefully at the web address. A missing letter, extra dot, wrong domain ending, or accidental space can trigger a Chrome site error. For example, typing goggle.com instead of google.com may send you somewhere unexpected or nowhere at all.

2. Try Another Website

If every website fails, your internet connection is probably the issue. If only one website fails, the problem may be with that specific site, its domain, or your browser’s stored data for that page.

3. Try Another Browser or Device

Open the same website in Edge, Firefox, Safari, or your phone’s browser. If it works elsewhere, Chrome may be the problem. If it fails everywhere on the same Wi-Fi, your router, DNS, or internet provider may be involved.

4. Restart Your Router and Device

Restart your computer, phone, and router. Unplug the router for about 30 seconds, plug it back in, and wait until the connection fully returns. This clears temporary network issues and gives your devices a fresh start.

How to Fix “This Site Can’t Be Reached” in Chrome

Fix 1: Clear Chrome Cache and Cookies

Chrome stores cached files, cookies, and site data to make websites load faster. Usually, that is helpful. Occasionally, it is like keeping a drawer full of old receipts and calling it “organization.” Corrupted or outdated browser data can stop a site from loading properly.

To clear Chrome browsing data:

1. Open Chrome.
2. Click the three-dot menu in the top-right corner.
3. Go to Settings.
4. Select Privacy and security.
5. Click Delete browsing data or Clear browsing data.
6. Choose Cached images and files.
7. Select Cookies and other site data if the issue is limited to one website.
8. Click Delete data.

Be aware that deleting cookies may sign you out of websites. That is normal, not a personal betrayal by your browser.

Fix 2: Open the Site in Incognito Mode

Incognito Mode disables many stored browsing elements and can help you test whether the problem is caused by cookies, cache, or extensions.

Press Ctrl + Shift + N on Windows or Command + Shift + N on Mac. Then open the website again. If it works in Incognito Mode, the issue is likely related to Chrome extensions or stored site data.

Fix 3: Disable Chrome Extensions

Extensions can improve Chrome, but a bad VPN extension, ad blocker, privacy tool, coupon finder, or “make your browser 900% faster” add-on can also break websites. Some extensions interfere with DNS, scripts, redirects, or secure connections.

To test extensions:

1. Type chrome://extensions into the address bar.
2. Turn off all extensions temporarily.
3. Restart Chrome.
4. Try the website again.

If the site loads, turn extensions back on one at a time until the error returns. The last extension you enabled is probably the troublemaker. Remove it, update it, or keep it disabled for that website.

Fix 4: Flush the DNS Cache

Your device keeps a DNS cache so it can remember where websites are located. When that cache becomes outdated or incorrect, Chrome may show DNS_PROBE_FINISHED_NXDOMAIN, ERR_NAME_NOT_RESOLVED, or another site loading error.

On Windows:

1. Search for Command Prompt.
2. Right-click it and choose Run as administrator.
3. Type this command and press Enter:

On macOS:

1. Open Terminal.
2. Run the following command:

After flushing DNS, restart the browser and try the website again.

Fix 5: Change Your DNS Server

Your internet provider usually assigns a DNS server automatically. Most of the time, that works. Sometimes, however, your default DNS server is slow, down, or struggling to resolve a domain. Switching to a reliable public DNS service can fix the problem.

Popular DNS options include:

• Google Public DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1
• Quad9 DNS: 9.9.9.9 and 149.112.112.112

On Windows, go to Settings > Network & Internet, open your active network adapter, and edit DNS server assignment. On macOS, go to System Settings > Network, choose your connection, and edit DNS under details or advanced settings.

After changing DNS, restart the browser. If you are on a school, office, or managed network, ask the administrator before changing network settings.

Fix 6: Reset the Windows Network Stack

If Chrome still cannot reach websites, Windows may need a deeper network reset. This can fix damaged TCP/IP settings, DNS resolver issues, and connection problems that survive a simple restart.

Open Command Prompt as administrator, then run these commands one at a time:

Restart your computer after running the commands. This step is especially useful when multiple browsers cannot load websites, not just Chrome.

Fix 7: Check Proxy Settings

A proxy routes your internet traffic through another server. If the proxy setting is wrong, outdated, or left over from old software, websites may stop loading.

On Windows:

1. Open Settings.
2. Go to Network & Internet.
3. Select Proxy.
4. Turn off manual proxy settings unless you intentionally use one.

In Chrome, you can also go to Settings > System and open your computer’s proxy settings from there. If you are using a company or school device, do not remove required proxy settings without permission.

Fix 8: Turn Off VPN Temporarily

VPNs can protect privacy and help with secure remote access, but they can also cause DNS conflicts, routing problems, or blocked connections. Temporarily disconnect your VPN and try the website again.

If the site works with the VPN turned off, switch VPN servers, update the VPN app, or contact the VPN provider. Avoid using VPNs to bypass network rules on managed school, office, or public networks.

Fix 9: Check Firewall and Antivirus Web Protection

Security software can sometimes block legitimate sites by mistake, especially if it includes web shield, HTTPS scanning, DNS filtering, or parental control features. Temporarily pause only the web protection component if your security software allows it, then test the site.

If the page loads after disabling a security feature, do not leave protection off permanently. Add the website to the allow list only if you trust it, update your security software, or contact support for the tool you use.

Fix 10: Review Chrome Secure DNS Settings

Chrome includes a Secure DNS feature that can use encrypted DNS lookups. This is generally helpful, but a mismatch between Chrome’s DNS provider and your network can occasionally cause loading problems.

To check it:

1. Open Chrome Settings.
2. Go to Privacy and security.
3. Click Security.
4. Find Use secure DNS.
5. Try Automatic, or choose a trusted DNS provider.

You can temporarily turn Secure DNS off for testing, but turning it back on later is usually better for privacy and security.

Fix 11: Reset Chrome Settings

If Chrome has been heavily customized, a reset can remove bad settings without deleting your bookmarks, history, or saved passwords.

Go to Settings > Reset settings, then choose Restore settings to their original defaults. This disables extensions, resets startup pages, clears temporary site settings, and returns Chrome to a cleaner state.

Fix 12: Update Chrome and Your Operating System

An outdated browser can struggle with newer web standards, security certificates, and network behavior. Open Chrome’s three-dot menu, go to Help > About Google Chrome, and install any available update.

Also update Windows, macOS, Android, or iOS. Network drivers, certificate stores, and security components are often updated through the operating system.

How to Fix the Error in Edge, Firefox, Safari, and Other Browsers

The message changes from browser to browser, but the core fixes are similar. Edge uses Chromium like Chrome, so cache, extensions, proxy settings, DNS, and network resets apply almost the same way.

Microsoft Edge

In Edge, you may see “Hmm… can’t reach this page.” Clear browsing data, disable extensions, check proxy settings, and test InPrivate Mode. Because Edge and Chrome share the Chromium foundation, many Chrome fixes also work in Edge.

Firefox

Firefox may show “Server not found” or “Unable to connect.” Try Troubleshoot Mode, clear cookies and cache, check proxy settings under Network Settings, and test whether DNS over HTTPS is causing a conflict.

Safari

Safari may say it cannot open the page because the server cannot be found. Clear website data, test another network, disable content blockers temporarily, check macOS DNS settings, and make sure the date and time are correct.

When the Website Itself Is the Problem

Sometimes your browser is innocent. Yes, Chrome has a lot of tabs open and questionable life choices, but this one may not be its fault.

The Website May Be Down

If other sites load but one website does not, the server may be offline, overloaded, or under maintenance. Try again later or check the website’s official social media or status page if available.

The Domain May Have DNS Problems

If you own the website, check whether the domain is expired, nameservers are correct, and DNS records exist for both the root domain and the www version. Missing A, AAAA, or CNAME records can trigger DNS errors.

DNS Changes May Still Be Propagating

When a website owner changes DNS records, the update may take time to spread across DNS resolvers. During that window, some visitors can access the site while others see errors. This is annoying but common.

The Server May Be Blocking Traffic

Firewalls, hosting security rules, rate limits, or misconfigured CDN settings can block visitors. Website owners should check hosting logs, firewall rules, CDN DNS settings, and SSL configuration.

Extra Tips for Website Owners

If visitors are reporting “This site can’t be reached”, do not assume it is only their Wi-Fi. Website-side issues can create the same error.

Check Your DNS Records

Make sure your domain has the correct records. Your root domain, such as example.com, should point to the right server or service. Your www subdomain should also resolve properly.

Check Nameservers

If you use a DNS provider or CDN, confirm that your domain registrar points to the correct nameservers. A mismatch can make the domain disappear from the internet like it entered witness protection.

Check SSL and HTTPS Redirects

Broken HTTPS redirects, expired certificates, or incorrect server rules can stop pages from loading. Make sure the HTTP version, HTTPS version, root domain, and www version all redirect cleanly.

Check Hosting and CDN Status

If your host or CDN is having an outage, the fix may be on their side. Review your provider’s status dashboard and support notices.

My Practical Experience Fixing “This Site Can’t Be Reached”

After dealing with this error across personal laptops, office networks, client websites, and the occasional family “the internet is broken” emergency, one pattern stands out: the error message sounds big, but the cause is often small.

The most common real-world fix is still the boring one: restart the router and clear DNS. Many people jump straight into advanced settings, but a stale DNS cache or tired router can make Chrome act as if half the web has vanished. I have seen websites fail in Chrome, work on a phone using mobile data, then work again on the computer after a simple DNS flush. That is why I always test the same site on another device or network before making big changes.

Another common situation involves browser extensions. Privacy extensions, ad blockers, VPN add-ons, and script blockers can be useful, but they can also break login pages, payment pages, dashboards, and media-heavy websites. The easiest test is Incognito Mode. If the site works there, extensions or stored site data are high on the suspect list. Think of Incognito as Chrome wearing a plain T-shirt and pretending it has no baggage.

DNS server problems are also surprisingly frequent. Some internet providers have DNS outages or slow resolution during peak hours. Switching to a public DNS provider often solves the problem quickly. However, on managed networks, especially schools and workplaces, changing DNS can interfere with required filtering, internal sites, or access rules. In those cases, the best move is to contact the network administrator rather than fighting the system like a tiny browser gladiator.

For website owners, the biggest lesson is to check both versions of the domain: the root domain and the www version. A site may work at www.example.com but fail at example.com, or the other way around. I have also seen new websites show DNS errors simply because the domain records were incomplete or the nameservers had not fully updated. When launching a site, it is smart to test DNS records, redirects, SSL, and CDN settings before announcing the site to the world.

Security software can be another sneaky cause. Antivirus tools with web protection features sometimes block sites that are actually safe. The right approach is not to turn off protection forever. Instead, test temporarily, update the software, and only allowlist a site if you are confident it is legitimate. If the browser is warning about a suspicious site, do not ignore that warning just because you really want to click something. The internet contains wonderful things, but it also contains digital raccoons in trench coats.

Finally, patience matters. If one website is down for everyone, no amount of cache clearing will bring it back. The best troubleshooting habit is to narrow the problem: one site or all sites, one browser or all browsers, one device or all devices, one network or every network. Once you answer those questions, the fix becomes much clearer.

Final Thoughts

The “This site can’t be reached” error in Chrome looks frustrating, but it is rarely the end of the story. Start with simple checks: confirm the URL, test another website, restart your router, and try another browser. Then move into stronger fixes such as clearing Chrome cache, disabling extensions, flushing DNS, changing DNS servers, checking proxy or VPN settings, and resetting the network stack.

If the issue appears only on one website, the website may be down or misconfigured. If it appears across every website, your device, router, DNS, firewall, or internet connection is more likely responsible.

The best troubleshooting method is calm, organized, and slightly suspicious of everything. Test one change at a time, avoid random settings chaos, and keep notes if you are fixing a business website. With the right steps, Chrome can usually stop shouting “This site can’t be reached” and get back to doing what browsers do best: opening tabs you will definitely read later.