Why is my domain not verifying?
If your domain is stuck in a pending or failed verification state, work through these common causes.
1. DNS propagation delay
DNS changes can take anywhere from a few minutes to 48 hours to propagate, depending on your provider. Most providers propagate within 30 minutes, but some take longer.
What to do: Wait 30 minutes, then click Verify Domain in the AgentMail Console to trigger a recheck. You can also use dnschecker.org to confirm your records are visible globally before retrying.
2. Wrong record type
Make sure you are adding the exact record type AgentMail provides. AgentMail uses TXT records for SPF, DMARC, and DKIM selector verification, plus MX records when the domain receives mail.
Double check the records in the AgentMail Console under Domains to see the exact type and value required.
Legacy orgs should keep existing working DNS records in place. For new domain setup, add the TXT selector records shown in AgentMail.
3. Extra quotes or spaces
Some DNS providers (like GoDaddy) automatically wrap TXT values in quotes. If you paste a value that already includes quotes, you end up with double-quoted values that fail verification.
What to do: Paste the value exactly as provided by AgentMail. If your DNS provider adds quotes automatically, do not add your own.
Route 53 is the opposite: it requires quotes around TXT values. If you omit them, the record will not validate.
4. Domain name auto-appended
Many DNS providers (Namecheap, GoDaddy, Cloudflare) automatically append your domain to the record name. If AgentMail provides a DKIM selector host like selector._domainkey.yourcompany.com, entering the full hostname may create selector._domainkey.yourcompany.com.yourcompany.com, which will fail.
What to do: Enter only the host portion your DNS provider expects. For example, if your provider appends the domain automatically, enter selector._domainkey, not the full hostname.
5. Conflicting records
Some DNS providers reject multiple records with the same host and type, and multiple SPF records on one host will fail authentication. If an old DKIM record or another stale record exists at the same selector host, it can also prevent the new TXT selector record from validating.
What to do: Check your DNS dashboard for conflicts on the DKIM selector host. Keep the current TXT value from AgentMail and remove stale or duplicate records that use the same host.
6. Nameservers pointing elsewhere
If your domain’s nameservers are pointed to a different provider than where you are adding records, the records will have no effect. For example, if your domain uses Cloudflare nameservers but you add records in the Namecheap panel, those records are ignored.
What to do: Add your DNS records at the provider that actually controls your nameservers.
Verification statuses
You can check your domain’s status in the AgentMail Console:
Still not working?
If you have checked all of the above and your domain is still not verifying, email support@agentmail.cc with your domain name and a screenshot of your DNS records. We can help diagnose the issue.