Amazon SES
Amazon SES DKIM, SPF record and DMARC: setup guide
Set up Amazon SES DKIM with three Easy DKIM CNAMEs, add the SPF record on a custom MAIL FROM subdomain, then publish DMARC and confirm it.
Check your current setup:
How Amazon SES authenticates your mail
Amazon SES DKIM setup comes down to three CNAME records on your domain. SES generates them, you publish them, and SES then signs your mail with your own domain. This guide covers those records, the SPF record for a custom MAIL FROM domain, and the DMARC record that ties both together.
DMARC asks whether SPF or DKIM passed for a domain that matches the From domain people see. That match is called alignment, and one aligned pass is enough.
Before you configure anything, neither one aligns:
- SPF. SES uses a subdomain of
amazonses.comas the MAIL FROM, the hidden envelope sender that receives bounces. SPF passes for that domain, which belongs to Amazon, so it cannot align with yours. - DKIM. DKIM (DomainKeys Identified Mail) adds a digital signature to each message. SES automatically adds its own signature with
d=amazonses.com. Easy DKIM adds another one with your domain ind=.
The Amazon SES facts to keep at hand:
- SPF include:
amazonses.com, published on the custom MAIL FROM subdomain. Your root domain does not need it. - DKIM selectors: SES generates three for each identity, so there is no fixed name. A selector is the label before
._domainkeythat tells receivers which public key to fetch. With BYODKIM (your own key) you choose one selector. - DKIM alignment: the signature aligns once Easy DKIM or BYODKIM is active on your domain. The
d=amazonses.comsignature does not align with your domain.
Step 1: Set up Amazon SES DKIM with a domain identity
- In the SES console, select the AWS Region you send from. In the navigation pane, under Configuration, choose Identities, then Create identity.
- Under Identity details, choose Domain and enter your domain without
www. - Keep the default DKIM settings: Easy DKIM with a 2048-bit key (
RSA_2048_BITunder Advanced DKIM settings) and DKIM signatures enabled. Choose Create identity. - On the identity's Authentication tab, expand Publish DNS records and copy the three CNAME records. Create all three at your DNS host exactly as shown.
Each name has the form token._domainkey.example.com, and each value has the form token.dkim.amazonses.com. The token is the DKIM selector. SES generates three for each identity, so copy them instead of typing them. The zone after the token varies by Region and identity and can read dkim.us-west-2.amazonses.com, so take the value from the console.
DNS changes can take up to 72 hours to propagate. When SES detects all three records, DKIM configuration shows Successful and Identity status shows Verified. Keep the records in place afterwards. If they disappear, SES disables DKIM signing and sends you an email.
Identities are per AWS Region. To send from a second Region, create and verify the identity there too. Deterministic Easy DKIM (DEED) is another option: a replica identity in another Region reuses the DNS records of an Easy DKIM parent. In the console, replicas appear as Global identities.
Step 2: Add the Amazon SES SPF record with a custom MAIL FROM domain
Easy DKIM alone can pass DMARC. A custom MAIL FROM adds a second aligned route, and AWS says using SPF and DKIM together gives DMARC the best chance to authenticate your mail.
- Open the verified domain identity. In the Custom MAIL FROM domain pane, choose Edit.
- Select Use a custom MAIL FROM domain and enter a subdomain in MAIL FROM domain, for example
mail.example.com. Pick a subdomain that does not send or receive mail and has no other use. - Under Behavior on MX failure, choose Use default MAIL FROM domain during setup. With Reject message, SES refuses mail from this identity while the MX record is wrong. Choose Save changes.
- Publish the two records from the Publish DNS records table on that subdomain:
- An MX record with priority
10pointing to the feedback endpoint for your Region, for examplefeedback-smtp.us-east-1.amazonses.com. It receives bounce and complaint notifications, and it must be the only MX record on that subdomain. - A TXT record with the SPF value below. AWS says the value usually needs the quotation marks shown in the console, though some DNS hosts do not require them.
- An MX record with priority
v=spf1 include:amazonses.com ~all
This TXT must be the only SPF record on the subdomain, because a name can publish just one. Your root domain's SPF record does not need include:amazonses.com. SPF is checked against the MAIL FROM domain, and that is now the subdomain, so leave the root record as it is.
SES looks for the MX record for up to 72 hours, and the state moves from Pending to Success. Until then, SES applies the option you chose under Behavior on MX failure.
Step 3: Publish your Amazon SES DMARC record
DMARC is now defined by RFC 9989, and RFC 9990 defines its aggregate reports. Both replace RFC 7489. If your domain already has a _dmarc record, edit it instead of creating a second one. Keep its current policy and add the reporting address to its rua tag, separated by a comma. Receivers discard every DMARC record when more than one comes back.
Create a TXT record named _dmarc on your domain (_dmarc.example.com):
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace dmarc@example.com with your DMARC Pulse reporting address. p=none is monitoring mode: you get reports and do not yet ask receivers to act on failures.
Relaxed alignment accepts related subdomains; strict alignment requires exact domains. Preserve your existing adkim and aspf settings. SES’s custom MAIL FROM is a subdomain, so strict SPF alignment may fail while exact-domain DKIM still passes DMARC.
Step 4: Confirm it works, then enforce
Send a test message and inspect the results added by your receiving provider. Confirm dkim=pass and dmarc=pass; read d= in the corresponding DKIM-Signature for the actual signing domain and s= for the selector. header.i is the AUID and can contain an address or subdomain; it is not DMARC’s alignment input, especially under adkim=s.
2. Enter the token from one of your CNAME names as the selector in the DKIM Checker.
3. Read your aggregate reports. Each row names the header_from domain and the DKIM and SPF results. RFC 9990 makes envelope_from optional, so some reports may leave it out. On SES rows, dkim or spf under policy_evaluated should read pass.
Preserve any existing policy and report destinations. For a first deployment, monitor at p=none. After every legitimate sender passes with alignment, assess p=quarantine. Consider p=reject separately, including mailing-list and forwarding risks; it is optional. Receivers decide how to handle individual messages.
A domain that publishes p=reject must apply valid DKIM signatures (RFC 9989, section 7.4), so finish Step 1 first. If people on your domain post to mailing lists, the RFC advises against p=reject.
Common problems
DKIM stays pending after 72 hours
Check the record names at your DNS host. Some hosts append your domain without saying so, which creates token._domainkey.example.com.example.com. Remove the domain from the name, or add a period at the end of it. Keep the underscore in _domainkey and do not add another one before the token. If your DNS host rejects underscores in record names, contact its support, because the underscore is required.
Mail carries only the amazonses.com signature
Verifying only an email address does not set up DKIM for its domain. Verify the domain identity. If you also verified one specific address, its settings override the domain's. Open that identity and confirm DKIM signatures is enabled, or delete the identity so the address follows the domain.
amazonses.com shows up in DMARC reports
There are two reasons. The default MAIL FROM uses a subdomain of amazonses.com, and SES automatically adds the d=amazonses.com signature. AWS says that signature is required for complaint feedback loops and that you can ignore it. Confirm that the row also has a pass aligned with your domain.
The custom MAIL FROM stays Pending or turns Failed
The subdomain needs exactly one MX record. With two, the setup fails. SES tries to detect the record for 72 hours and then marks it Failed, and you have to restart the setup. In Pending, TemporaryFailure and Failed, SES applies your Behavior on MX failure choice. With Use default MAIL FROM domain, mail goes out through a subdomain of amazonses.com and SPF stops aligning. With Reject message, SES refuses the send and returns the error MailFromDomainNotVerified.
Sending from another Region or AWS account
DKIM setup does not carry over between AWS accounts, or between Regions unless you use a DEED replica. Each AWS account needs its own setup and records. Each Region does too, unless you use a DEED replica. If you remove the records, SES disables signing in that Region or account and tells you by email. If you get a revocation notice, publish the records again within the period it gives. After a revocation, you have to redo the setup from the beginning.
Strict alignment breaks DMARC
With adkim=s, verify and sign with the exact From domain, including a sending subdomain. With aspf=s, rely on aligned DKIM when the custom MAIL FROM differs. Changing alignment to relaxed affects the whole domain and requires a deliberate policy decision; do not remove strict tags automatically.
Switching between Easy DKIM and BYODKIM
AWS warns that SES does not sign with the old method while the new one is pending, so mail can go out with no DKIM signature. AWS suggests using a subdomain as an intermediate step, or making the change during downtime.
Different results at Microsoft Outlook
AWS reports that Microsoft Enterprise Outlook validates only one of the two DKIM signatures, chosen at random. Aligned SPF through a custom MAIL FROM gives those messages a second route.
If DMARC still fails, see Amazon SES DMARC fail.