isitdownnow.siteStatus & Diagnostic Hub

DNS_PROBE_FINISHED_NXDOMAIN: 7 Proven Fixes for Windows, Mac & Mobile

Published 2026-03-16•7 min read time•Practitioner Verified
Quick Answer Capsule

DNS_PROBE_FINISHED_NXDOMAIN means your browser cannot resolve the domain name to an IP address because the domain is unregistered, nameservers are invalid, or your local DNS cache is corrupt. Fix it by flushing local DNS (ipconfig /flushdns), switching to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1), and checking WHOIS domain registration status.

Interactive Companion Tool

DNS-over-HTTPS (DoH) Multi-Record Explorer

Query real DNS records (A, AAAA, CNAME, MX, TXT, NS) with TTLs using Google and Cloudflare DNS-over-HTTPS JSON resolvers.

Technical Specifications & Benchmarks2026 Reference
Parameter / MetricExact Value / StandardNotes & Operational Context
Error CodeDNS_PROBE_FINISHED_NXDOMAINNon-Existent Domain response
RFC DefinitionRFC 2308 (NXDOMAIN)Authoritative server confirms name does not exist
Cloudflare Public DNS1.1.1.1 / 1.0.0.1Fastest recursive global resolver
Google Public DNS8.8.8.8 / 8.8.4.4Global secondary fallback
Windows Flush Commandipconfig /flushdnsPurges local client DNS resolver cache

1. Understanding NXDOMAIN (Non-Existent Domain)

NXDOMAIN is an authoritative DNS response code defined in RFC 2308. It indicates that the queried domain name does not exist in the Domain Name System. When your browser encounters this, Chrome displays `DNS_PROBE_FINISHED_NXDOMAIN`.

2. The 7-Step Troubleshooting Protocol

Follow these fixes in descending order of speed:

  • 1. Flush Local DNS Cache (Windows): Open Command Prompt as Administrator and run `ipconfig /flushdns`.
  • 2. Flush Local DNS Cache (macOS): Open Terminal and run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`.
  • 3. Change DNS Resolvers: Replace sluggish ISP DNS with Cloudflare (`1.1.1.1` and `1.0.0.1`) or Google (`8.8.8.8` and `8.8.4.4`).
  • 4. Restart DNS Client Service: On Windows, run `net stop dnscache` followed by `net start dnscache`.
  • 5. Check Local Hosts File: Ensure `C:\Windows\System32\drivers\etc\hosts` (or `/etc/hosts` on Mac) does not contain erroneous mappings.
  • 6. Reset Winsock Catalog: In Windows Command Prompt, run `netsh winsock reset` and restart your PC.
  • 7. Verify Domain Registration: Use a WHOIS search to verify the domain has not expired or entered ClientHold status.

Frequently Asked Questions

Why does the site work on my phone but give NXDOMAIN on my PC?

Your PC is using a stale or corrupted local DNS cache from your Wi-Fi router. Your phone on cellular data queries mobile carrier DNS towers directly. Flush your PC's DNS cache to fix the desynchronization.

Can expired SSL certificates cause NXDOMAIN?

No. Expired SSL certificates trigger ERR_SSL_PROTOCOL_ERROR or SSL_ERROR_BAD_CERT_DOMAIN. NXDOMAIN is exclusively a DNS resolution failure.

Recommended Cloud Host

Need 99.99% Uptime for Your Website?

Deploy ultra-low latency NVMe servers with automated Cloudflare DDoS mitigation, automated backups, and 1-click WordPress staging.

99.99% Guaranteed SLA Uptime
Free SSL & Automated Backups
Global CDN in 280+ Edge Locations
30-Day Money-Back Guarantee

* FTC Disclosure: We may receive affiliate compensation when you subscribe via our partner links at no extra cost to you.

Exclusive Community Discount

Recommended Diagnostic Tools

More Engineering Guides

View all 55 guides