TROUBLESHOOTING GUIDE
How to tell a DNS problem from a website outage
A DNS problem stops your device finding the website’s address. A website can also fail after its address has been found. Start with the exact error and compare another network: neither a browser message nor a single checker result proves the cause on its own.
Reviewed
Likely causes
DNS translates a domain name into network addresses. A missing or incorrect record, an unavailable resolver or a DNSSEC validation failure can prevent that lookup. Successful DNS does not prove the web server is healthy: the connection, HTTPS or application can still fail. A DNS incident can itself make a website unavailable, so “DNS problem” and “outage” are not mutually exclusive.
Steps for visitors
Change one thing at a time. Keep certificate warnings, firewalls and other security protections in place. Ask your administrator before changing a managed network.
Check the spelling and capture the error
Use a known bookmark or the website’s published address. Record the error text before retrying once. If you see a certificate warning, stop and use our HTTPS guide.
What the result means: A name-not-found or DNS-related error points towards address lookup, but can also reflect a mistyped domain. A timeout does not distinguish DNS from later connection stages.
Compare another network
Try the same domain on mobile data or another trusted connection. Check whether unrelated websites also load.
What the result means: If it works elsewhere, investigate a local resolver or network-path difference. If it fails on independent networks, look for an official incident report. This is stronger evidence of a wider issue, but still not proof that every visitor is affected.
Compare the homepage check with the affected page
Use our checker for the domain, then compare that observation with your browser’s exact error. Also check the service’s official status page if available.
What the result means: A successful homepage check means our server completed that request at that time. Your browser may use a different resolver or route. An HTTP error such as 503 means an HTTP server or intermediary returned a response; it is not simply a failure to find an address.
Optionally inspect a DNS lookup
If you are comfortable using a terminal, run nslookup followed by the affected domain, for example nslookup example.com. This is a read-only query. Keep the output for support; do not browse to a returned IP address as a workaround.
What the result means: An address answer means that resolver returned an address at that moment; it does not test the website. NXDOMAIN means the queried name was reported as nonexistent. SERVFAIL means the lookup failed and needs investigation; it can include DNSSEC problems. A query timeout may mean the resolver or the route to it is unavailable. Browser secure-DNS settings can use a different resolver from this command.
Ask for a targeted comparison
Give your ISP or administrator the lookup result and network comparison. Ask them to compare the configured resolver with an independent resolver. On a managed device, leave DNS settings to the administrator.
What the result means: Different answers need interpretation: caches and deliberate geographic routing can legitimately differ. Do not assume that changing to a public DNS service fixes the underlying fault, and do not disable DNSSEC or browser security to make the error disappear.
Our checker makes a request from our server. It cannot test your Wi-Fi, account or every website feature.
If you own the website
Check the exact hostname, its authoritative nameservers and the expected A, AAAA or CNAME records. Review recent DNS changes, cached answers and DNSSEC validation. Use your DNS provider’s diagnostic guidance before changing records. If DNS answers are correct, examine HTTPS, server and application logs instead. Do not promise a fixed “propagation” time: cached records have their own lifetimes.
Who to contact
Visitors should contact the ISP or network administrator when only its resolver or connection fails, and the website when the domain fails on several independent connections. Owners should contact the DNS provider for missing records, nameserver or validation problems; contact the hosting or CDN provider when address lookup succeeds but the service fails. Include the hostname, time, error and comparison results, without passwords or private browsing data.
Sources and further reading
These provider documents support the technical explanations. The comparisons above narrow the investigation; they cannot diagnose every network or service.