The name could not be turned into an address. When DNS answers NXDOMAIN, the name does not exist: a typo, a record never added, or a domain expired or on hold. Beware Chrome’s DNS_PROBE_FINISHED_NXDOMAIN, though: it is Chrome’s guess, shown for any DNS failure once it has checked your own connection works — the lookup here gives the real answer.
This site can’t be reached Check if there is a typo in example.com. DNS_PROBE_FINISHED_NXDOMAIN
How 10 other clients word the same error
Chrome, when its test did not run
This site can’t be reached example.com’s server IP address could not be found. ERR_NAME_NOT_RESOLVED
Firefox
Server Not Found — Firefox can’t connect to the server at example.com. (older versions: Hmm. We’re having trouble finding that site.)
curl
curl: (6) Could not resolve host: example.com
Linux (ping, Python, Java)
ping: example.com: Name or service not known · [Errno -2] Name or service not known
macOS
nodename nor servname provided, or not known
Windows
No such host is known. · Python: [Errno 11001] getaddrinfo failed · ping: Ping request could not find host example.com. Please check the name and try again.
Node.js
Error: getaddrinfo ENOTFOUND example.com
Python requests
NameResolutionError: Failed to resolve 'example.com' ([Errno -2] Name or service not known)
dig
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4242
nslookup
** server can't find example.com: NXDOMAIN · Windows: *** dns.google can't find example.com: Non-existent domain
| Error | DNS_PROBE_FINISHED_NXDOMAIN |
| Usually fixed by | Either side |
| RCODE | 3 — Non-Existent Domain (RFC 1035) |
| Chrome’s code | A guess after testing your connection — not proof the name does not exist |
| Cached for | The zone’s negative TTL — 15 minutes for an unregistered .com name |
Look up one record
Look the name up from outside your network — the full name, www included if it has one: this shows whether it really does not exist, or fails for another reason.
What it means
NXDOMAIN is DNS saying the name does not exist — not the record, the whole name. Browsers and tools rarely show that code itself. Chrome and Firefox show one page for every DNS failure; Chrome tests your connection and, if it works, labels the failure DNS_PROBE_FINISHED_NXDOMAIN whatever the site’s real problem was.
Resolvers remember a “does not exist” answer for the zone’s negative TTL, so a record added a moment ago can keep failing for a few minutes — up to the negative TTL, which resolvers cap at an hour or three.
DNS hosts that use compact denial of existence for DNSSEC (RFC 9824) — Cloudflare among them — never answer NXDOMAIN: a missing name gets “no error, no records” instead. There, a name that does not exist shows up as No answer in dig and in the lookup above; browsers show the same not-found page either way.
Why it happens
- A typo in the address.
- The record was never created: the site lives at www.example.com but not example.com, or a new subdomain was not added.
- The domain has expired, or the registry holds it (clientHold, serverHold) — see domain on hold.
- The domain’s nameservers at the registrar point to a DNS host that does not have the zone.
- On the visitor’s side: a hosts file entry, or a VPN or filtering DNS that blocks the name.
How to fix it
- Look the name up with the check above. If it resolves here, the problem is local to the device or network.
- If it does not: check the spelling, then check the record exists at the DNS host — for both example.com and www.
- Check the domain’s status and nameservers at the registrar: an expired or held domain, or nameservers pointing elsewhere, both give NXDOMAIN.
- After a fix, give resolvers the negative TTL to forget the old answer — or flush Google’s or Cloudflare’s cache for the name with their own tools.
If you are visiting the site
- Flush the device’s DNS cache: ipconfig /flushdns on Windows, resolvectl flush-caches on Linux.
- Check the hosts file (C:\Windows\System32\drivers\etc\hosts, /etc/hosts) for an entry for the name.
- Try another network, or a public resolver such as 1.1.1.1 or 8.8.8.8.
See it for yourself
dig example.com A @1.1.1.1
nslookup example.com 8.8.8.8
status: NXDOMAIN means the name really does not exist. SERVFAIL, or NOERROR with no answer, means a different problem — see those pages.
Questions
Chrome says DNS_PROBE_FINISHED_NXDOMAIN but the domain exists. Why?
Because Chrome shows that code for any DNS failure once it has checked your own DNS works — it does not see the site’s actual answer. The site may be returning SERVFAIL, have broken DNSSEC or lack the record; look it up to see which.
I just added the record. Why does it still say NXDOMAIN?
Resolvers cache “does not exist” for the zone’s negative TTL. Wait that long, or flush the name at Google Public DNS (dns.google/cache) and Cloudflare (one.one.one.one/purge-cache).
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 2308 — rfc-editor.org
- Dns probe service factory.cc — raw.githubusercontent.com
- Error page strings.grdp — raw.githubusercontent.com
- System Error Codes (9000-11999) (WinError.h) — learn.microsoft.com
- libcurl — Error Codes — curl.se
- Flush Cache — Public DNS — developers.google.com
- RFC 9824 — rfc-editor.org