Troubleshoot a domain that isn't working
Work through four checks in order: has the domain expired, are the nameservers right, is DNSSEC blocking it, and do the records point to the right place. Each takes a minute with ICANN Lookup or a dig command.
Applies to: Cloudflare
On this page
When your website or email stops working at your domain, check four things in this order: whether the domain has expired, whether its nameservers are the two Cloudflare nameservers we sent you, whether a leftover DNSSEC record is blocking it, and whether the DNS records point to the right place. The first three you can check yourself in a few minutes; the fourth we check for you.
If the website is down and you're on Website Care, it's monitored around the clock and an outage is picked up without you reporting it. You're still welcome to open a ticket.
Prerequisites
- Your domain name.
- A browser. A terminal with
digis optional.
Step 1: Has the domain expired?
- Go to ICANN Lookup.
- Enter your domain and run the lookup.
- Check the expiration date and the status.
If it has expired, or the status mentions a hold or redemption, sign in to the registrar shown and renew it. Oogle can't renew domains for you. See How domain registration, renewal and expiry work.
Step 2: Are the nameservers right?
In the same lookup result, read the nameservers. Or run:
dig ns example.com @1.1.1.1Replace example.com with your domain. You should see exactly the two Cloudflare nameservers we sent you (names ending in .ns.cloudflare.com), and nothing else.
- Different nameservers? They've been changed, perhaps by the registrar after a renewal or transfer. Set the two Cloudflare ones back: How to change your domain's nameservers.
- Changed in the last day? It may still be spreading. See How long DNS changes take.
Step 3: Is DNSSEC blocking the domain?
If the domain doesn't resolve at all and the nameservers were changed recently, check for a leftover DS record:
dig ds example.com +short
dig example.com @1.1.1.1If the first command shows a DS record we didn't give you, or the second shows status: SERVFAIL, the DS record from an old DNS provider is the likely cause. Remove it at your registrar, then allow time for old copies to expire, often 24–48 hours. See DNSSEC basics.
Step 4: Do the records point to the right place?
- Go to Google Public DNS.
- Enter your domain and select Resolve.
- Repeat for
wwwin front of your domain, such aswww.example.com.
If either returns no answer, a record is missing. Website records for Oogle-hosted domains are in our Cloudflare account, so we'll check and fix them: open a Website Support ticket. See How to ask us to change a DNS record.
Match the symptom
| What you see | Most likely cause | Where to start |
|---|---|---|
| "This site can't be reached" or "server not found" | Expired domain, wrong nameservers, missing record | Steps 1, 2 and 4 |
| Nothing resolves after a nameserver change | Old DNSSEC record | Step 3 |
| A Cloudflare page with error 521, 522, 525 or 526 | Cloudflare can't reach the website | Fix DNS and SSL errors |
| "Too many redirects" or a certificate warning | SSL settings or redirects | Fix DNS and SSL errors |
| Website works, email doesn't | Mail records | Email DNS records |
Works with www, not without (or the reverse) | One record missing | Step 4 |
You'll know it's fixed when
The domain loads in a private browser window, on your phone using mobile data, and the lookups show the expected nameservers and records.
What to put in a ticket
Choose Website Support, and include:
- the domain and the exact error message
- when it started, and whether anything changed (renewal, transfer, nameservers, a new service)
- what the four checks above showed
Never include your registrar password. If we need registrar access, we'll explain how to share it safely.
Next steps
- Fix DNS and SSL errors
- How long DNS changes take
Frequently asked questions
My website shows a Cloudflare error number. Is that a domain problem?
Usually not. A Cloudflare page with an error such as 521 or 522 means the domain works but Cloudflare couldn't reach the website. See Fix DNS and SSL errors.
The domain works for me but not for a customer. Why?
After a recent change, some networks still hold old answers. If nothing changed recently, ask what error they see and from which network, and include that in a ticket.
Is my website down or is it the domain?
If the error says the server or site "can't be found", it's DNS or the domain. If a page loads but shows an error, it's more likely the website.