DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

Beginner⏱ 3 min readUpdated October 13, 2026

"This site can't be reached" with DNS_PROBE_FINISHED_NXDOMAIN underneath means one thing: the DNS answer your browser got says the name does not exist. Either that is true — the domain expired or the record is missing — or something on your side is giving a wrong answer. Five minutes is usually enough to tell which.

What the error means

NXDOMAIN ("non-existent domain") is a normal DNS answer, not a timeout: a resolver asked and was told the name is not there. Chromium browsers show a code; Firefox and Safari show a sentence in your interface language instead, such as "Hmm. We're having trouble finding that site" or "Safari can't find the server".

Browser	Error code
Chrome · Edge · Brave · Opera	`DNS_PROBE_FINISHED_NXDOMAIN`
Chrome · Edge · Brave · Opera	`ERR_NAME_NOT_RESOLVED`

ERR_NAME_NOT_RESOLVED is the same problem without the probe's verdict. If the error ends in NO_INTERNET or BAD_CONFIG instead, the lookup never got an answer — check the connection, not the domain.

First: is it only you?

Everything else depends on this answer, and it takes a minute:

Open the site on your phone with Wi-Fi switched off, so it uses a different network and resolver.
Run the domain through the PixDNS propagation checker: 18 public resolvers around the world look it up.
If the site works elsewhere and the resolvers find it, the problem is on your device or network. If they all say NXDOMAIN, the problem is the domain.

If it is only you

0 of 7 done

Check the spelling, including the ending: .com and .co are different domains.
Flush the DNS cache on your computer and restart the browser.
Turn off any VPN, proxy or ad-blocking DNS (Pi-hole, NextDNS, AdGuard): blocklists answer NXDOMAIN on purpose.
Restart your router, which may have cached the bad answer.
Switch your device to a public resolver such as 1.1.1.1 or 8.8.8.8 and try again.
Check the hosts file for a stray line with the domain in it.
On Windows, if nothing else helps, reset the network stack:

:: Windows — run in Command Prompt as administrator, then restart
ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Tip: If changing the resolver fixes it, your provider's DNS is the culprit — either it still caches an old "does not exist" answer, or it is filtering the domain. Stay on the public resolver or contact the provider.

If it is everyone (you own the domain)

A domain that resolvers worldwide report as non-existent has a problem in its registration or delegation, not in its web server:

0 of 5 done

The domain has not expired. A WHOIS or RDAP status of clientHold or serverHold removes it from the TLD, and every lookup returns NXDOMAIN.
The nameservers at the registrar are the ones that actually host the zone.
Those nameservers have a record for the exact name visitors use — www and the apex are separate names.
A newly registered domain has had time to appear in the TLD's zone, usually minutes, rarely a few hours.
The zone was not deleted or recreated empty at the DNS provider during a migration.

dig example.com A +short               # what a resolver says
dig example.com NS +trace              # follow the delegation from the root
whois example.com | grep -i -E "status|expir|name server"

NXDOMAIN versus SERVFAIL

A broken DNSSEC signature or nameservers that do not answer produce SERVFAIL, which Chrome usually shows as ERR_NAME_NOT_RESOLVED rather than NXDOMAIN. The causes and fixes differ — Fix NXDOMAIN and SERVFAIL covers both, and DNS Doctor walks through them for your domain.

Run DNS Doctor on a domain →Next: how to flush the DNS cache →

Frequently asked questions

Is DNS_PROBE_FINISHED_NXDOMAIN my fault?

Only if the site works on other networks. If resolvers worldwide also say the name does not exist, the domain itself has a problem — often an expired registration.

Does changing DNS to 8.8.8.8 fix it?

It fixes the cases where your provider's resolver is wrong or filtering. It cannot fix a domain that really does not resolve.

Why does it happen on one site only?

Because the answer is per domain: that domain's record is missing, it has expired, or your network blocks it.

How long does NXDOMAIN stay cached?

For the negative-caching time in the zone's SOA record, often 5 minutes to an hour. Flushing your own cache only removes your device's copy.

Try it on your domain

See the theory in practice — run a DNS Doctor for your own domain.

Updated October 13, 2026

Sources