"This Site Can't Be Reached" — How to Fix It

"This site can't be reached" (Chrome) or "Hmm, can't reach this page" (Edge) is a deliberately vague message — your browser tried to connect and failed, but it doesn't tell you exactly why. The cause could be a DNS lookup failure, a connection reset, the website's own server being down, or something local on your machine.

Step 1: figure out the scope of the problem

• Try the same site in a different browser. If it loads fine elsewhere, the problem is specific to your original browser (cache, extensions, settings) rather than your network.
• Try a different website entirely. If every site fails, the problem is more likely network-wide (Wi-Fi, router, DNS) rather than specific to one site.
• Try on a different device on the same network (phone on Wi-Fi, for example). If it works there, the issue is specific to your one computer rather than your whole network or ISP.
• Check if the site is actually down for everyone. Use a service like downdetector.com to check if the specific website itself is having an outage — if so, there's nothing to fix on your end, just wait it out.

Fix 1: flush your DNS cache

One of the most common and effective fixes — outdated DNS records can cause exactly this error even when the site is fine and your internet connection works otherwise:

1. Press Windows key, type cmd, right-click Command Prompt and choose Run as administrator
2. Type ipconfig /flushdns and press Enter
3. Close Command Prompt and try the site again

Fix 2: clear browser cache and cookies

1. In Chrome or Edge, press Ctrl + Shift + Delete
2. Select "Cached images and files" (and optionally cookies, though this will sign you out of sites)
3. Choose a time range — "All time" for a thorough clear
4. Click Clear data, then restart the browser and try again

Fix 3: try a different DNS server

Your ISP's default DNS servers occasionally have issues. Switching to a public DNS provider like Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1) can resolve persistent site-loading problems:

1. Go to Settings → Network & internet, click your active connection (Wi-Fi or Ethernet)
2. Find DNS server assignment and click Edit
3. Switch from "Automatic (DHCP)" to "Manual," enable IPv4, and enter 8.8.8.8 as preferred and 8.8.4.4 as alternate
4. Save, then try the site again

Fix 4: check for proxy or VPN interference

An incorrectly configured proxy can cause exactly this error for some or all sites. Check Settings → Network & internet → Proxy and confirm nothing unexpected is enabled. If you're using a VPN, try temporarily disconnecting it to see if that resolves the issue.

Fix 5: temporarily disable antivirus/firewall to test

Security software occasionally blocks legitimate traffic, particularly after a definition update introduces a false positive. Temporarily disable third-party antivirus or firewall software (re-enable it immediately after testing) to see if that's the cause — if the site loads with it off, you'll need to add an exception for the specific site rather than leaving protection off long-term.

If it's truly network-wide (every site, every browser, every device)

At this point the issue is likely with your router, modem, or ISP rather than anything on your computer:

1. Restart your router (unplug for 30 seconds, plug back in)
2. If the problem persists across all devices, contact your ISP — there may be an outage or line issue on their end