DNS_PROBE_FINISHED_NXDOMAIN is a browser error that means your device tried to look up a website's address and failed. NXDOMAIN stands for "non-existent domain," so the name could not be turned into an IP address. It is almost always a local DNS problem, and it is usually fixable in a few minutes.
You type a web address, press Enter, and instead of the page you get a blank screen that says something like "This site can't be reached" with the code DNS_PROBE_FINISHED_NXDOMAIN. You see it most often in Google Chrome, but Edge, Brave, and other Chromium browsers show the same thing. This page is for anyone who just wants the site to load again — and for site owners who see it on their own domain. Don't worry: this is almost always a small settings problem you can clear yourself. To understand the system behind it, see our guide to what DNS is and how it works.
Start with a few quick checks before you change any settings. First, re-read the web address slowly — a single wrong letter causes this error every time. Next, open the same site on a different device on the same network, then open it again on mobile data (turn Wi-Fi off on your phone). You can also paste the address into a free online "is it down" or DNS checker. These three tests tell you where the fault sits.
Every website lives at a numeric IP address (a string of numbers that identifies a server). People remember names like example.com, not numbers, so the internet uses DNS (the Domain Name System — the "phone book" that translates names into IP addresses). When you visit a site, your device asks a DNS resolver (a server that looks names up for you) to find that address.
NXDOMAIN is the answer the resolver sends back when it cannot find a matching record — it literally means "non-existent domain." Chrome runs a "probe" to confirm the lookup, that probe finishes with an NXDOMAIN result, and you get DNS_PROBE_FINISHED_NXDOMAIN. The key point: this is a translation failure, not proof the website is gone. A typo, a stale record saved on your machine, or a struggling DNS server can all produce the exact same message. Learn more about the lookup process in our DNS explainer.
There is no single "fix" because there is no single cause. Work down the list from easiest to most involved and stop as soon as the site loads. The common causes and their matching fixes look like this:
| Likely cause | Fastest fix |
|---|---|
| Typo in the address | Re-check and retype the URL |
| Stale local DNS cache | Flush your DNS cache |
| Router or modem glitch | Restart the router |
| Weak or slow DNS server | Switch to a public resolver (8.8.8.8 / 1.1.1.1) |
| VPN, proxy, or firewall | Turn it off to test |
| Expired or unpointed domain (site owners) | Renew the domain; fix the A record / nameservers |
.con instead of .com triggers this error. Retype it by hand instead of trusting autocomplete.ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. This clears bad saved records. Our flush DNS and check propagation guide covers every system.ipconfig /release and then ipconfig /renew. This asks your network for a fresh connection and often clears the error.8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). These are fast and reliable when your default server is struggling.chrome://net-internals/#dns and click Clear host cache. Chrome keeps its own small DNS cache separate from your operating system.The other frequent slip-ups: ignoring an expired domain. If you own the site, a lapsed registration will show NXDOMAIN to everyone until you renew — check the expiry date first. And forgetting a VPN is running. Many people leave a VPN or proxy on and never connect it to the problem; always test with it off. Finally, skipping the retype step — a plain typo is the single most common cause and the easiest to miss.
Set your devices or router to use a reliable public DNS resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8) instead of leaving them on a slow default — this alone stops many random NXDOMAIN errors. If you own a domain, keep its registration current: turn on auto-renew at your registrar and note the expiry date, because a lapsed domain takes your whole site offline. It also helps to keep your router firmware updated and to bookmark sites you visit often so you never rely on typing the address correctly. For server-side errors that are not about DNS, our server errors guide is a useful companion.
It means your browser asked a DNS server to find a website's IP address and got no match. NXDOMAIN stands for "non-existent domain," so the name could not be translated into a numeric address. It is a DNS lookup failure, and it usually points to a local settings problem rather than a website that is truly gone.
Test the site on another device and on mobile data. If it loads elsewhere, the problem is your computer, network, or DNS server, and the fixes on this page will help. If it fails on every device and network, and an online checker also fails, the domain is likely down, expired, or not pointed at a server — a site-owner issue.
Open Command Prompt and run ipconfig /flushdns, then ipconfig /release and ipconfig /renew. If it persists, change your DNS to 8.8.8.8 or 1.1.1.1 and restart the DNS Client service in Services. These steps clear stale records and give you a fresh, reliable lookup path.
Flush the DNS cache with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then turn Wi-Fi off and on. If the error stays, open Network settings and set your DNS servers to Cloudflare (1.1.1.1) or Google (8.8.8.8). Restarting the Mac also resets its DNS service.
Often yes. If your default DNS server is slow, misconfigured, or holding bad records, it can return NXDOMAIN for sites that are actually online. Switching to a well-run public resolver like Google or Cloudflare gives you a fresh, dependable lookup and clears the error in many cases.
If every other site works and just one fails, the record for that single domain is usually the problem — a stale entry in your cache, a domain that recently changed servers, or, for a site you own, an expired registration or a wrong A record. Flush your cache and, if you own it, check the domain's records.
No. It is a normal network error, not malware. That said, some aggressive VPNs, proxies, or browser extensions can interfere with DNS and trigger it. If it appears suddenly across many sites, disable recent extensions and any VPN or proxy, then test again.
DNS_PROBE_FINISHED_NXDOMAIN means your device could not translate a web address into an IP address. It is almost always a local DNS issue — a typo, a stale cache, or a weak DNS server — so start by testing on another device, then flush your DNS cache and switch to a public resolver like 8.8.8.8 or 1.1.1.1. If you own the site, confirm the domain is current and its records point correctly. Next, learn how DNS caching and updates spread across the internet in our flush DNS and check propagation guide.
The editorial team behind the Bitrich777 Hosting Help Center — practical, tested guides on web hosting, WordPress, servers, DNS, SSL, email, security and migration. Every walkthrough is reproduced on a live host before it is published.
View all guides by the Hosting Team Spotted an error? Tell us
