DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

Check whether the site exists, find out whose side the problem is on, then fix it.

DNS_PROBE_FINISHED_NXDOMAIN means the DNS server said the site's name doesn't exist. Check the spelling first, then test the domain below: if it exists, the problem is on your side, and clearing the DNS cache, turning off a VPN or blocker, or switching to a public DNS server fixes it. If it doesn't exist, only the site owner can fix it.

Our server asks Google, Cloudflare, Quad9 and OpenDNS, and the domain's own DNS servers when needed. It can't see your own DNS server: compare its verdict with what you get.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

It means your browser couldn't find the site's IP address because a DNS server answered NXDOMAIN, "non-existent domain": as far as that server knows, the name doesn't exist.

Every visit starts with a DNS lookup that turns the name, such as example.com, into an IP address (how DNS works). NXDOMAIN is DNS answer code 3, "Name Error" in RFC 1035. When the lookup fails, Chrome runs a quick test, the "DNS probe": it asks your own DNS server and Google Public DNS (8.8.8.8) for google.com, a name that surely exists. If your DNS server answers that test correctly, it's working, so Chrome concludes that the site's name really doesn't exist and shows DNS_PROBE_FINISHED_NXDOMAIN. On Android, Chrome often can't test your DNS server; then Google's answer alone decides.

After a failed lookup, Chrome tests your DNS server and Google Public DNS with a name that exists: your DNS works, so the site's name doesn't exist (DNS_PROBE_FINISHED_NXDOMAIN); only Google answers (DNS_PROBE_FINISHED_BAD_CONFIG); neither answers (DNS_PROBE_FINISHED_NO_INTERNET)

Edge, Brave, Opera and Vivaldi are built on the same engine (Chromium) and usually show the same code. Firefox says "Hmm. We're having trouble finding that site", and Safari says "Safari Can't Find the Server": the same problem in other words.

Whose Side Is It On? The Usual Causes

If the test above finds the domain, the cause is on your side; if it says the domain doesn't exist, it's the address or the website.

CauseSideWhat to do
A typo in the address, or an old linkAddressCheck each letter and the ending (.com, .co, .net)
Domain expired or not registeredWebsiteThe owner renews it; look up the expiry with domain WHOIS
New domain or new subdomain without DNS recordsWebsiteThe owner adds an A or CNAME record (see site owners)
A wrong or old answer in a cacheYouClear Chrome's and your device's DNS cache
VPN, ad blocker or security appYouTurn it off for a minute and reload
Your DNS server blocks the domainYouQuad9, ad-blocking DNS and parental controls answer "doesn't exist" for what they block
Your DNS server is failingYouRestart the router, or switch to 1.1.1.1 or 8.8.8.8

How to Fix DNS_PROBE_FINISHED_NXDOMAIN, in Order

Start with the quick checks; each step fixes a different cause, so reload the site after each one.

  1. Check the address and test the domain with the check at the top of this page. If the domain doesn't exist, stop here: nothing on your device can fix it.
  2. Try another device or mobile data. If the site opens there, the problem is on this device; if it fails on every device at home, it's the router or your provider's DNS.
  3. Turn off your VPN, ad blocker or antivirus web protection for a minute, and reload.
  4. Clear Chrome's DNS cache: open chrome://net-internals/#dns and click Clear host cache (in Edge, edge://net-internals/#dns).
  5. Check Chrome's secure DNS: Settings › Privacy and security › Security › Use secure DNS. A custom provider that blocks sites can answer "doesn't exist"; choose "OS default (when available)" to test.
  6. Flush your device's DNS cache: on Windows, ipconfig /flushdns; every system in how to flush DNS.
  7. Restart the router: unplug it for 30 seconds. It keeps its own DNS cache.
  8. Switch to a public DNS server: Cloudflare 1.1.1.1 or Google 8.8.8.8, on the device or the router (how to change DNS). If the site opens now, your previous DNS server was the problem.
  9. Reset the network settings if nothing else worked: the commands are below, and more in DNS server not responding.

Steps for Windows, Mac, Android and iPhone

The steps for the system you're using are open below.

Windows 11 and 10
  1. Right-click Start and open Terminal (Admin) or Command Prompt (Admin).
  2. Run these commands one by one, then restart the computer:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

ipconfig /release disconnects you for a moment; /renew reconnects. netsh winsock reset clears network settings that VPNs and security apps sometimes leave behind.

Mac
  1. Open Terminal, run the command and type your password:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  1. Turn Wi-Fi off and on from the menu bar.
  2. Still failing: System Settings › Network › Wi-Fi › Details › DNS, and add 1.1.1.1 and 8.8.8.8.
Android
  1. Turn Airplane mode on, wait 10 seconds, turn it off.
  2. Check Settings › Network & internet › Private DNS (on Samsung: Connections › More connection settings). A provider hostname that blocks sites can cause the error: set it to Automatic to test (what Private DNS is).
  3. Turn off VPN and ad-blocking apps.
  4. In Chrome: Settings › Privacy and security › Delete browsing data › Cached images and files.
iPhone and iPad

Chrome on iPhone doesn't run the DNS test, so it shows a plain error such as ERR_NAME_NOT_RESOLVED; Safari says it can't find the server.

  1. Turn Airplane mode on and off in Control Center.
  2. Turn off any VPN (Settings › VPN) and ad-blocking or security apps.
  3. On Wi-Fi: Settings › Wi-Fi › (i) › Configure DNS › Automatic, or Manual with 1.1.1.1 and 8.8.8.8.
  4. Still failing: Settings › General › Transfer or Reset iPhone › Reset › Reset Network Settings (Wi-Fi passwords are deleted).

Your Own Site Shows DNS_PROBE_FINISHED_NXDOMAIN

If the test above says your domain or subdomain doesn't exist, the fix is in your DNS: the domain's name servers, or a missing record.

  1. Is the domain still registered? Look up its status and expiry with the domain WHOIS lookup. An expired domain stops resolving.
  2. Do its name servers point to your DNS host? The NS lookup shows them; they must match the ones your host (GoDaddy, Cloudflare, your web host) gives you. A new domain often still points to the registrar's parking servers.
  3. Is there a record for the name? Add an A record (or CNAME) for the domain itself (@) and for www. WordPress sites need both if the site's address uses www. Check with the DNS lookup.
  4. Just fixed it? DNS servers that already answered NXDOMAIN keep that answer for the negative-caching time in your SOA record (RFC 2308). Follow it with the DNS propagation checker.

ERR_NAME_NOT_RESOLVED is the same failure without Chrome's DNS test: the name couldn't be turned into an address. The other DNS_PROBE codes say where the test failed.

ErrorWhat Chrome's test foundFix
DNS_PROBE_FINISHED_NXDOMAINYour DNS server works and says the name doesn't existThe steps on this page
ERR_NAME_NOT_RESOLVEDNo test (iPhone, or a resource inside a page); the name didn't resolveThe same steps; developers: check the host name in the failing request
DNS_PROBE_FINISHED_BAD_CONFIGYour DNS server fails, Google Public DNS worksRestart the router or switch DNS: DNS server not responding
DNS_PROBE_FINISHED_BAD_SECURE_CONFIGChrome's secure DNS provider fails, Google Public DNS worksSettings › Privacy and security › Security › Use secure DNS: choose "OS default (when available)" or another provider in "Select DNS provider"
DNS_PROBE_FINISHED_NO_INTERNETNeither answers: no connectionCheck Wi-Fi and the router
DNS_PROBE_STARTEDThe test is still runningReload; if it stays, follow the steps above

Frequently Asked Questions

What does DNS_PROBE_FINISHED_NXDOMAIN mean?
Your browser asked a DNS server for the site's address and got the answer NXDOMAIN: this name doesn't exist. Either the address is wrong or the domain is gone, or something between you and the site, such as your DNS server, a VPN or a blocker, says it doesn't exist.
Is DNS_PROBE_FINISHED_NXDOMAIN my problem or the website's?
Check the domain with the test on this page. If it finds an address, the site exists and the problem is on your side: your device, browser, network or DNS server. If it says the domain doesn't exist, the problem is the address or the website's own DNS, and only the site owner can fix it.
How do I fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome?
Check the spelling, try another device, turn off any VPN or ad blocker, clear Chrome's DNS cache at chrome://net-internals/#dns (Clear host cache), flush your device's DNS cache, restart the router, and switch to a public DNS server such as 1.1.1.1 or 8.8.8.8.
How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Android?
Turn Airplane mode on and off, then check Settings › Network & internet › Private DNS: set it to Automatic, or to a provider that doesn't block the site. Turn off VPN and ad-blocking apps. In Chrome, clear the browsing data's cached files. If it only fails on Wi-Fi, restart the router.
What is ERR_NAME_NOT_RESOLVED?
Chrome's network error for a name it couldn't turn into an address. You see it instead of DNS_PROBE_FINISHED_NXDOMAIN on iPhone and when Chrome doesn't run its DNS test; developers see net::ERR_NAME_NOT_RESOLVED in the console when an image, script or API address on a page doesn't resolve. The fixes are the same.
What is NXDOMAIN?
NXDOMAIN ("non-existent domain") is the DNS answer code 3, called "Name Error" in RFC 1035: the DNS server says the name you asked for doesn't exist. Google Public DNS shows it as "Status": 3 in its JSON API.
I just bought my domain. Why does it show DNS_PROBE_FINISHED_NXDOMAIN?
The domain usually has no DNS records yet, or its name servers point to a host that doesn't have it. Add an A record (or CNAME) for the domain and for www at your DNS host, then check again here. A DNS server that already answered "doesn't exist" keeps that answer for a while (RFC 2308), so some people see the error longer than others.
Can a DNS server block a site with NXDOMAIN?
Yes. Quad9 answers "doesn't exist" for the malicious domains it blocks, and other security or ad-blocking DNS services, router filters and parental controls can do the same. If the domain works in this test but not for you, your DNS server may be blocking it.
What is an NXDOMAIN attack?
An attack on DNS servers, not on you: it floods them with lookups of random names that don't exist, so they waste work asking other servers. It's also called a DNS water torture attack. It doesn't cause this error on your device.

Next steps

Related Tools

DNS Lookup
Every record of a domain, from the DNS server you pick.
DNS Leak Test
Which DNS server answers your lookups.
DNS Speed Test
Which public DNS server is fastest from your connection.
Domain WHOIS Lookup
Is the domain registered, and when does it expire?

Related Guides

Guide DNS Server Not Responding
When no site opens at all.
Guide How to Flush DNS
The command for every system.
Guide How to Change DNS
Switch to 1.1.1.1 or 8.8.8.8.