DNS_PROBE_FINISHED_NXDOMAIN: What It Means and 7 Ways to Fix It
Chrome can't find the site's address. Seven fixes in order — from a 10-second typo check to switching your DNS for good.
You're trying to open a website and Chrome greets you with DNS_PROBE_FINISHED_NXDOMAIN instead. The phrasing is cryptic, but the meaning is simple: your browser asked "where is this website?" and the internet's phone book answered "never heard of it." NXDOMAIN literally stands for "non-existent domain" — the DNS lookup failed, so the page never stood a chance of loading.
The good news: this error is almost always fixable in minutes, and it rarely means the website itself is down. It usually means something between you and the DNS system is misconfigured, stale, or blocking the lookup. Work through these seven fixes in order.
1. Check the URL for typos first
Before touching any settings, look at the address bar. A single mistyped letter — gogle.com instead of google.com — produces exactly this error, because the mistyped domain genuinely doesn't exist. This sounds obvious, but it resolves a surprising share of NXDOMAIN reports. If you clicked a link, try typing the address manually.
2. Restart your browser and flush its DNS cache
Browsers keep their own DNS cache, separate from your operating system. A stale or corrupted entry there can keep failing even after the real problem is gone. In Chrome, open chrome://net-internals/#dns and click "Clear host cache." Then fully quit and reopen the browser. In Edge the same page works; Firefox users can clear it via about:networking#dns.
3. Flush your operating system's DNS cache
Your OS caches DNS answers too, and a poisoned or outdated entry will keep failing lookups. On Windows, open Command Prompt as administrator and run ipconfig /flushdns — you should see a confirmation message. On macOS, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then enter your password. On most Linux distributions, restart the resolver with sudo systemctl restart systemd-resolved or sudo resolvectl flush-caches depending on your setup.
4. Switch to a public DNS server
If your ISP's DNS servers are slow, broken, or hijacking failed lookups, switching to a reputable public DNS often fixes NXDOMAIN instantly — and can make browsing noticeably snappier. The two most trusted options are Google's 8.8.8.8 and 8.8.4.4, and Cloudflare's 1.1.1.1 and 1.0.0.1. On Windows, change this under Network Adapter settings → IPv4 properties; on macOS, under System Settings → Network → DNS. Better yet, change it once on your router and every device in the house benefits. Our guide to changing DNS walks through each platform step by step.
5. Disable your VPN, proxy, or browser extensions
VPNs and proxies reroute your DNS queries through their own servers, and a misbehaving one is a classic NXDOMAIN factory. Temporarily disconnect your VPN and reload the page. If it works, the VPN's DNS is the culprit — try a different server location or enable the VPN's own DNS leak protection settings. Likewise, ad-blockers, "privacy" extensions, and antivirus web shields can intercept DNS; disable them one at a time to find the offender.
6. Restart your router and check its DNS settings
Routers cache DNS too, and cheap ISP-provided units are notorious for corrupting their caches. Unplug the router for a full 30 seconds, plug it back in, and wait two minutes for it to reconnect. While you're at it, log into the router's admin page and check what DNS servers it's handing out — if it points to something odd (or itself with a broken forwarder), set it to 1.1.1.1 / 8.8.8.8 directly.
7. Rule out the website itself
Occasionally NXDOMAIN is real: the site's domain expired, its DNS records were deleted, or the owner moved hosts and botched the migration. Run the domain through our server-side checker — if our independent server also can't resolve it, the problem is on the site's end and no amount of flushing on your side will help. Check the site's social accounts for announcements, then wait for the owner to fix their DNS.
When NXDOMAIN hits every website
If no site loads and everything shows DNS errors, the problem is systemic: your router lost its upstream DNS, your ISP is having a DNS outage, or a firewall is blocking port 53. Switch to mobile data — if that works, your home network or ISP is at fault. ISP-wide DNS outages are usually fixed within hours, and switching to public DNS on your router bypasses them entirely.
Preventing it in the future
Two habits nearly eliminate this error: keep a fast public DNS configured on your router (so one ISP hiccup can't break your browsing), and avoid "DNS booster" utilities that promise speed but install fragile local resolvers. DNS is the foundation every page load stands on — a solid configuration means you may never see NXDOMAIN again.
Frequently asked questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means your browser's DNS lookup failed: the domain name could not be resolved to an IP address (NXDOMAIN = non-existent domain). The page never loaded because the browser couldn't find the server.
Is DNS_PROBE_FINISHED_NXDOMAIN caused by the website being down?
Rarely. It usually means a typo in the URL, a stale DNS cache on your device, a misbehaving VPN or extension, or your DNS server failing — not the website itself. Verify with an independent server-side checker.
Will changing my DNS fix DNS_PROBE_FINISHED_NXDOMAIN?
Often, yes. If your ISP's DNS servers are broken or slow, switching to a public DNS like 1.1.1.1 or 8.8.8.8 fixes the error immediately and usually speeds up browsing too.
Don't guess — test it. Our free checker tells you in seconds whether any website is up or down.
Check a website now