Guide
Add SPF, DKIM, DMARC and MX records in Amazon Route 53
How to add SPF, DKIM, DMARC and MX records in Amazon Route 53, with the quoting rules TXT records need.
Updated
Email authentication comes down to a handful of DNS records: SPF, DKIM and DMARC, plus MX to
receive mail. Your email provider tells you what they should say; this guide shows where to put
them in Amazon Route 53. You can tell your DNS is at Amazon Route 53 when your domain’s name servers look like awsdns-… (.com, .net, .org or .co.uk); the WHOIS lookup shows them.
Open the record editor
- Open the Route 53 console in AWS and choose Hosted zones.
- Select your domain’s hosted zone and click Create record.
- Choose the record type, fill in Record name and Value, and save. Leave TTL at its default.
What to enter for each record
| Record | Type | Record name | Value |
|---|---|---|---|
| SPF | TXT | leave empty | v=spf1 include:… ~all |
| DKIM | TXT or CNAME, as your provider says | selector._domainkey (e.g. google._domainkey) | The key or target your provider gives you |
| DMARC | TXT | _dmarc | v=DMARC1; p=none; rua=mailto:… |
| MX | MX | leave empty | Your provider’s mail server, with its priority |
For the domain itself, leave Record name empty.
For any other name, type only the part before your domain: _dmarc, not _dmarc.example.com.
Amazon Route 53 specifics
- Leave Record name empty for the domain itself.
- TXT values must be in double quotes. A value longer than 255 characters (a 2048-bit DKIM key) goes in as several quoted strings on one line: "first part" "second part".
- MX records take the priority in the value itself: 10 mail.example.com.
- Route 53 keeps all values of one name and type in a single record. To add to an existing TXT record, edit it and put the new value on its own line.
Mistakes that break email authentication
- The domain written twice. Typing the full name where the panel adds your
domain creates
_dmarc.example.com.example.com, which nothing looks up. Check the record with our DNS lookup. - A second SPF record. A domain may have only one TXT record starting
v=spf1; with two, SPF fails for all your mail. Edit the existing one and add the new include to it. - Old MX records left in place. When you switch email provider, delete the previous provider’s MX records, or some mail keeps going there.
- Checking too soon. A new record usually shows up within minutes, but a changed one can take as long as its old TTL. The DNS propagation checker shows who has the new value yet.
Records for your email provider
The exact records, and where to turn on DKIM, for common providers:
Using another provider? The SPF and DMARC generators build the records, and the health check shows what’s still missing.
Related tools
All toolsEmail Domain Health Check
SPF, DKIM, DMARC and MX checked together, with a score and a list of fixes.
DNS Propagation Checker
Ask 20 public DNS resolvers and the domain’s own servers, and see who has your change yet.
SPF Record Generator
Pick the services that send your email and get a ready-to-paste SPF record, lookups counted.
DNS Lookup
Look up A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV records for any domain.
More guides
- Add SPF, DKIM, DMARC and MX records in Cloudflare Where to add SPF, DKIM, DMARC and MX records in the Cloudflare dashboard, and the proxy setting that breaks DKIM.
- Add SPF, DKIM, DMARC and MX records in GoDaddy Where to add SPF, DKIM, DMARC and MX records in GoDaddy’s DNS manager, and the default records to replace.
- Add SPF, DKIM, DMARC and MX records in Namecheap Where to add SPF, DKIM, DMARC and MX records in Namecheap’s Advanced DNS, and why MX records go elsewhere.