Domain verification failures
Operations
Common reasons a domain gets stuck in pending and how to fix each.
DKIM record missing or malformed
Most common failure. Double-check:
- The record is a TXT record, not a CNAME (different providers handle this differently — some auto-flatten DKIM keys into TXT, others don't).
- The record name is the selector we returned, not the apex. Typically something like
1234567._domainkey.yourcompany.com. - The record value is the full
k=rsa; p=...string with no line breaks. Some DNS editors silently wrap long values; paste into a tool that shows you the raw stored value.
CNAME for bounce handler missing
The CNAME on bounce.yourdomain.com is required. Without it, bounces aren't routed back to us and we can't track deliverability.
DNS propagation delay
After adding records, wait 5-15 minutes. Some registrars (looking at you, GoDaddy) take up to an hour. Use dig TXT _domainkey.yourdomain.com to confirm the record is live before retrying verify.
Wildcard TXT records interfering
If you have a wildcard TXT * record, it can shadow specific records on some DNS servers. Set the DKIM record with the exact hostname, not a wildcard.
Still stuck?
Fetch the current status and raw DNS records we expected:
curl https://myagentmail.com/v1/domains/yourdomain.com/verify \
-H "X-API-Key: tk_..."
The response shows each record's individual verification state. Whichever is pending is the one missing in DNS.