You type an address, hit return, and Safari stops cold: "Safari Can't Find the Server" or "Server cannot be found." It is one of the most common and most misunderstood errors on a Mac, because it almost never means your internet is down. It means your Mac asked "where does this website live?" and got no answer back. This guide walks the fixes in the order that actually solves it, fastest first.
First: is it one site, or every site?
This single check tells you where the problem is. Open a second website, like apple.com, in a new tab.
- Only one site fails: the problem is that site's address or its own server, not your Mac. Double-check the spelling of the URL and try again later.
- Every site fails but Wi-Fi shows connected: this is a DNS problem on your end. Jump to fixes 3 through 5.
- Wi-Fi itself is dropping or grayed out: that is a connection problem, not a "server not found" problem. See our guide on Wi-Fi that keeps dropping.
The fixes, fastest first
1. Check the address for a typo
It sounds obvious, but the number-one cause of "Server cannot be found" is a misspelled or mistyped address, an autocomplete that filled in a dead URL, or an old bookmark pointing at a site that no longer exists. Retype the address by hand. If you reached the page from a bookmark, delete and recreate it.
2. Reload in a Private window
Press Command-Shift-N to open a Private window and load the site there. Private windows ignore your cache, cookies, and extensions. If the page loads in Private but not in a normal window, the cause is a bad cached entry or a browser extension, and fixes 6 and 7 will clear it.
3. Toggle Wi-Fi off and on
Click the Wi-Fi icon in the menu bar, turn it off, wait five seconds, and turn it back on. This forces your Mac to renew its network lease and re-resolve DNS. It fixes the "connected but nothing loads" state more often than any other single step.
4. Flush the DNS cache
Your Mac remembers the addresses of sites it has visited. When one of those saved answers goes stale, you get "Server cannot be found" even though the site is fine. Clear the cache: open Terminal (Applications → Utilities) and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Enter your password when asked (you will not see it as you type), press return, then reload the page.
5. Switch to a public DNS server
If flushing the cache did not help, your internet provider's DNS server may be the thing that is failing. Point your Mac at Cloudflare (1.1.1.1) or Google (8.8.8.8) instead. This is the most reliable long-term fix, and we cover it step by step in how to change DNS on a Mac. After switching, flush the cache again (fix 4).
6. Clear this site's data
In Safari, go to Safari → Settings → Privacy → Manage Website Data, search for the site that fails, select it, and click Remove. This deletes only that one site's cached data, not your whole history. Reload the page afterward.
7. Disable extensions and content blockers
A misbehaving extension or ad blocker can silently kill a site's connection and produce this exact error. Go to Safari → Settings → Extensions, turn them all off, and reload. If the page comes back, re-enable them one at a time to find the culprit.
8. Check date, time, and any VPN
A wrong system clock breaks the secure handshake many sites need, and a VPN or proxy can route your request into a dead end. Set System Settings → General → Date & Time to "Set automatically," and turn off any VPN to test. If turning off the VPN fixes it but you need the VPN, the DNS-server fix in step 5 usually resolves the conflict.
9. Restart the Mac and the router
If nothing above worked, restart your Mac, then unplug your router for 30 seconds and plug it back in. This clears both ends of the connection and re-establishes a clean DNS path.
The honest part: when it is not something you can fix in software
If every site fails on your Mac but loads fine on your phone over the same Wi-Fi, and none of the steps above help, the problem may be a failing Wi-Fi antenna or a network chip on an older logic board. That is common on MacBooks from 2015 to 2019. If your Mac is old enough that a repair costs more than the machine is worth, it may be time to upgrade rather than repair. A newer refurbished MacBook connects instantly and comes with a warranty, and you can see current deals on our Apple clearance page.
Frequently Asked Questions
Why does Safari say "Server cannot be found" when my Wi-Fi is connected?
Because "connected" only means your Mac reached the router, not the wider internet. The most common cause is a stale or failing DNS server: your Mac can't translate the website name into an address. Flush the DNS cache (fix 4) and switch to a public DNS server (fix 5).
Does this error mean the website is down?
Sometimes. Test the same address on your phone over cellular. If it loads there, the site is fine and the problem is on your Mac. If it fails everywhere, the site itself is likely down and there is nothing to fix on your end but wait.
What's the difference between "Server cannot be found" and "This connection is not private"?
"Server cannot be found" means your Mac never reached the site at all, usually a DNS or address problem. "This connection is not private" means it did reach the site but the security certificate looked wrong. That is a different fix, covered in Safari "This Connection Is Not Private".
Why do all my other apps work but Safari can't find the server?
If other apps genuinely work while Safari fails on every site, the cause is inside Safari: a bad cache, an extension, or a corrupted site setting. Work through fixes 2, 6, and 7. If other apps only seem to work because they show older cached content, you likely have the same DNS problem, so start with fixes 4 and 5.
My pages load but they are painfully slow. Is that the same thing?
No. Slow-loading or spinning pages are a different symptom with a different fix. See Safari slow or pages not loading.