TL;DR
- Of 23 customer domains added to AISend (accounts not ours, not banned), 4 verified and 19 are still pending. The 4 verified in a median of about 8 minutes; 17 of the 19 pending ones were added more than 30 days ago. People either finish quickly or never.
- A public-DNS check of the 19 pending domains on 2026-11-17 found that 11 do not exist (NXDOMAIN at the registrable domain). Of the other 8, six had no DKIM records published at all, one was behind a Cloudflare proxy and one is unclear; five already had an SPF record that a second one would break.
- The fixes are mechanical: publish the DKIM CNAMEs exactly as given and DNS-only, keep one SPF record per name, and verify a subdomain such as
mail.acme.comrather than your root domain.
Why I counted
I run AISend, a Resend-compatible email API that sends through Amazon SES. Domain verification is where new users get stuck, so I counted how and where. Domain names below are placeholders (acme.com); no customer domain appears in this article.
What "verified" actually checks
With Amazon SES, the thing that proves you own a domain is DKIM. AWS describes DKIM as the method SES uses to verify domain ownership, and a verified domain can send from any subdomain or address under it (SES identities). When you add a domain, SES issues three DKIM tokens and you publish them as three CNAME records. Only those gate verification in AISend. SPF and the return-path record are optional, and DMARC is recommended afterwards.
Resend works the same way at the dashboard level: add a domain, publish the records, wait. Resend says a domain often verifies within 15 minutes and sometimes takes up to 72 hours (Resend: add a domain). AWS gives the same 72-hour ceiling for DKIM (SES DKIM troubleshooting).
The records, with placeholders
For mail.acme.com the set looks like this. The <token> values come from your dashboard; never invent them.
Type Host (full name) Value CNAME <token1>._domainkey.mail.acme.com <token1>.dkim.amazonses.com CNAME <token2>._domainkey.mail.acme.com <token2>.dkim.amazonses.com CNAME <token3>._domainkey.mail.acme.com <token3>.dkim.amazonses.com TXT mail.acme.com v=spf1 include:amazonses.com ~all (only if mail.acme.com has no SPF yet) TXT _dmarc.mail.acme.com v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com Most DNS providers append your zone, so in the "Name" box you type <token1>._domainkey.mail, not the full name.
Decision table: what you see, what it means
| What you see | Likely cause | How to check | Fix |
|---|---|---|---|
| Pending for hours, records "added" | Host typed with the zone twice: <token>._domainkey.mail.acme.com.acme.com | dig +short CNAME <token1>._domainkey.mail.acme.com returns nothing | Type only <token1>._domainkey.mail |
| Pending, DNS shows an IP at the DKIM name | Cloudflare proxy (orange cloud) hides the CNAME | dig +short A <token1>._domainkey.mail.acme.com returns Cloudflare addresses | Set each CNAME to DNS only |
| Pending, CNAME exists | Wrong value or a stale record | dig +short CNAME shows a different target | Replace with the exact value |
| Nothing resolves anywhere | Domain not registered, typo, or expired | dig NS acme.com returns NXDOMAIN | Fix the name or register the domain |
| No DKIM records found, zone is live | Records added at a DNS host the domain does not use | dig NS acme.com differs from where you edited | Add them at the provider the nameservers point to |
| Verified, but old mail starts failing SPF | A second SPF record at the same name | dig +short TXT acme.com shows two v=spf1 | Merge into one record |
| "Already added by another account" | First account to add the name holds it | Error from the API or dashboard | Contact support |
Cloudflare: turn the proxy off
Cloudflare can only proxy A, AAAA and CNAME records, and its docs say CNAMEs that prove domain ownership should not be proxied (Cloudflare proxy status). Resend gives the same instruction for its CNAMEs (Resend docs). A proxied CNAME answers a lookup with Cloudflare IP addresses, so the verifier cannot see the target. The fix is one click per record: grey cloud, "DNS only".
SPF at the root: the collision
AISend lists an SPF record at the domain itself: v=spf1 include:amazonses.com ~all. If you verify acme.com and you already send mail through, say, Google Workspace, you already have an SPF record there. Adding this one next to it produces two. RFC 7208 section 4.5 says a receiver that finds more than one SPF record returns permerror, so SPF fails for all mail from that name, including your existing mail (RFC 7208).
The merge is a single record:
Before: v=spf1 include:_spf.google.com ~all After: v=spf1 include:_spf.google.com include:amazonses.com ~all Why the collision is less scary than it sounds
Two things. First, SES does not need your SPF record for verification, and by default SES uses an amazonses.com subdomain as the MAIL FROM, which passes SPF without you (SES SPF). Second, a subdomain avoids the question entirely, because mail.acme.com has no SPF record to collide with.
AISend's Verify screen reports each record as found, wrong value, proxied, wrong host, duplicate or merge needed, and says which one to fix.
Start on a subdomain
Resend recommends sending from a subdomain (updates.acme.com) to isolate sending reputation and signal intent (Resend: verified domains). The same reasoning applies to any SES-based sender. A subdomain also leaves the root domain's existing mail and SPF untouched. The exception is a root domain whose reputation you want to keep: then keep it, and warm up as your provider advises.
Our numbers: the cohort
Snapshot: 2026-11-17, read-only counts from AISend's database. Verified domains took a median of 7.8 minutes from being added (range 1.2 minutes to 1.5 hours; n = 4, so treat it as an anecdote). Of the 19 pending, 2 were added in the last 7 days and 17 more than 30 days ago; none sit in between. Apex domains verified 3 of 16 times and subdomains 1 of 7. That sample is too small to say subdomains are better.
| Step | Domains |
|---|---|
| Rows in the domains table (33 accounts) | 55 |
| Our own product domains | -17 |
| Founder or internal test accounts | -8 |
| Banned accounts | -7 |
| Customer cohort | 23 |
| Verified | 4 (17%) |
| Pending | 19 (83%) |
Our numbers: what public DNS shows
I looked up the 19 pending names in public DNS (1.1.1.1 and 8.8.8.8) on the same day. Of the 8 domains that do exist, 5 already have an SPF record at the name, so an unmerged second record would have broken their mail. I did not expect the biggest bucket: more than half of the stuck domains do not exist in DNS. Typos and unregistered names are the main failure here, ahead of the DNS subtleties above. AISend rejects malformed names, reserved names and free-subdomain hosts when you add a domain, but it does not currently check that a well-formed name is actually registered, which is why these rows exist.
| Finding | Domains |
|---|---|
| Registrable domain returns NXDOMAIN (does not exist in DNS) | 11 |
| Zone exists, no DKIM CNAMEs published | 6 |
| Zone exists, DKIM names answer with Cloudflare addresses (proxied) | 1 |
| Zone exists, an address record answers instead of the CNAME | 1 |
Doubled-host records (...acme.com.acme.com) | 0 |
Doing it from an agent
AISend's MCP server exposes add_domain and verify_domain. add_domain returns the records to publish and suggests a subdomain; you publish them yourself, since the tool cannot change DNS. verify_domain returns each record's live state with a plain-language hint, such as a Cloudflare proxy or a second SPF record. The sequence is add, publish, verify, then send.
Frequently asked questions
How long does domain verification take?
Usually minutes once the CNAME records are visible in public DNS. Our four verified customer domains took a median of about 8 minutes. Resend and AWS both say it can take up to 72 hours, so wait that long before assuming a fault.
Why does my domain stay pending after I added the records?
Check three things in order: the domain exists (dig NS acme.com), the records are at the DNS provider your nameservers point to, and the DKIM CNAMEs are not proxied and not typed with the zone twice. In our pending set, 11 of 19 domains did not exist in DNS.
Can I have two SPF records on one domain?
No. Receivers treat more than one v=spf1 record on a name as a permanent error, and SPF fails for all mail from it. Merge the includes into a single record.
Should I verify my root domain or a subdomain?
A subdomain such as mail.acme.com is the safer default: it keeps sending reputation separate and avoids touching the root domain's SPF. Keep the root domain only if its reputation is something you need to preserve.
Does Cloudflare break domain verification?
Only if the DKIM CNAMEs are proxied. Set them to DNS only. Cloudflare says records that prove domain ownership should not be proxied.
Methodology and data
- Read-only snapshot of AISend's production database, 2026-11-17 around 09:40 UTC. Counts only; no customer domain is shown.
- Cohort: domains added by accounts that are not ours. Excluded: 17 domains on our own products, 8 from founder or internal test accounts, 7 from banned accounts.
- "Verified" means the domain's status is
verified. Time to verify isverified_atminuscreated_at, which is the first successful check, not the moment DNS propagated. - DNS findings come from public lookups on the same day and are a point-in-time view; a domain fixed since would show differently.
- Queries and the DNS script are published at aisend.app/data/domain-verification-queries.md.
- Stated plainly: n = 23, one product, one day. Not an industry statistic.