DNS_PROBE_FINISHED_NXDOMAIN Browser Origin: On your device Last updated 15 Oct 2026

Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN

The DNS server answered that the domain name does not exist (NXDOMAIN) — a typo, an expired or unregistered domain, a missing DNS record, or a stale DNS cache.

Exact message you may see server IP address could not be foundDNS_PROBE_FINISHED_NXDOMAIN This site can’t be reached
Explore the map of this error Full error map →
Seen on: Chrome Edge Windows macOS

Meaning

Unlike a timeout, DNS replied clearly: no such name. Check spelling first, then whether the domain is registered and has A/AAAA/CNAME records. If it works on other devices or networks, flush the local DNS cache or change DNS servers.

Common causes

  • Typo in the domain or a missing www/subdomain record
  • Domain expired, not yet registered or nameservers not delegated
  • DNS records missing or recently changed (propagation)
  • Stale local DNS cache or hosts file entry
  • ISP/router DNS problem

⚡ Quick fix

  1. Check the spelling and test with nslookup example.com 8.8.8.8
  2. Flush DNS cache: ipconfig /flushdns (Windows) / sudo dscacheutil -flushcache (macOS)
  3. Owners: verify nameservers and records at the registrar

Detailed fix by platform

Windows

  1. ipconfig /flushdns then netsh winsock reset; set DNS to 1.1.1.1 / 8.8.8.8 in the adapter settings

macOS

  1. sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux

  1. resolvectl flush-caches and dig example.com +short

Code examples

Is it DNS?

bash
nslookup example.com            # your resolver
nslookup example.com 8.8.8.8    # public resolver
dig NS example.com +short       # are the nameservers set?

How to diagnose

  1. Name — Spelled correctly?
  2. Resolvers — Does a public DNS resolve it?
  3. Records — A/AAAA/CNAME present at the DNS host?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

1000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)10001001 — Cloudflare Error 1001: DNS resolution error (Cloudflare)10011002 — Cloudflare Error 1002: DNS points to Prohibited IP / Restricted (Cloudflare)10021003 — Cloudflare Error 1003: Direct IP access not allowed (Cloudflare)10031004 — Cloudflare Error 1004: Host Not Configured to Serve Web Traffic (Cloudflare)10041014 — Cloudflare Error 1014: CNAME Cross-User Banned (Cloudflare)10141016 — Cloudflare Error 1016: Origin DNS error (Cloudflare)10161018 — Cloudflare Error 1018: Could not find host (Cloudflare)1018DNS_PROBE…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.