Skip to content

How to Fix "This Site Can't Be Reached" Errors

Updated November 16, 2026 · 5 min read

"This site can't be reached" is Chrome's way of saying it couldn't even start a conversation with the website. Safari says "Safari can't find the server" or "Safari can't open the page", and Edge says "Hmm… can't reach this page". The wording differs, but the causes and fixes are mostly the same.

Quick answer

First, check whether the site is up for everyone using the Is It Down Everywhere? checker. If it's down, wait. If it's up, the problem is on your side: reload the page, try a private window, restart your Wi-Fi or router, flush your DNS cache, switch to a public DNS server such as 1.1.1.1 or 8.8.8.8, and turn off any VPN, proxy or security extension that might be interfering.

Step 0: Make sure it's not just the site

Before changing anything on your device, spend ten seconds checking the site from outside your network. If our check shows it's down, nothing below will help, and you can save yourself the effort. If it's up, carry on. Our guide on telling whether a site is down for everyone or just you goes into more detail.

What the error codes mean

The small grey code under the message tells you where things went wrong.

Error What happened Most likely fix
DNS_PROBE_FINISHED_NXDOMAIN / ERR_NAME_NOT_RESOLVED The domain name couldn't be looked up. Check spelling, flush DNS, change DNS server
DNS_PROBE_FINISHED_NO_INTERNET Your device has no working internet connection. Reconnect Wi-Fi, restart router
DNS_PROBE_POSSIBLE / DNS_PROBE_FINISHED_BAD_CONFIG Your DNS settings are broken or unreachable. Change DNS server, reset network
ERR_CONNECTION_REFUSED The server, or something in between, said "no". Disable proxy/VPN, check firewall
ERR_CONNECTION_TIMED_OUT Nothing answered at all. Check network, firewall, or wait if the site is down
ERR_CONNECTION_RESET The connection started and was cut off. Disable VPN or security software, try another network
ERR_SSL_PROTOCOL_ERROR A secure connection couldn't be set up. Check your device's date and time, try another network

Fixes that work everywhere

Work through these in order. Most problems are solved by step 4.

  1. Check the address. A single typo in a domain gives you an NXDOMAIN error. Try typing just the domain, such as example.com, without anything after it.
  2. Reload, then try a private window. Private or incognito mode ignores most extensions and cached data.
  3. Try another browser or device. If the site works on your phone but not your laptop, the problem is on the laptop.
  4. Restart your router and device. Unplug the router for 30 seconds. Restart your computer or phone too.
  5. Turn off VPNs, proxies and security extensions temporarily. These sit between you and every site and are a common cause of refused or reset connections.
  6. Flush your DNS cache and switch DNS server. This fixes most DNS_PROBE errors. We've written a step-by-step DNS guide for every platform.
  7. Check your device's date and time. A clock that's far off makes secure connections fail.
  8. Try a different network. Mobile data versus Wi-Fi is the fastest test. See why a site might work on one and not the other.

Browser-specific fixes

Chrome

  1. Go to chrome://net-internals/#dns and click Clear host cache.
  2. Go to chrome://net-internals/#sockets and click Flush socket pools.
  3. Open Settings → Privacy and security → Security and check Use secure DNS. Try switching it on with a provider like Cloudflare or Google, or off if it's already on with a custom provider.
  4. Clear browsing data for the last hour (cookies and cached files).

Safari

  1. In Safari → Settings → Privacy, choose Manage Website Data, find the site and remove it.
  2. Turn off content blockers for the site via the aA menu on iPhone or Safari → Settings for This Website on a Mac.
  3. If you use iCloud Private Relay, try turning it off temporarily (Settings → your name → iCloud → Private Relay).

Edge

  1. Go to edge://net-internals/#dns and click Clear host cache.
  2. In Settings → Privacy, search, and services, check the Use secure DNS option in the Security section.
  3. Edge's tracking prevention set to Strict can occasionally break sites, so try Balanced.

Operating system fixes

Windows

  1. Open Command Prompt as administrator and run:
    ipconfig /flushdns
    ipconfig /release
    ipconfig /renew
    netsh winsock reset
    
  2. Restart your PC.
  3. Still stuck? Go to Settings → Network & internet → Advanced network settings → Network reset. This reinstalls your network adapters, so you'll need to rejoin Wi-Fi afterwards.

macOS

  1. Open Terminal and run:
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    
  2. In System Settings → Network → Wi-Fi → Details → TCP/IP, click Renew DHCP Lease.
  3. Check System Settings → Network → Filters (or VPN and proxies) for anything you don't recognise.

iPhone and iPad

  1. Toggle Airplane Mode on for ten seconds, then off. This clears the DNS cache.
  2. Forget the Wi-Fi network and rejoin it.
  3. As a last resort: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. You'll need to re-enter Wi-Fi passwords.

Android

  1. Toggle Airplane mode on and off.
  2. Check Settings → Network & internet → Private DNS. If it's set to a hostname that isn't working, switch to Automatic or try one.one.one.one or dns.google.
  3. As a last resort: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. Menu names vary slightly between phone makers.

When none of this works

If the site is up on our checker, you've tried another browser, another device and another network, and it still fails on one particular connection, the site is probably being blocked on that network. That can happen at work, at school, on public Wi-Fi, through your provider or at a national level. Our guide on what to do when a website is blocked covers your options.

If the site is down on our checker, it's not you. Bookmark the site's status page here, check back in a few minutes, and read how outages happen while you wait. More questions? See the FAQ.