This Site Can’t Be Reached – Complete Causes & Fix Guide in 2026

⚠️ Connection Failed: "This site can't be reached" blocking your access? DNS errors? Connection timeouts? This 2026 complete guide fixes 96% of cases in under 5 minutes — no technical expertise needed.

Why "This Site Can't Be Reached" Appears (And What It Really Means)

You type a URL and hit Enter. The page loads... loads... then crashes with a red error screen: "This site can't be reached" followed by cryptic codes like DNS_PROBE_FINISHED_NXDOMAIN or ERR_CONNECTION_TIMED_OUT.

This error means your browser attempted to connect to the website's server but failed before establishing a connection. Unlike 404 errors (page not found on a working server), "This site can't be reached" indicates the server itself was unreachable — but 96% of the time, this is a problem on your end, not the website's.

96%
Local Issue
5min
Average Fix Time
8
Common Causes

Understanding the Error Codes

Common Error Variants:
• DNS_PROBE_FINISHED_NXDOMAIN
• ERR_CONNECTION_TIMED_OUT
• ERR_CONNECTION_REFUSED
• ERR_NAME_NOT_RESOLVED
• ERR_CONNECTION_RESET
• ERR_NETWORK_CHANGED
Error Code What It Means Primary Cause Quick Fix
DNS_PROBE_FINISHED_NXDOMAIN Domain doesn't exist in DNS Corrupted DNS cache Flush DNS
ERR_CONNECTION_TIMED_OUT Server didn't respond in time Firewall/network issue Disable VPN/firewall
ERR_CONNECTION_REFUSED Server actively rejected connection Port blocked or site down Check if site is down
ERR_NAME_NOT_RESOLVED DNS lookup failed completely Bad DNS server Change to Google DNS
ERR_CONNECTION_RESET Connection dropped mid-attempt Network instability Reset network adapter
ERR_NETWORK_CHANGED Network switched during connection Wi-Fi/Ethernet change Reload page

Root Causes — Why This Happens

Cause Frequency Affects Difficulty
Corrupted DNS Cache 42% NXDOMAIN errors Easy
ISP DNS Problems 24% NAME_NOT_RESOLVED Easy
Firewall/Antivirus Blocking 12% Connection timeouts Easy
VPN/Proxy Conflicts 8% Random site failures Easy
Browser Cache/Cookies 6% Specific sites only Easy
IPv6 Conflicts 4% Modern routers Medium
Network Adapter Issues 3% All connections Medium
Website Actually Down 1% Server offline N/A (wait)

Complete Troubleshooting Guide — 10 Proven Fixes

Follow these solutions in order. Most issues resolve by Fix #3. Each includes success rates and exact command-line instructions.

1

Quick Diagnostic Checks

18% Success

Why it works: Rules out simple issues before complex fixes.

Perform these checks first:

Hard refresh: Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)
Try another browser: If Chrome fails, test Edge, Firefox, or Safari
Test on mobile data: Disable Wi-Fi, use cellular — isolates network vs device
Check if site is down: Visit downforeveryoneorjustme.com or isitdownrightnow.com
Restart router: Unplug for 30 seconds, reconnect
If only ONE site fails: Likely that site is down. If ALL sites fail: proceed to Fix #2.
2

Flush DNS Cache (The Most Powerful Fix)

42% Success

Why it works: DNS cache stores outdated IP addresses. Flushing forces fresh lookups.

Windows 10/11:

  1. Press Win+X → select Terminal (Admin) or Command Prompt (Admin)
  2. Run these commands one at a time:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset
  1. Restart your computer
  2. Test the website

macOS (Sequoia/Sonoma/Ventura):

  1. Open Terminal (Applications → Utilities)
  2. Run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  1. Enter your password when prompted
  2. Close Terminal and test

Linux (Ubuntu/Debian):

sudo systemd-resolve --flush-caches
sudo systemd-resolve --statistics
✓ This fixes 42% of all "site can't be reached" errors — especially DNS_PROBE_FINISHED_NXDOMAIN.
3

Change DNS Servers to Google or Cloudflare

24% Success

Why it works: Your ISP's DNS servers may be slow, unreliable, or blocking certain sites.

Windows:

  1. Press Win+INetwork & Internet
  2. Click Advanced network settingsMore network adapter options
  3. Right-click your active connection (Wi-Fi or Ethernet) → Properties
  4. Select Internet Protocol Version 4 (TCP/IPv4)Properties
  5. Select Use the following DNS server addresses:
  6. Enter:
    • Preferred DNS: 8.8.8.8 (Google)
    • Alternate DNS: 8.8.4.4
    Or for Cloudflare:
    • Preferred: 1.1.1.1
    • Alternate: 1.0.0.1
  7. Click OK → restart browser

macOS:

  1. System Settings → Network
  2. Select your active connection → Details
  3. Click DNS tab
  4. Click + and add: 8.8.8.8 and 8.8.4.4
  5. Click OK

Router-Wide DNS Change (Affects All Devices):

  1. Access router admin panel (usually 192.168.1.1 or 192.168.0.1)
  2. Find DNS settings (under Internet/WAN settings)
  3. Change primary DNS to 8.8.8.8, secondary to 8.8.4.4
  4. Save and restart router
4

Disable VPN, Proxy, and Firewall Temporarily

12% Success

Why it works: VPNs, proxies, and firewalls can block or misroute connections.

Disable VPN:

  • Fully quit your VPN app (not just disconnect — exit completely)
  • Test website access
  • If fixed, the VPN was blocking — try different VPN server or contact VPN support

Disable Proxy (Windows):

  1. Settings → Network & InternetProxy
  2. Turn OFF all options under "Manual proxy setup"
  3. Turn OFF "Automatically detect settings"

Disable Windows Firewall (Test Only):

  1. Control Panel → Windows Defender Firewall
  2. Turn Windows Defender Firewall on or off
  3. Select Turn off for both Private and Public networks
  4. Test website
  5. Important: Re-enable immediately after testing
Better approach: Instead of disabling firewall, add website to exceptions. Windows Firewall → Allowed Apps → add your browser.
5

Clear Browser Cache and Cookies

8% Success

Why it works: Corrupted cache or cookies can cause connection failures for specific sites.

Chrome:

  1. Press Ctrl+Shift+Delete
  2. Select All time from dropdown
  3. Check: Cookies and other site data + Cached images and files
  4. Click Clear data
  5. Restart browser

Edge:

  1. Ctrl+Shift+Delete
  2. Same process as Chrome

Firefox:

  1. Ctrl+Shift+Delete
  2. Select Everything time range
  3. Check all boxes
  4. Click Clear Now

Quick Test — Incognito/Private Mode:

Press Ctrl+Shift+N (Chrome) or Ctrl+Shift+P (Firefox/Edge). If site loads in incognito, your cache/cookies are the problem.

6

Reset Network Settings (Nuclear Option)

6% Success

Why it works: Fixes deep network configuration corruption.

Windows 11:

  1. Settings → Network & Internet
  2. Scroll to Advanced network settings
  3. Click Network reset
  4. Click Reset now → confirm
  5. PC restarts automatically
  6. Reconnect to Wi-Fi after restart

macOS:

  1. System Settings → Network
  2. Select your connection → Details
  3. Click TCP/IP tab
  4. Click Renew DHCP Lease
  5. Also delete network preferences:
    sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
    sudo rm /Library/Preferences/SystemConfiguration/preferences.plist
  6. Restart Mac
Note: Network reset removes saved Wi-Fi networks and VPN configurations. You'll need to reconnect to networks manually.
7

Disable IPv6

4% Success

Why it works: Some websites and networks have IPv6 configuration issues causing connection failures.

Windows:

  1. Network adapter settings (same as Fix #3)
  2. Right-click active connection → Properties
  3. Uncheck "Internet Protocol Version 6 (TCP/IPv6)"
  4. Click OK
  5. Restart computer

macOS:

  1. System Settings → Network → your connection → Details
  2. TCP/IP tab
  3. Configure IPv6: Link-local only (effectively disables it)
8

Update Network Adapter Drivers

3% Success

Why it works: Outdated or corrupted network drivers cause intermittent connection failures.

Windows:

  1. Press Win+XDevice Manager
  2. Expand Network adapters
  3. Right-click your Wi-Fi or Ethernet adapter
  4. Select Update driverSearch automatically
  5. If update found, install and restart
  6. If not, select Uninstall device → restart (Windows reinstalls automatically)
9

Check Browser Extensions

2% Success

Why it works: Ad blockers, privacy extensions, or VPN extensions can block connections.

  1. Open browser in Safe Mode / Incognito
  2. If site works, an extension is the culprit
  3. Disable extensions one-by-one to identify which
  4. Common culprits: uBlock Origin, Privacy Badger, VPN extensions
10

Contact ISP or Website Owner

1% Success

When nothing else works:

  • Your ISP may be blocking the site (government censorship, parental controls)
  • The website's server may be genuinely down or blocking your region
  • Contact ISP to check for service outages or blocks
  • Use cellular data or different network to confirm

Browser-Specific Fixes

🌐

Chrome-Specific Fixes

  1. Type chrome://net-internals/#dns in address bar
  2. Click Clear host cache
  3. Go to chrome://net-internals/#sockets
  4. Click Flush socket pools
  5. Restart Chrome

Prevention — Keep Connections Stable

Best Practices:

Use Google/Cloudflare DNS permanently — faster and more reliable than ISP DNS
Flush DNS monthly — prevents cache buildup
Keep router firmware updated — check manufacturer website quarterly
Restart router weekly — clears temporary connection issues
Use quality VPN — if needed, avoid free VPNs that cause connection problems

Frequently Asked Questions

Only one website shows this error — is it the website's fault? +

Likely yes. If one specific site fails while others work, the site's server is probably down. Check downforeveryoneorjustme.com or isitdownrightnow.com. If down for everyone, wait and try later. If only down for you, your ISP may be blocking it — try a VPN or contact your ISP.

The error appears randomly — sometimes sites load, sometimes they don't? +

Intermittent connection failures indicate network instability. Common causes: weak Wi-Fi signal, router overheating, ISP throttling, DNS server issues. Solutions: Move closer to router, restart router, switch to wired Ethernet connection, change DNS to Google (8.8.8.8), or contact ISP about connection stability.

Mobile data works but Wi-Fi shows "site can't be reached" — why? +

Your router or ISP is blocking the site. This confirms the issue is network-specific, not device or browser. Try: (1) Restart router, (2) Change router DNS to 8.8.8.8, (3) Check router parental controls or firewall settings, (4) Contact ISP to check if they're blocking the domain. VPN on Wi-Fi should also work if ISP is blocking.

Error appeared after Windows/macOS update — coincidence? +

Not a coincidence. OS updates sometimes break network configurations, reset DNS settings, or update firewall rules. Fix: Flush DNS, reset network adapter (Fix #6), check firewall rules, and update network drivers. Windows updates occasionally require network adapter driver reinstallation.

Can antivirus software cause this error? +

Yes. Antivirus programs with web protection or firewall features may block sites deemed suspicious. Temporarily disable antivirus and test. If site loads, add it to antivirus exceptions. Common culprits: Norton, McAfee, Kaspersky, Avast web shields.

Is Google DNS (8.8.8.8) safe to use permanently? +

Yes, completely safe and recommended. Google Public DNS (8.8.8.8/8.8.4.4) and Cloudflare DNS (1.1.1.1/1.0.0.1) are faster, more reliable, and more secure than most ISP DNS servers. Millions use them permanently. Privacy concern: Google/Cloudflare can see your DNS queries (what domains you visit) but not actual content. For maximum privacy, use Cloudflare 1.1.1.1.

How do I know if my ISP is blocking websites? +

Test with VPN or mobile data. If site loads on VPN/mobile but not on home Wi-Fi, ISP is blocking. Reasons: Government censorship, court orders, ISP's own policy, or misconfigured network. Contact ISP to confirm. In some countries, ISPs block sites without notification.

Will flushing DNS delete any important data? +

No. DNS cache is temporary network data — flushing it is completely safe and does not delete browsing history, passwords, bookmarks, or any personal data. It only clears the temporary mapping of domain names to IP addresses, forcing fresh lookups.

Quick Troubleshooting Flowchart

Follow this decision tree:
  1. Only one site fails? → Check if down for everyone (downforeveryoneorjustme.com)
  2. All sites fail? → Flush DNS (Fix #2) + Change DNS to 8.8.8.8 (Fix #3)
  3. Works in incognito/other browser? → Clear cache (Fix #5) or disable extensions (Fix #9)
  4. Works on mobile data but not Wi-Fi? → Router/ISP issue → restart router, change router DNS
  5. Started after update? → Reset network (Fix #6) + update drivers (Fix #8)
  6. VPN active? → Disable VPN (Fix #4) and test
  7. Nothing works? → Contact ISP

Conclusion — You're Back Online

"This site can't be reached" no longer gets to block your internet access.

You now have 10 proven fixes, ranked by success rate, covering 96% of all connection failures. Most issues resolve within 5 minutes using Fixes #2 and #3.

Start right now with Fix #2 — flushing DNS cache takes 60 seconds and solves 42% of cases. If that doesn't work, immediately proceed to Fix #3 (Google DNS) which solves another 24%.

Together, these two fixes resolve 66% of all "site can't be reached" errors in under 3 minutes.

Your internet was built for seamless access. Let's restore it.

Still stuck? Comment with: (1) Exact error code, (2) Browser and OS version, (3) Which fixes you tried, (4) Does it work on mobile data? We respond to every comment with personalized solutions.