Work down this list in order. The causes are ranked by how often they turn out to be the problem, not by how likely they feel.
#Still pending after 48 hours
| Check | How to tell |
|---|---|
| Did you enter a subdomain? | Root domains only. mail.yourdomain.com will never verify, re-enter as yourdomain.com |
| Are all the records in? | DKIM needs several CNAMEs. A partial set stays pending forever |
| Did the host field get doubled? | Look for ...yourdomain.com.yourdomain.com. Some registrars append the domain automatically, if so, enter only the prefix |
| Did you save? | Several registrars need a separate confirm or publish after adding records |
| Right domain, right account? | If you own several, it is easy to add records to the wrong one |
| Is DNS actually hosted where you edited it? | If the nameservers point elsewhere, a host, a CDN, a previous web designer, records added at the registrar do nothing |
You can buy a domain in one place and have its DNS served somewhere else entirely. If records look perfect and still do nothing, this is very often why. Check which nameservers the domain uses, and add the records there.
#Verification failed
Failed means the records were found but are wrong, a different situation from pending, and usually a copy error.
- 1
Compare each value character by character against the screen.
Use the copy button rather than reading it across.
- 2
Check for trailing spaces.
Pasting into some registrar fields adds one invisibly.
- 3
Check for smart quotes.
A value that went through a word processor or a chat app may have had its quotes converted.
- 4
Re-save and check again.
#You already send email from this domain
A domain may have only one SPF record. If you already use Google Workspace or Microsoft 365, you have one. Adding a second breaks SPF for all your mail, not just EasyDigz, including mail that was working fine. The existing record has to be edited to include EasyDigz. This is the one step worth handing to whoever set up your existing mail.
#It verified, then stopped working
| Likely cause | Check |
|---|---|
| Records were removed or overwritten | Anyone changing DNS since, a new website, a move to a different host, a tidy-up |
| The domain expired | Check its renewal status at the registrar |
| Nameservers changed | Moving hosting moves DNS. The records need re-adding in the new place |
Because EasyDigz checks live rather than caching, a domain that breaks is noticed rather than silently trusted. Sending stops, which is the safe failure, though it is startling if you do not know why.
#Still stuck
Raise a support request with your domain name, your registrar, and a screenshot of your DNS records as they appear at the registrar. That last one resolves most cases immediately, it shows what is actually there rather than what was intended.