What the Error Means
Chrome and other Chromium-based browsers show DNS_PROBE_FINISHED_NXDOMAIN when a DNS lookup returns NXDOMAIN — “non-existent domain”. The browser asked for the address of the site and the DNS resolver answered that the name does not exist. Other browsers show the same problem with messages such as “Hmm. We’re having trouble finding that site”.
Step 1: Is It Just You?
The fastest test is to check the domain from outside your network:
- Look it up with our DNS Record Lookup. If it returns an A record, the domain exists and the problem is on your side.
- Check whether the site responds with Is My Site Down.
- Try the site on mobile data instead of Wi-Fi.
If the domain fails everywhere, skip to fixes for site owners.
Fixes on Your Device
1. Check the Spelling
A typo in the address is the most common cause. Check the domain extension too (.com vs .co).
2. Flush the DNS Cache
Your computer may have cached an old “does not exist” answer.
- Windows:
ipconfig /flushdns - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Chrome: open
chrome://net-internals/#dnsand click “Clear host cache”.
3. Change Your DNS Server
Your internet provider’s resolver may be failing or filtering the domain. Switch to a public resolver such as Google (8.8.8.8) or Cloudflare (1.1.1.1). Our guide to public DNS servers shows how.
4. Check the Hosts File
An entry in C:\Windows\System32\drivers\etc\hosts or /etc/hosts can override DNS for a domain.
5. Disable VPN, Proxy or Security Software Temporarily
VPNs, browser extensions and filtering software can block or redirect DNS. Turn them off briefly to test.
6. Restart the Router
Home routers also cache DNS and sometimes stop answering correctly.
Fixes for Site Owners
If the domain returns NXDOMAIN from everywhere, the problem is in its registration or DNS:
- Expired domain: check the expiry date with our WHOIS Lookup. Expired domains are removed from DNS.
- Missing or wrong nameservers: the domain must be delegated to nameservers that host its zone. Run a DNS Report and see how to read it.
- Missing record for a subdomain:
www.example.comneeds its own record. A newly created record may be hidden by negative caching for a while — see why DNS changes are not showing. - Registry hold: a status such as
serverHoldorclientHoldin WHOIS removes the domain from DNS, often because of unpaid fees or unverified contact details.