How to fix DNS_PROBE_FINISHED_NXDOMAIN

Find out how widespread the error is

Copy the address and check for typos. The root example.com and www.example.com are separate DNS names. Try the same URL on a second device on Wi-Fi, then on mobile data. If only one device fails, check its resolver, browser Secure DNS or VPN. If the whole Wi-Fi network fails but mobile data works, compare the networks’ DNS resolvers.

Read the DNS result

NXDOMAIN means the queried name does not exist. A hostname with no AAAA record can still work over IPv4 if it has an A record. SERVFAIL means the resolver could not produce a valid answer, which can happen with DNSSEC problems. Astrotor shows what an external resolver sees. An internal company name may resolve only on the company network or VPN.

Clear the Windows cache when appropriate

If other devices resolve the name, or the public record has already changed, run this command in Windows Terminal or Command Prompt and retry:

ipconfig /flushdns

This clears the Windows resolver cache. Your browser, router and internet provider may cache separately. Private browsing does not reset the system DNS cache.

Check the record if you manage the site

If the root domain opens but www returns NXDOMAIN, verify the A, AAAA or CNAME your host requires for www. Check that the registrar delegates the domain to the nameservers whose zone you edited. A newly created name can still return a cached negative result. Verify the authoritative answer before testing recursive resolvers again.