How to add AISend's DNS records in Cloudflare
Typing the Name field correctly is half of it; the other half is one Cloudflare switch. A proxied (orange cloud) CNAME answers with Cloudflare addresses instead of the DKIM target, so verification cannot see it. In our count of 19 pending domains, one was behind the Cloudflare proxy; it is the Cloudflare-specific cause we measured. This guide walks the form field by field for mail.acme.com, using Cloudflare's own documentation for the parts that are Cloudflare's, and ends with a terminal check that proves the records are published.
Provider statements checked on November 19, 2026 against the provider's own pages, linked as Sources.
What you will add
AISend is our product: a Resend-compatible email API that sends through Amazon SES. This page is written by the team that builds it, so the records below are the ones AISend really issues. Add a domain on the AISend Domains page first; it shows your three tokens.
Examples use mail.acme.com, a subdomain of acme.com. We recommend verifying a subdomain like this over the root domain; the setup overview and our count of 23 real domains explain why.
| Record | Type | Full host | Value | Needed? |
|---|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail.acme.com | <token1>.dkim.amazonses.com | Yes, gates verification |
| DKIM 2 | CNAME | <token2>._domainkey.mail.acme.com | <token2>.dkim.amazonses.com | Yes, gates verification |
| DKIM 3 | CNAME | <token3>._domainkey.mail.acme.com | <token3>.dkim.amazonses.com | Yes, gates verification |
| SPF (optional) | TXT | mail.acme.com | v=spf1 include:amazonses.com ~all | No |
| DMARC (optional) | TXT | _dmarc.mail.acme.com | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com | No |
Only the three DKIM CNAMEs gate verification. Replace each <tokenN> with the token the Domains page shows; never use a token from this page.
Is Cloudflare really your DNS host?
Edit records in Cloudflare only if the domain's nameservers point to Cloudflare, that is, the domain is active on a Cloudflare zone. If you bought the domain elsewhere and never changed nameservers, Cloudflare can show a zone that nobody queries, and everything you add there is ignored.
One exception Cloudflare documents: if your domain was added to Cloudflare by a hosting partner, you manage its DNS records through that partner. Source: Cloudflare Docs: Manage DNS records, checked November 19, 2026.
Add the records in Cloudflare
- Sign in to the Cloudflare dashboard, open the domain (acme.com) and go to DNS, then Records.
- Select Add record.
- Set Type to
CNAME. - Fill Name and Target (next table), then switch Proxy status to DNS only (grey cloud).
- Select Save, then repeat for the second and third DKIM record.
| Field | What to enter for the DKIM record | Why |
|---|---|---|
| Type | CNAME | TXT for the optional SPF and DMARC records. |
| Name | <token1>._domainkey.mail | Cloudflare's own email example types mail to get mail.example.com, so leave acme.com off. Underscores are valid in names. |
| Target | <token1>.dkim.amazonses.com | Copy it from the AISend Domains page. No trailing text, no https://. |
| Proxy status | DNS only (grey cloud) | The one setting that decides whether verification can work. Only A, AAAA and CNAME records can be proxied; TXT records are always DNS-only. |
| TTL | Leave the default | Proxied records are fixed at Auto (300 seconds); DNS-only records let you choose a value. |
| Content (TXT only) | v=spf1 include:amazonses.com ~all | Type it without quotes. Cloudflare adds the double quotes when you save text that has none. |
Type the host the way Cloudflare wants it
Cloudflare calls the host box Name, the CNAME target Target and the TXT text Content. Worked example for mail.acme.com, in Cloudflare's own words:
| Record | Type | Name to type | Value to type |
|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail | <token1>.dkim.amazonses.com |
| DKIM 2 | CNAME | <token2>._domainkey.mail | <token2>.dkim.amazonses.com |
| DKIM 3 | CNAME | <token3>._domainkey.mail | <token3>.dkim.amazonses.com |
| SPF (optional) | TXT | v=spf1 include:amazonses.com ~all | |
| DMARC (optional) | TXT | _dmarc.mail | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com |
On a record that sits on the registered domain itself (acme.com, not mail.acme.com), Cloudflare wants: @. The calculator below does the same for your own domain.
Type the domain you added in AISend, for example mail.acme.com. Nothing leaves your browser.
What Cloudflare's own documentation says
- Cloudflare says records that prove domain ownership, such as CNAMEs, should not be proxied. Source: Cloudflare Docs: Proxy status, checked November 19, 2026.
- A query for a proxied record is answered with Cloudflare anycast IP addresses instead of the record's own content. Source: Cloudflare Docs: Proxy status, checked November 19, 2026.
- In some cases Cloudflare shows a warning or prevents you from proxying a CNAME, and it names records used for DKIM validation among them. Source: Cloudflare Docs: Proxy status, checked November 19, 2026.
- The orange cloud icon means Proxied; the grey cloud means DNS only. Proxying is on by default when you onboard a domain in the dashboard, so new CNAMEs may arrive orange. Source: Cloudflare Docs: Proxy status, checked November 19, 2026.
- TXT content is a set of strings in double quotes. Inconsistent quotation marks give a validation error, and text saved with no quotes gets them added. Source: Cloudflare Docs: DNS record types, checked November 19, 2026.
- SPF, DKIM and DMARC are all published as DNS records in the zone; Cloudflare says the exact values depend on your email provider. Source: Cloudflare Docs: Set up email records, checked November 19, 2026.
Three Cloudflare switches that hide a correct record
Cloudflare lists four causes when a CNAME used for domain verification does not work: the record is proxied, "CNAME flattening for all CNAME records" is on in the zone settings, Flatten is on for that one record, or an NS record makes another DNS provider authoritative for the name. Source: Cloudflare Docs: Verify a domain with CNAME, checked November 19, 2026.
| Where to look | What should it say | Why |
|---|---|---|
| Proxy status on each DKIM row | DNS only | Proxied answers with Cloudflare IPs, not the CNAME target. |
| Zone DNS settings: CNAME flattening | Not set to flatten all CNAME records | Flattening returns resolved addresses instead of the CNAME. |
| Flatten toggle on the record | Off | Same effect, for a single record. |
An NS record on mail or _domainkey.mail | None, unless you delegated on purpose | It hands that name to another DNS provider, so Cloudflare's CNAME is never read. |
Verify in AISend
- Open the AISend Domains page, find your domain and click Verify DNS Records.
- Each record gets its own live status: "Found", "Not found yet", "Wrong value", "Proxied", "Wrong host", "Duplicate" and so on, with a plain hint on what to change.
- When the three DKIM rows are found the domain is verified. SPF and DMARC stay optional.
The Cloudflare pages we read give no time for a new record to take effect, and the proxy page says only that your own resolver cache can lag behind the 300-second TTL on proxied records. In practice press Verify after a few minutes; the check is live, so a record that exists shows up as soon as resolvers see it.
Check from your terminal
These commands show what the public DNS answers, which is what verification reads.
# paste your first token from the AISend Domains page
TOKEN1=your-first-token
# should print <token>.dkim.amazonses.com.
dig +short CNAME "$TOKEN1._domainkey.mail.acme.com"
# optional records
dig +short TXT mail.acme.com
dig +short TXT _dmarc.mail.acme.com
# where does the domain's DNS really live?
dig NS acme.com +shortPrefer a page? The free SPF & DMARC checker looks up the same records for any domain, no sign-up.
Common failures at Cloudflare
| What you see | Likely cause | Fix |
|---|---|---|
dig A <token1>._domainkey.mail.acme.com returns Cloudflare addresses | The CNAME is proxied (orange cloud). In our count of pending domains, one was behind the proxy. | Edit the record, set Proxy status to DNS only, save. Repeat for all three. |
Record exists in the dashboard but dig CNAME shows nothing | CNAME flattening is on for all records or for that record, or an NS record delegates the name. | Turn flattening off and remove or review the NS record, as Cloudflare's CNAME troubleshooting page describes. |
| Cloudflare refuses to save, or shows a warning on the CNAME | Cloudflare restricts proxying of some CNAMEs, DKIM-validation records among them. | Set the record to DNS only and save again. |
| TXT record rejected with a validation error | Quotation marks are unbalanced, for example "v=spf1 ... ~all with no closing quote. | Paste the value with no quotes at all and let Cloudflare add them. |
dig NS acme.com returns NXDOMAIN | The domain name is misspelled, was never registered, or has expired. In our count of pending domains on 2026-11-17, 11 of 19 did not exist in DNS. | Fix the name in AISend or register the domain; no DNS record can verify a name that does not exist. |
| The nameservers are not the ones you edited | Records were added at a DNS host the domain does not use. Run dig NS acme.com +short and compare the names with the nameservers your Cloudflare zone lists. If they differ, the live DNS is somewhere else and Cloudflare's records are never read. | Add the records at the provider the nameservers point to, or switch the nameservers to the one you edited. |
| Verified, but old mail now fails SPF | A second SPF record on the same name; a name may carry only one. | Merge into one v=spf1 record with a single all, or skip SPF; AISend does not require it. |
The shared causes (zone typed twice, proxies, a second SPF record, a name that does not exist, records added at the wrong DNS host) come from our count of pending domains; the Cloudflare-specific rows come from its documentation, linked above.
Frequently asked questions
Why is Cloudflare's proxy a problem for DKIM CNAMEs?
A proxied record is answered with Cloudflare's IP addresses, not with its target, so a CNAME that is meant to point at dkim.amazonses.com can no longer be seen. Cloudflare's own documentation says CNAMEs that prove domain ownership should not be proxied. Set Proxy status to DNS only.
Do I type the full name in Cloudflare's Name box?
No. Type only the part before your registered domain: <token1>._domainkey.mail for mail.acme.com. Cloudflare's documentation example uses mail to create mail.example.com. If you paste the full name, AISend flags a doubled host.
Does Cloudflare want quotes around the SPF value?
No. Type v=spf1 include:amazonses.com ~all with no quotes; Cloudflare adds double quotes when it saves TXT text that has none. Mismatched quotes cause a validation error.
Which of the records does AISend need before the domain verifies?
Only the three DKIM CNAME records. The SPF and DMARC TXT records are optional and do not block verification. A subdomain such as mail.acme.com is the safer first choice because it rarely already has an SPF record.
Why do the guide's tokens look like placeholders?
The three tokens are generated per domain and shown only in your AISend dashboard. We never invent them; copy each token from the Domains page into the host and into the value.
Sources
Other DNS providers
Ready to send from your own domain?
Creating an account is free, and a free account can send 10 test emails to its own verified address from onboarding@send.aisend.app. Sending to other people needs Pro, $14/month for 50,000 emails, and a verified domain.