Browser showing DNS_PROBE_FINISHED_NXDOMAIN error with warning icon

Domain Management

DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

Domain 360 Team

·July 9, 2026·7 min read

DNS_PROBE_FINISHED_NXDOMAIN is Chrome's way of saying it could not find any DNS record for the domain you tried to visit. NXDOMAIN is a specific DNS response code meaning Non-Existent Domain — the DNS system answered the lookup with a definitive "this name does not exist."

Quick answer: NXDOMAIN means the DNS system has no record of the domain you tried to reach. The fix depends on why — here are all five causes, in the order most likely to apply to your situation.

That definitiveness is important. Unlike a timeout or a connection error, NXDOMAIN is an answer. Something in the DNS chain told Chrome this domain is not registered or has no records. The question is: what is causing that answer, and is it accurate?

What Are the Five Most Likely Causes?

Cause 1: Typo in the URL

The most common cause, and the easiest to check. A single character wrong in the domain name produces an NXDOMAIN because the misspelled domain genuinely does not exist. Check the address bar carefully, including the extension — .co vs .com is a common source of this error.

Cause 2: Stale DNS Cache

Your device may have cached a previous NXDOMAIN response from when the domain was briefly unreachable or unregistered. Now that the situation has changed, your cache serves the old failure response without checking again.

Fix: flush your DNS cache. Windows: ipconfig /flushdns in Command Prompt as administrator. Mac: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Full instructions in our DNS flush guide.

After flushing, also clear Chrome DNS specifically: navigate to chrome://net-internals/#dns and click Clear host cache.

Cause 3: DNS Server Problem

Your configured DNS server may be returning incorrect NXDOMAIN responses due to filtering, misconfiguration, or outage. Try changing your DNS server to a public alternative:

Open network settings, set DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). Our guide on setting up Cloudflare DNS covers the process for each operating system.

If the site loads after changing DNS server, the problem was with your previous DNS server, not the domain itself.

Cause 4: Expired Domain

If this is a site you manage, or a site that was working until recently, check whether the domain has expired. An expired domain has its DNS records pulled from nameservers. Anyone looking it up — including your own browser — gets NXDOMAIN.

Run a WHOIS lookup on the domain and check the expiry date and status codes. If the status shows RedemptionPeriod or PendingDelete, the domain has lapsed and recovery options are time-sensitive.

For a domain you own, see our expired domain recovery guide for recovery steps. For a site you use that belongs to someone else, there is nothing to do but wait and see if the owner renews it.

Cause 5: VPN or DNS Filtering

Some VPNs, firewalls, and DNS filtering services block domains by returning NXDOMAIN responses rather than the real IP address. This is how content filtering works at the DNS level — it is technically the same response as a non-existent domain.

If you are on a work network or using a VPN, try disabling it and retrying the site. If the site loads without the VPN, the filtering is the cause. On corporate networks this is typically intentional; on a personal VPN it may be a misconfiguration.

Are There Chrome-Specific Steps?

If only Chrome shows this error and other browsers (or the same URL on a phone) work fine, the issue is Chrome-specific:

Navigate to chrome://net-internals/#dns and click Clear host cache. Then navigate to chrome://net-internals/#sockets and click Flush socket pools. Restart Chrome and try again.

Chrome extensions — particularly some security and privacy extensions — can also interfere with DNS resolution. Try opening the site in a new Incognito window (which disables extensions by default) to test this.

How Do You Check DNS from the Command Line?

To see what DNS records the domain actually has, run a lookup from Terminal or Command Prompt: nslookup example.com 1.1.1.1. If this returns an IP address, the domain resolves on Cloudflare DNS and your local DNS or cache is the problem. If it returns NXDOMAIN even here, the domain genuinely has no records at the moment, and the cause is either expiry, propagation, or a DNS configuration issue on the domain side.

Quick Answers

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

NXDOMAIN stands for Non-Existent Domain. This error means the DNS system returned a definitive "this domain does not exist" response for the address you tried to visit. It can mean the domain is unregistered, expired, or has broken DNS records — but it can also mean your own DNS cache or server has incorrect information.

How do I fix DNS_PROBE_FINISHED_NXDOMAIN?

Work through these steps: 1) Check for a typo in the URL. 2) Flush your DNS cache (ipconfig /flushdns on Windows). 3) Try a different DNS server such as 1.1.1.1 or 8.8.8.8. 4) Check whether the domain has expired via WHOIS. 5) Disable VPN or proxy if active. In most cases, one of the first three steps resolves it.

Why does DNS_PROBE_FINISHED_NXDOMAIN only appear in Chrome?

Chrome uses its own DNS implementation separate from the operating system, and it shows its own error messages. The same DNS failure on other browsers might show ERR_NAME_NOT_RESOLVED or simply "Server not found." Clearing Chrome DNS cache at chrome://net-internals/#dns can resolve browser-specific cases.

Can DNS_PROBE_FINISHED_NXDOMAIN mean my domain expired?

Yes. An expired domain loses its DNS records. When resolvers try to look up an expired domain, they get NXDOMAIN responses as the records clear. If you own the site and it suddenly shows this error, check your domain expiry date immediately. The grace period window for recovery varies by registrar.

Does DNS_PROBE_FINISHED_NXDOMAIN mean the website is permanently gone?

Not necessarily. It means the domain was not found in DNS at the moment of the query. The site could be temporarily down due to DNS propagation, a configuration error, or a recently expired domain — any of which can be resolved. Only if the domain has been deleted after the redemption period is the loss potentially permanent.

Never lose a domain again

Track every domain you own in one dashboard. Free for up to 15 domains.