Safari "Can't Find the Server"

What’s actually happening

Safari on macOS or iOS shows this when the hostname never resolved to an address. The page may load fine in another browser or on cellular, which usually means the DNS path Safari is using is the problem, not the site. A mistyped domain produces the same wording. Unlike a connection timeout, this fails fast because resolution itself returned nothing usable.

Common causes

• The domain genuinely doesn't exist or is mistyped (true NXDOMAIN)
• A stale or corrupt macOS DNS cache (mDNSResponder) holding a bad entry
• An unreachable or misconfigured DNS server in the active network's settings
• A new domain or recently changed record still propagating (TTL not yet expired)
• A VPN/Network Extension or content filter on iOS intercepting and dropping the lookup

How to fix it

1. Confirm the name resolves outside SafariIn Terminal run `dig example.com` or `nslookup example.com`. If it returns no answer, the problem is DNS, not Safari. If it resolves but Safari still fails, move to the cache step.
2. Flush the macOS DNS cacheRun `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`, then retry. This clears a poisoned or stale cached NXDOMAIN that survives even after the record goes live.
3. Change the DNS serverSystem Settings -> Network -> Details -> DNS, add 1.1.1.1 and 8.8.8.8, remove a dead entry. On iOS, set DNS per-Wi-Fi under the network's Configure DNS -> Manual.
4. Disable VPN / content filters and retestTurn off any VPN, iCloud Private Relay, or DNS-based content blocker. These install Network Extensions that can silently fail lookups; if the site loads with them off, reconfigure or whitelist the domain.
5. Wait out propagation for new recordsIf you just pointed the domain, check propagation with `dig @1.1.1.1 example.com` from a clean resolver. Until the old TTL expires, some resolvers still return the previous (or empty) answer.