Opens in a new tab

Amazon SES SPF, DKIM and DMARC setup

Amazon SES sends with its own bounce domain by default, so SPF passes for amazonses.com, not for you. What makes SES mail pass DMARC is Easy DKIM — three CNAME records — and, if you also want SPF to align, a custom MAIL FROM subdomain.

SPFNot needed on your domain
DKIMEasy DKIM: three CNAMEs
Bounce domainamazonses.com, or your custom MAIL FROM subdomain
Set up inSES console → Configuration → Identities → your domain → Authentication

Is your domain set up for Amazon SES?

We read your SPF record, look for Amazon SES’s DKIM key and check DMARC. Nothing is stored.

SPF for Amazon SES

By default the bounce (MAIL FROM) address is a subdomain of amazonses.com. SES says SPF is “implicitly set up for you” — it passes, but for amazonses.com, which does not align with your From domain.

To align SPF, set a custom MAIL FROM domain: a subdomain of your verified domain that you use for nothing else (for example bounce.yourdomain.com). Publish exactly one MX record there, 10 feedback-smtp.<region>.amazonses.com, and a TXT record v=spf1 include:amazonses.com ~all on the same subdomain — not on your main domain.

DKIM for Amazon SES

In the SES console, open Configuration → Identities → your domain → Authentication → DKIM. Easy DKIM gives you three CNAME records; the target’s exact zone depends on the region, so copy them from the console rather than typing them.

Easy DKIM keys are 2048-bit by default. Bring-your-own-key (BYODKIM) is available if you need to publish your own TXT key under a selector you choose.

Every SES message is DKIM-signed for amazonses.com anyway; that signature does not align with your domain. Easy DKIM on your domain is what makes DMARC pass.

NameTypeValue
<token1>._domainkeyCNAME<token1>.dkim.<region>.amazonses.com
<token2>._domainkeyCNAME<token2>.dkim.<region>.amazonses.com
<token3>._domainkeyCNAME<token3>.dkim.<region>.amazonses.com

The exact values come from Amazon SES; copy them from there. Placeholders are in angle brackets.

Bounce domain and DMARC

With Easy DKIM, SES mail passes DMARC on DKIM. With a custom MAIL FROM subdomain as well, it also passes on SPF under relaxed alignment (the default) — a DMARC record with aspf=s breaks that, because the bounce address is a subdomain.

No DMARC record yet? Start with one that only reports, read the reports for a couple of weeks, then tighten it: build it with the DMARC generator.

Common mistakes

  • Identities are per region: sending from two regions means verifying the domain and setting up DKIM in each.
  • Publishing include:amazonses.com on your main domain. It costs a DNS lookup and authorises nothing, because SES never uses your main domain as the bounce address.
  • DNS hosts that append the domain to the record name, producing <token>._domainkey.yourdomain.com.yourdomain.com. Enter only the part before your domain, or end the name with a dot.
  • More than one MX record on the custom MAIL FROM subdomain — SES then fails the setup.

Questions

Should I add include:amazonses.com to my SPF record?

Not on your main domain. Only on the custom MAIL FROM subdomain, if you set one up.

How long does SES take to see the records?

SES keeps looking for up to 72 hours after you publish them.

Sources

Checked against Amazon SES’s own documentation on 25 September 2026:

See every service’s mail pass or fail

Point your DMARC reports at us and we name every server sending as your domain, with what passes, what fails and the exact fix. Free for your first domain.

Create a free account