How to Fix ‘Safari Cannot Open the Page Because the Server Cannot Be Found’

Browsing on your Mac, iPhone, or iPad only to have Safari halt navigation with the alert “Safari cannot open the page because the server cannot be found” indicates that the browser failed to translate the website domain name (FQDN) into a routable IP address through the Domain Name System (DNS). While other internet services or alternative browsers may continue functioning normally, Safari enforces strict Apple security, Private Relay routing, and local network socket rules. When DNS servers timeout, iCloud Private Relay proxy nodes stall, or stale website cache tokens corrupt domain resolution records, Safari terminates HTTP/HTTPS connection establishment. This troubleshooting guide explains how to isolate domain resolution failures, flush Apple system DNS caches, and restore smooth web browsing in Safari.

What Triggers the ‘Server Cannot Be Found’ Error in Safari?

Domain resolution in Safari depends on a chain of DNS resolvers, system caches, and privacy proxies:

• DNS Server Resolution Failure: Your router or internet service provider (ISP) default DNS servers are experiencing latency, query packet drops, or upstream outages.
• iCloud Private Relay Stalling: Apple iCloud Private Relay routes traffic through dual-hop encrypted proxies; if an intermediary egress node degrades, Safari fails to resolve hostnames.
• Corrupted Local macOS/iOS DNS Cache: Outdated or poisoned DNS cache records in mDNSResponder failing to refresh IP endpoints.
• Corrupted Safari Website Data and Cache: Broken local storage or stale Service Worker registrations attempting to fetch assets from decommissioned hostnames.
• VPN or Third-Party Content Blocker Conflict: Security extensions or VPN configuration profiles intercepting socket handshakes and returning empty DNS responses.

Method 1: Verify the URL Syntax and Network Status

Rule out fundamental typographical mistakes and local network disconnections before altering system configurations.

1. Check the address bar for accidental typographical errors, missing domain suffixes (such as .com or .org), or erroneous characters.
2. Test loading a prominent, highly available website (such as apple.com or wikipedia.org) in a new tab.
3. If all sites fail, disconnect your device from the current Wi-Fi network, wait 10 seconds, and reconnect.
4. On mobile devices (iPhone/iPad), toggle Flight Mode on for 10 seconds in Control Centre, then turn it off to re-establish clean cellular and Wi-Fi radio links.

Method 2: Flush the System DNS Cache in macOS

Flushing the native multicast DNS responder clears stale hostname lookups across the entire operating system.

1. Press Cmd + Space to open Spotlight, type Terminal, and press Return.
2. Execute the official Apple DNS cache purge command:

   sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

3. Enter your Mac administrator password when prompted (characters will not display on screen) and press Return.
4. Quit Safari completely (Cmd + Q), relaunch it, and re-attempt to navigate to the website.

Method 3: Toggle or Reconfigure iCloud Private Relay

iCloud Private Relay encrypts DNS lookups; however, proxy server drops frequently prevent Safari from resolving target web servers.

1. On Mac: Open System Settings > Click your Apple Account (Name) at the top > Select iCloud > Private Relay.
2. On iPhone/iPad: Open Settings > Tap your Name > iCloud > Private Relay.
3. Toggle Private Relay to Off (select Turn Off Until Tomorrow to test).
4. Return to Safari and refresh the blocked webpage. If the page loads immediately, Private Relay routing was the bottleneck. You can re-enable it later once Apple proxy clusters stabilise.

Method 4: Clear Safari Website Data, Cookies, and History

Purging stale cached site files and tracking tokens forces Safari to initiate fresh socket negotiations with web servers.

1. On Mac:
   • With Safari open, click Safari in the top menu bar and select Settings… (or Preferences…).
   • Click the Privacy tab, then select Manage Website Data….
   • Click Remove All, then confirm by clicking Remove Now.
   • Click History in the menu bar > Clear History… > Set the timeframe to all history > Click Clear History.
2. On iPhone/iPad:
   • Open device Settings and tap Safari.
   • Scroll down and tap Clear History and Website Data.
   • Select All history and tap Clear History.

Method 5: Configure High-Performance Public DNS Servers

Replacing unreliable ISP DNS resolvers with fast, resilient public DNS resolvers eliminates name lookup timeouts.

1. On Mac:
   • Open System Settings > Wi-Fi.
   • Click Details… next to your connected Wi-Fi network.
   • Click the DNS tab in the left sidebar.
   • Click the + button under DNS Servers and add Cloudflare and Google public resolvers:

     1.1.1.1
     1.0.0.1
     8.8.8.8

   • Click OK to apply your new DNS configuration.
2. On iPhone/iPad:
   • Open Settings > Wi-Fi > Tap the (i) info icon next to your network.
   • Tap Configure DNS and change it from Automatic to Manual.
   • Tap Add Server and enter 1.1.1.1 and 8.8.8.8.
   • Tap Save in the upper-right corner.