DNS_PROBE_FINISHED_NXDOMAIN in Chrome, or "server IP address could not be found" — both mean your device asked the DNS system for the domain and got the answer "that name doesn't exist". Let's find out whether the domain is really gone, or your resolver is just confused.

Step 1: Does the domain exist at all?

Use our DNS records tool — it queries the authoritative servers directly. If it returns A/NS records, the domain is fine and the problem is on your side. If it returns nothing, the domain may be expired or deleted (see our one-site-won't-load guide).

Step 2: Flush your local DNS cache

Follow the DNS flush guide: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS.

Step 3: Change your DNS server

Your ISP's resolver may be returning stale NXDOMAIN answers (negative caching). Switch to 1.1.1.1 or 8.8.8.8 and retry — this alone fixes most cases.

Step 4: Check for local hijacks

  • Inspect the hosts file for rogue entries.
  • Disable VPNs, "secure DNS" apps and ad-blocking DNS filters.
  • Restart your router — router-level DNS caches go stale too.

Step 5: Confirm with a live check

Finally run the domain through the website down checker. If our server resolves it normally while you still get NXDOMAIN, the fault is 100% in your local network stack — keep working through the steps above until it clears.