dns
DNS Server Not Responding
Compare two public DNS-over-HTTPS resolvers and a direct-IP HTTPS endpoint, then check whether the issue follows your browser or network.
Run DNS Check ↓Measurements describe the endpoint and test shown. HTTP timing is not network-layer packet loss or a direct measurement of your router, WiFi radio or ISP.
Your guided check
Observe. Compare. Take the next step.
Public DNS is a comparison, not your configured resolver
This check requests a controlled public hostname through Cloudflare and Google DNS-over-HTTPS. It cannot read operating-system DNS configuration or force the browser to use the ISP resolver. Public success does not prove local DNS is healthy.
Reachability without a new hostname lookup
The direct-IP HTTPS request uses 1.1.1.1 with certificate validation and needs no DNS lookup for that endpoint. Filtering, TLS, CORS or path failures can prevent it. This does not establish a general outage.
Change one setting only after a useful comparison
Check spelling and try a second browser first. If you later compare DNS providers on a personal device, record the original automatic/manual setting and restore it afterward. Work networks may depend on private DNS; ask the administrator before changing it.
Frequently asked questions
Does this reveal my DNS server?
No. It compares explicitly selected public resolvers and labels each observation.
What does NXDOMAIN mean?
That resolver reported the name does not exist at that moment. A typo, stale record or resolver policy can explain it; another vantage point may disagree.