Fix “server not found” and DNS_PROBE_FINISHED_NXDOMAIN

Messages such as DNS_PROBE_FINISHED_NXDOMAIN, “Server not found” and “We can’t find that site” all mean the same thing: your device could not turn the website’s name into an address. The website may be fine. The lookup failed.

Why a lookup fails

• The address was typed wrongly.
• The domain has expired or has not been set up yet.
• Your device or router has a stale or broken DNS cache.
• Your internet provider’s DNS server is having trouble.
• A VPN, security tool or parental filter is intercepting the lookup.

Fixes, in the order to try them

1. Check the spelling of the address, including the ending such as .com or .co.uk.
2. Run a check on siteupdown.com. If our probes reach the site, the problem is on your side. If none do, the site’s DNS or hosting is the problem.
3. Try another network. Switch from Wi-Fi to mobile data. If it works, your router or provider is the issue.
4. Restart your router and wait two minutes.
5. Flush your DNS cache.
6. Change your DNS server to a public one in your network settings, then try again.
7. Turn off VPNs and filters for a minute to see whether they are the cause.

If the website is yours

Check that the domain has not expired, the nameservers are correct, and the right A or CNAME record exists. Remember that changes can take a while to spread, as explained in DNS propagation.

Related guides

• How to flush your DNS cache on Windows, Mac and Linux
• What is DNS propagation, and why does a change take time?
• Website not loading? A step-by-step checklist

Last updated 2 November 2026. Written by the siteupdown.com team. Spotted a mistake?

← All help guides