DNS_PROBE_FINISHED_NXDOMAIN Fix Checklist
How to diagnose NXDOMAIN errors by checking DNS records, nameserver delegation, resolver cache, and domain registration state.
Diagnose your site now
Problem
Your browser shows DNS_PROBE_FINISHED_NXDOMAIN, or the domain appears to not exist at all.
Symptoms
- Browsers return NXDOMAIN-style errors instead of loading the site.
- Public DNS lookups return
status: NXDOMAINor no usable answer. - Some networks can resolve the domain while others still fail.
Top 3 Causes
- The authoritative zone has no usable record - A, AAAA, or CNAME records are missing or were removed.
- Nameserver delegation is incorrect - The registrar points to different nameservers than the zone you actually manage.
- Negative caching or propagation delay - Recursive resolvers still cache the old NXDOMAIN answer.
Diagnose with DechoNet
- DNS Lookup to verify whether A, AAAA, NS, and SOA answers exist at all.
- DNS Propagation Check to compare resolver responses and see whether NXDOMAIN is still cached globally.
- RDAP / WHOIS to confirm the domain is not expired, on hold, or delegated to the wrong nameservers.
Resolution Checklist
- Confirm the registrar nameservers match the authoritative DNS provider you intend to use.
- Check that at least one valid A, AAAA, or CNAME record exists in the authoritative zone.
- Verify propagation against multiple public resolvers such as 8.8.8.8 and 1.1.1.1.
- If the name was previously missing, allow one full negative-cache TTL window before assuming propagation is broken.
- If RDAP shows expiry, hold, or deletion-related status, resolve that state with the registrar first.
When to Escalate
- Contact the registrar if RDAP shows expiry or hold flags.
- Contact the DNS hosting provider if registrar delegation is correct but the authoritative zone still returns no answer.
- If NXDOMAIN persists across many resolvers for an extended period, also inspect DNSSEC and zone publication status.
Related Tools
Related Guides
Share this guide
[Ad] Guide Detail Inline