DNS_PROBE_FINISHED_NXDOMAIN means your browser cannot resolve a domain name into an IP address because the DNS lookup failed. In 2026, the most frequent causes are typos in the URL, incorrect DNS server settings, or expired domain registrations. Flush your DNS cache and verify the domain exists before troubleshooting deeper network issues.
DNS failures account for roughly 15% of all website downtime incidents, according to Catchpoint’s 2025 Internet Resilience Report. When you see this error, your site or the sites you’re trying to reach become completely inaccessible—no fallback, no cached version, just a blank error page. For site owners, a single NXDOMAIN response can cascade into lost revenue, broken API integrations, and support tickets. For users, it’s a dead end.
The error breaks into three parts. “DNS_PROBE” tells you Chrome (or a Chromium-based browser) attempted a domain name lookup. “FINISHED” confirms the lookup completed—it didn’t time out or hang. “NXDOMAIN” is DNS-speak for “Non-Existent Domain.” The authoritative name server for that zone returned a response saying “this name does not exist in my records.”
It’s not a connection problem. Your network is working. The DNS server answered. It just said no.
NXDOMAIN differs from SERVFAIL (server error) or timeouts. When you get NXDOMAIN, the DNS infrastructure is healthy enough to tell you definitively that the name is invalid. That narrows down where to look.
Typos remain the top trigger. One transposed letter or an accidental hyphen sends the query to a name that was never registered. I’ve seen support tickets where the user typed “gooogle.com” for twenty minutes before noticing.
DNS propagation delays are less common now than five years ago, but they still happen after you change name servers or update records. Cloudflare’s public resolver (1.1.1.1) usually picks up changes within seconds, but some ISP resolvers cache aggressively and may hold stale negative responses for an hour.
Expired domains trigger NXDOMAIN the moment the registry deletes the zone. If your domain renewal failed, the authoritative servers stop answering with A or CNAME records and start returning NXDOMAIN instead.
Incorrect DNS server configuration on your machine can also cause it. If your OS or router is pointing to a non-functional resolver (say, 192.168.1.1 when your router doesn’t run a DNS service), queries go nowhere or return errors.
Local DNS cache corruption is rare but real. Windows, macOS, and Linux all cache DNS responses to speed up repeated lookups. A corrupted cache entry can persist even after the upstream DNS has corrected itself.
Start by checking the URL. Sounds obvious, but it catches 30% of cases in my experience. Look for extra dots, missing TLDs, or autocorrect mangling.
Next, flush your local DNS cache. On Windows:
ipconfig /flushdnsOn macOS (Ventura and later):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderOn Linux with systemd-resolved:
sudo systemd-resolve --flush-cachesRestart your browser after flushing. Chromium keeps its own DNS cache separate from the OS.
If the error persists, test the domain from another device or network. Use your phone on cellular data. If it loads there, the problem is local to your machine or network. If it fails everywhere, the domain itself is misconfigured or unregistered.
Check your DNS server settings. On Windows, open Network Connections, right-click your adapter, Properties, Internet Protocol Version 4, and verify the DNS server addresses. On macOS, go to System Settings → Network → your connection → Details → DNS. Make sure you’re not pointing to 127.0.0.1 unless you’re intentionally running a local resolver.
Switch to a public DNS resolver temporarily to rule out ISP issues. Set your DNS servers to 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google). If the site loads with public DNS, your ISP’s resolver is either blocking the domain or has stale cache.
Use a command-line tool to verify DNS responses directly. On any platform with dig:
dig example.comLook for the status line. If you see “NXDOMAIN,” the domain genuinely doesn’t exist in DNS. If you see “NOERROR” with an answer section, the domain resolves fine and the issue is elsewhere (browser cache, proxy, firewall).
On Windows without dig, use nslookup:
nslookup example.comAn answer means DNS is working. “Non-existent domain” confirms NXDOMAIN.
Chrome’s “Use secure DNS” feature can interfere if your network blocks DNS-over-HTTPS (DoH). Navigate to chrome://settings/security and check the DNS section. Try toggling it off temporarily. If that fixes it, your network is blocking port 853 or 443 to public DoH resolvers.
Browser extensions that modify DNS or routing (VPNs, ad blockers, privacy tools) sometimes inject bad DNS settings. Disable all extensions and test in an incognito window. Incognito bypasses extension interference.
Proxy settings can also redirect DNS queries through a misconfigured proxy server. Check chrome://settings → System → Open your computer’s proxy settings. Make sure no proxy is configured unless you need one.
If you control the domain and users are reporting NXDOMAIN, log into your registrar and confirm the domain is active and not expired. Check the name server (NS) records. They must point to functioning authoritative servers.
Run a DNS propagation check at a service like whatsmydns.net. Query your domain from multiple global locations. If half the world returns NXDOMAIN and half returns your IP, propagation is incomplete. Wait 5-10 minutes and recheck.
Verify your zone file on the authoritative name server. If you’re self-hosting DNS, missing A or CNAME records will cause NXDOMAIN for subdomains. Query the domain at the authoritative server directly:
dig @ns1.example.com subdomain.example.comReplace ns1.example.com with your actual name server. If the authoritative server itself returns NXDOMAIN, the record is missing or the zone isn’t loaded.
DNSSEC misconfigurations can also produce NXDOMAIN on validating resolvers. If your domain uses DNSSEC, check for broken signatures with Verisign’s DNSSEC Analyzer or DNSViz. A failed validation makes the resolver treat all responses as bogus and return SERVFAIL or NXDOMAIN depending on the resolver implementation.
Clearing browser cache won’t fix it because the error happens during DNS resolution, before any HTTP cache is checked. You need to flush DNS cache at the OS level or change DNS servers.
Yes, if the firewall blocks outbound DNS traffic on port 53 (UDP/TCP) or blocks responses from specific DNS servers. Check firewall logs and temporarily disable it to test.
The network’s DNS resolver may be misconfigured, offline, or blocking certain domains. Try manually setting DNS to 1.1.1.1 on that network or ask the network administrator to check their DNS settings.
Only if the root cause is temporary—like DNS propagation or a brief resolver outage. If the domain expired or you have persistent local DNS corruption, it won’t resolve until you take action.
Yes, by using the IP address directly in your browser (http://93.184.216.34/ for example.com). This bypasses DNS entirely but won’t work for virtual hosts that require a correct Host header.