How to add AISend's DNS records in Amazon Route 53

Route 53 has the most fields of any provider here, and two of them cause most mistakes: the Record name box, where you must not repeat the hosted zone, and TXT values, which Route 53 wants inside quotation marks. This guide fills the Create record form for mail.acme.com using AWS's documentation for the console, then checks the published records from a terminal.

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.

RecordTypeFull hostValueNeeded?
DKIM 1CNAME<token1>._domainkey.mail.acme.com<token1>.dkim.amazonses.comYes, gates verification
DKIM 2CNAME<token2>._domainkey.mail.acme.com<token2>.dkim.amazonses.comYes, gates verification
DKIM 3CNAME<token3>._domainkey.mail.acme.com<token3>.dkim.amazonses.comYes, gates verification
SPF (optional)TXTmail.acme.comv=spf1 include:amazonses.com ~allNo
DMARC (optional)TXT_dmarc.mail.acme.comv=DMARC1; p=none; rua=mailto:dmarc@mail.acme.comNo

Only the three DKIM CNAMEs gate verification. Replace each <tokenN> with the token the Domains page shows; never use a token from this page.

Which hosted zone to open

In the Route 53 console you open Hosted zones, choose the hosted zone for your domain and then Create record. If you have no hosted zone yet, AWS tells you to create one first. Source: AWS Docs: Creating records by using the Amazon Route 53 console, checked November 19, 2026.

Route 53 only answers for the domain if the domain's registrar points its nameservers at that hosted zone. A hosted zone that exists but is not the one the registrar uses is the Route 53 version of our most common failure: records added at a DNS host the domain does not use. Check with the terminal command further down before you spend time on the form.

Record name plus hosted-zone name make the full host. With the hosted zone acme.com, the name <token1>._domainkey.mail becomes <token1>._domainkey.mail.acme.com. If you delegated mail.acme.com to its own hosted zone, the zone already supplies .mail.acme.com, so you would type only <token1>._domainkey.

Add the records in Amazon Route 53

  • Sign in to the AWS Management Console and open the Route 53 console.
  • In the navigation pane choose Hosted zones, then choose the name of the hosted zone for your domain.
  • Choose Create record.
  • Choose Simple routing and define the record: Record name, Record type CNAME, Value and TTL (seconds).
  • Choose Create records. If you are adding several records, repeat from the Create record step.
FieldWhat to enter for the DKIM recordWhy
Routing policySimple routingAWS documents the simple-record values for this policy; DKIM CNAMEs need nothing fancier.
Record name<token1>._domainkey.mailAWS: enter the name of the domain or subdomain. Do not type acme.com again; after saving, the record list must read <token1>._domainkey.mail.acme.com exactly.
Record typeCNAMETXT for SPF and DMARC. Do not pick the SPF type: AWS says SPF records are not recommended.
Value<token1>.dkim.amazonses.comAWS: a fully qualified domain name; the trailing dot is optional and treated identically.
TTL (seconds)300We use 300 so a corrected record is picked up quickly. AWS recommends starting with a shorter value such as 300 seconds for a name already in use, then raising it once the settings are confirmed.
Value (TXT only)"v=spf1 include:amazonses.com ~all"Include the double quotes. AWS says to enclose TXT text in quotation marks.

Type the host the way Amazon Route 53 wants it

Amazon Route 53 calls the host box Record name, the CNAME target Value and the TXT text Value. Worked example for mail.acme.com, in Amazon Route 53's own words:

RecordTypeRecord name to typeValue to type
DKIM 1CNAME<token1>._domainkey.mail<token1>.dkim.amazonses.com
DKIM 2CNAME<token2>._domainkey.mail<token2>.dkim.amazonses.com
DKIM 3CNAME<token3>._domainkey.mail<token3>.dkim.amazonses.com
SPF (optional)TXTmail"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), Amazon Route 53 wants: (leave Record name empty). 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 Amazon Route 53's own documentation says

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.

AWS says changes generally propagate to all Route 53 name servers within 60 seconds. Other resolvers can keep an old answer until its TTL runs out, so after correcting a record wait out the previous TTL before judging the result.

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 +short

Prefer a page? The free SPF & DMARC checker looks up the same records for any domain, no sign-up.

Common failures at Amazon Route 53

What you seeLikely causeFix
The record list shows ...mail.acme.com.acme.comZone typed twice in Record name.Edit the record and type only <token1>._domainkey.mail.
Console refuses the CNAME or the SPF TXT at the zone's own nameA CNAME cannot share the hosted zone's name, and at the zone name the Name field must stay empty, not @.Verify a subdomain (mail.acme.com) so no record sits on the zone name.
dig TXT mail.acme.com shows a record, but with unexpected charactersThe SPF value was saved without the quotation marks Route 53 expects for TXT text.Edit it to "v=spf1 include:amazonses.com ~all", with quotes.
Console rejects a CNAME with three lines in ValueA CNAME takes a single value; AWS allows several lines (one per line) only for the other record types.Create three separate CNAME records, one token each.
dig NS acme.com returns NXDOMAINThe 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 editedRecords were added at a DNS host the domain does not use. Run dig NS acme.com +short. The names must match the name servers of the hosted zone you edited. If they do not, update the registrar or edit the zone that is live.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 SPFA 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 Amazon Route 53-specific rows come from its documentation, linked above.

Frequently asked questions

Do I type the full record name in Route 53?

Type the part before your hosted zone: <token1>._domainkey.mail for the hosted zone acme.com. Then read the record list; it must show the full <token1>._domainkey.mail.acme.com. AISend marks a doubled acme.com.acme.com as a wrong host.

Does the TXT value need quotation marks in Route 53?

Yes. AWS says to enclose TXT text in quotation marks. The CNAME values for DKIM take no quotes.

Can I use the SPF record type in Route 53?

Use TXT. AWS lists an SPF type but says SPF records are not recommended.

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

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.