Connection CheckupChoose a Symptom

dns

Fix ERR_NAME_NOT_RESOLVED

Check hostname spelling and compare public resolver results with the browser error you see.

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 hosts only. Query parameters and fragments are removed. Leave blank to use connection checks and your answers.

The check contacts our endpoints and Cloudflare / Google public DNS services. They receive your IP and the public hostname being queried. Test privacy

Begin with the exact public hostname

A misspelled name or private work hostname can fail at public resolvers. This tool accepts public hosts only. For an internal name use your organization’s DNS and support rather than public services.

Different resolvers may disagree

A public resolver can return NXDOMAIN, no address records or a timeout. Browser secure DNS, cached records and operating-system DNS can differ; we cannot inspect those local caches.

Compare browsers before changing DNS

Try another browser and check whether its secure-DNS setting differs. Preserve the original setting if you make a reversible comparison; managed-device policies belong with the administrator.

Frequently asked questions

Does public DNS success rule out a DNS problem?

No. It only proves that the selected public resolver answered that query.

Continue with a guided diagnosis

Run a connection check for this symptom