Domain authentication
The DNS records that prove your mail is yours: SPF, DKIM, DMARC and a custom MAIL FROM subdomain.
Overview
Mailbox providers trust mail that proves where it came from. You prove it with DNS records on your sending domain: the domain in your From address, or a parent of it. Campaigns are blocked until the domain is verified, and the From address must be on that domain.
Settings → Sending lists the exact records for your domain and provider, with copy buttons and a live status for each. For Amazon SES you will publish:
| Purpose | Type | Name | Value |
|---|---|---|---|
| DKIM (×3) | CNAME | {token}._domainkey.example.com | {token}.dkim.amazonses.com |
| MAIL FROM | MX | bounce.example.com | 10 feedback-smtp.{region}.amazonses.com |
| SPF | TXT | bounce.example.com | v=spf1 include:amazonses.com ~all |
| DMARC | TXT | _dmarc.example.com | v=DMARC1; p=none; rua=mailto:dmarc@example.com |
Other providers ask for their own set, usually DKIM plus a return-path or SPF record, and sometimes a verification TXT record. The page shows exactly which ones your provider needs. See Sending providers.
DKIM
DKIM signs every message with a key published in your DNS, so receivers can tell the mail was not altered and really came from your domain. With SES this is Easy DKIM: three CNAME records that point at keys Amazon manages and rotates for you.
Custom MAIL FROM and SPF
Every email has a hidden return-path (the MAIL FROM address) where bounces are sent. By default it is your provider's domain, which means SPF passes for them, not you. A custom MAIL FROM subdomain such as bounce.example.com makes SPF pass on your own domain, which DMARC needs for alignment.
- The subdomain is
bounceunless you change it. It needs an MX record (so bounces come back) and an SPF TXT record. - Publish exactly one SPF record per name. Two
v=spf1records on the same name make SPF fail. - Your root domain's own SPF record, if you have one, does not need to change.
DMARC
DMARC tells receivers what to do with mail that fails SPF and DKIM alignment, and where to send reports. Gmail and Yahoo require it for bulk senders. The platform does not create it for you, because it covers all mail from your domain, not just newsletters. If you don't have one yet, start with monitoring only:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"Once reports show all your legitimate mail passing, move to p=quarantine and later p=reject. Any valid policy passes the platform's check.
Daily checks
Records get deleted by accident, often during a DNS host migration. The platform checks your records itself on public DNS rather than taking the provider's word for it: right after you publish them (for providers other than SES, every minute for 20 minutes), then every day. If a record that used to pass stops passing, a banner names it at the top of the app and on the Sending page. Recheck now runs the same check on demand and, for SES, also refreshes the domain's verification status.