---
title: "“Safari can’t find the server” on Mac: causes and fixes · Kilobat Guides"
url: "https://kilobat.app/guides/safari-cant-find-server"
description: "Safari says it can’t find the server: check the address, DNS, proxy, VPN and Private Relay on your Mac, then fix the layer that fails."
---

Websites and speed

# Safari can’t find the server on a Mac

“Safari can’t find the server” usually means that the Mac could not get an address for the site name. Often DNS or the connection fails, not the site.

Applies to: Safari on macOS 13 Ventura and later. The Terminal commands work on all current macOS versions. · Checked: 29 October 2026

## Symptoms

- Safari shows “Safari can’t find the server” for one site or for all sites.
- Other apps on the Mac also cannot connect.
- The site opens on another device on the same network.

## Likely causes

- **A typing error in the address.** A wrong name has no address in DNS.
- **No internet connection.** If the Mac is not online, no name can resolve.
- **A DNS problem.** The DNS server does not answer, answers slowly, or gives an old answer from the cache.
- **Proxy, VPN or security software.** Apple says that custom proxy or DNS settings, and VPN or security software, can stop access to websites.
- **The site itself.** If every device and browser fails, the site or its DNS records can be the problem.

## How to check

1. Examine the address in the Smart Search field. Correct any typing errors.
2. Open a different website. If no site opens, examine the connection first. See [Mac connected to Wi-Fi but no internet](https://kilobat.app/guides/wifi-connected-no-internet).
3. In Terminal, look up the site name through the macOS resolver.

   ```
   dscacheutil -q host -a name example.com
   ```

   Output The `ip_address` or `ipv6_address` lines for the name. No lines means that the lookup failed.
4. Show the DNS servers that the Mac uses now.

   ```
   scutil --dns
   ```
5. Open the site in another browser or on another device on the same network. If it fails everywhere, the problem is probably the site.

## How to fix it

1. Reload the page. Choose View > Reload Page, or press Command-R.
2. If you use iCloud Private Relay, choose View > Reload and Show IP Address. See [iCloud Private Relay breaks some websites](https://kilobat.app/guides/icloud-private-relay-sites).
3. If a VPN or security app is on, turn it off for a short test.
4. Flush the DNS cache, then try again. See [Flush the DNS cache on a Mac](https://kilobat.app/guides/flush-dns-cache-mac).
5. If you set custom DNS servers, remove them for a test. Use System Settings > Network > the service > Details > DNS.
6. Update macOS. Safari updates come with macOS updates. Then restart the Mac.

## With Kilobat

1. Kilobat checks the DNS layer and the other layers in one command. It names the layer that failed.

   ```
   kilobat why example.com
   ```
2. To read or change the DNS servers, use `kilobat dns`. Changes need an administrator password.

   ```
   kilobat dns
   ```

   Output The DNS servers of the active network service.
3. To flush the DNS cache, use the same command.

   ```
   kilobat dns flush
   ```

   Needs an administrator password.

## Questions

**Does flushing the DNS cache make DNS faster?**

No. Flushing removes old answers. It helps after a site moved or after a stale error. It does not make the DNS server faster.

**Why does only Safari show the error?**

If other browsers work, look at Safari extensions and stored website data. Apple's Safari troubleshooting steps start there.

## Sources

- [Apple Support: If Safari doesn't work as expected on Mac](https://support.apple.com/en-us/102564)
- dscacheutil(1), man page installed with macOS 27.2
- scutil(8), man page installed with macOS 27.2

Sources checked on 29 October 2026. Man pages are the ones installed with macOS; open one with `man <name>` in Terminal.

## Related guides

- [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found): When DNS fails, the Mac cannot change a name such as apple.com into an IP address.
- [Flush the DNS cache on a Mac](https://kilobat.app/guides/flush-dns-cache-mac): macOS keeps DNS answers for some time.
- [A website works on your phone but not on your Mac](https://kilobat.app/guides/site-works-on-phone-not-mac): When a site opens on your phone but not on your Mac, the problem is usually on the Mac.
- [iCloud Private Relay breaks some websites](https://kilobat.app/guides/icloud-private-relay-sites): iCloud Private Relay sends Safari traffic through two relays.
- [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect): When the internet works but one address fails, Kilobat checks each layer in turn.
- [“A server with the specified hostname could not be found.” on Mac](https://kilobat.app/guides/server-hostname-not-found): This is the macOS text for error -1003.