Safari can’t find the server Browser Origin: On your device Last updated 15 Oct 2026

Safari: Safari Can’t Open the Page because Safari can’t find the server

Safari could not resolve the hostname — a typo, DNS trouble or no internet connection.

Exact message you may see Safari can’t find the serverSafari Can’t Open the Page because Safari can’t find the serverSafari cannot open the page because the server cannot be found
Explore the map of this error Full error map →
Seen on: Safari macOS iOS

Meaning

The Safari equivalent of "server IP address could not be found". On iPhone and Mac, check the address first, then Wi-Fi/cellular, then DNS, VPN and content-blocker/profile settings. Private Relay and some VPN profiles can also break lookups.

Common causes

  • Misspelled or non-existent domain
  • No internet or captive-portal Wi-Fi
  • DNS server problem on the router/ISP
  • iCloud Private Relay, VPN or DNS profile interfering
  • Content blocker or Screen Time restrictions

⚡ Quick fix

  1. Check the address and your connection
  2. Switch between Wi-Fi and cellular, or toggle airplane mode
  3. Turn off iCloud Private Relay / VPN to test

Detailed fix by platform

macOS

  1. sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and set DNS to 1.1.1.1 in System Settings → Network → DNS

iOS

  1. Settings → Wi-Fi → (i) → Configure DNS → Manual; Settings → Apple ID → iCloud → Private Relay (off for a test)

How to diagnose

  1. Scope — Only Safari or every app?
  2. Network — Wi-Fi vs cellular?
  3. Features — Private Relay/VPN on?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

1000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)1000A TLS error caused the secure connection to fail — Safari: Safari Can’t Open the Page — A TLS error caused the secure connection to fail (Browser)A TLS error caused th…captive portal — Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites (Browser)captive portalDNS_PROBE_FINISHED_NO_INTERNET — Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet) (Browser)DNS_PROBE_FINISHED_NO…DNS_PROBE_FINISHED_NXDOMAIN — Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN (Browser)DNS_PROBE_FINISHED_NX…ENOTFOUND — Error: getaddrinfo ENOTFOUND host / Name or service not known (API)ENOTFOUNDServer not found — Firefox: Hmm. We’re having trouble finding that site. / Server not found (DNS_PROBE or NS_ERROR_UNKNOWN_HOST) (Browser)Server not foundSafari ca…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.