DNS_PROBE_FINISHED_NXDOMAIN on Chrome
Why it happens on Chrome
Chrome keeps its own DNS cache separate from the operating system, so it can show NXDOMAIN after the OS cache has already been cleared.
The fix on Chrome
Visit chrome://net-internals/#dns and click Clear host cache, then chrome://net-internals/#sockets and flush socket pools before retrying.
Is DNS_PROBE_FINISHED_NXDOMAIN happening on your domain?
The DNS lookup queries public resolvers directly and shows the A, AAAA, CNAME and NS records that actually exist — which instantly separates 'record missing' from 'my resolver is stale'.
Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.
If that didn't fix it
Chrome has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes that apply everywhere. The most common one overall is: the a or cname record for the hostname does not exist.
All causes and fixes for DNS_PROBE_FINISHED_NXDOMAINDNS_PROBE_FINISHED_NXDOMAIN on other platforms and devices
Monitor this continuously with LemWatch
A one-off dns_probe_finished_nxdomain monitoring is a snapshot, not ongoing protection. Keep uptime, performance, SEO and security signals together with scheduled monitoring and configured alerts. Start free for 10 sites, no card needed.
Explore ongoing SEO checks · Compare free monitoring options