Why isn't my domain loading?
A “server not found” error can have many causes: an expired or suspended domain, wrong name servers, a broken DNSSEC chain or a missing A record. The tool checks these layers in order using the official RDAP record and public DNS resolvers, and states clearly which server and application parts it cannot check.
Loading the tool…
This tool runs in your browser and needs JavaScript.
How to use it
- Enter the address that will not open in the browser (with or without www).
- Press the run button. Results are listed separately as definite problems, possible issues, unverifiable and passed; each finding shows what was found, what it means, the fix and the limits of the check.
- Apply the suggested fix and run the tool again to confirm. Use “Copy result” to add the report to a support ticket.
Example
For a domain placed on clientHold over an unpaid invoice, the tool reports as a definite problem why the site is offline even though the DNS records are correct. The “Example” button in the form fills in a scenario like this and shows the result immediately.
Scope and limits
Scope: domain registration (RDAP), delegation (NS), DNSSEC chain, A/AAAA/www records and consistency between two public resolvers. Web server, SSL and application errors are out of scope.
Your inputs are not added to the address bar or passed to analytics, and result pages are not indexed by search engines.
Related guides
- DNS records explained: A, AAAA, CNAME, MX, TXT
- What happens when a domain expires
- Fix HTTPS and mixed content after SSL
- Domain search and prices
More tools
Ready to Get Started?
Create your account, or write to our team if you have questions.