Migadu + Amazon Route 53
Set up Migadu email on Amazon Route 53
The records Migadu needs, written with the field names Amazon Route 53 uses (Record name, Value), in the order to add them.
- 5 steps
- 8 DNS records
- Sources checked October 21, 2026
Before you start
- Have your Migadu account ready. Some values are unique to your account and come from the Migadu admin.
- Open DNS at Amazon Route 53: Open the Route 53 console and select Registered domains, then your domain. Select Manage DNS, then the hosted zone for your domain. If no hosted zone exists, create one first.
- Keep both tabs open and add the records below one at a time.
Records to add
Copy each value with the button next to it. Rows marked “Copy from Migadu admin” are unique to your account.
| Record | Type | Record name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Record name | Leave empty | Value | Copy from Migadu admin Not yet confirmed by us | Priority | n/a | TTL | Default |
| MX records Where incoming email goes | Type | MX | Record name | Leave empty | Value | 10 aspmx1.migadu.com | Priority | in the value | TTL | Default |
| MX records Where incoming email goes | Type | MX | Record name | Leave empty | Value | 20 aspmx2.migadu.com | Priority | in the value | TTL | Default |
| SPF record Which servers may send as you | Type | TXT | Record name | Leave empty | Value | "v=spf1 include:spf.migadu.com -all" | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Record name | key1._domainkey | Value | key1.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Record name | key2._domainkey | Value | key2.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Record name | key3._domainkey | Value | key3.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | Default |
| DMARC record What to do with fakes · recommended | Type | TXT | Record name | _dmarc | Value | "v=DMARC1; p=quarantine;" | Priority | n/a | TTL | Default |
Step by step in Amazon Route 53
Verify your domain
Your email provider needs proof that you control this domain before it accepts email for it.
- Type
- TXT
- Record name
- Leave this field empty
- Value
- Copy it from Migadu admin (see below)
Where to find your value
Copy the verification record shown for your domain in the Migadu admin (admin.migadu.com).
We haven’t been able to confirm this value from Migadu's public docs yet, so we don’t show one.
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Point your MX records
MX records tell every other mail server where to deliver email for your domain. They must point to your provider and nowhere else.
- Type
- MX
- Record name
- Leave this field empty
- Value
-
10 aspmx1.migadu.com
- Type
- MX
- Record name
- Leave this field empty
- Value
-
20 aspmx2.migadu.com
In Amazon Route 53
- In the hosted zone, select Create record.
- Leave Record name empty, choose MX as Record type, and keep Simple routing.
- In Value, enter the priority, a space, then the mail server (for example 10 mail.example.com). Put each mail server on its own line in the same record.
- Select Create records, then delete any older MX records.
- Repeat for each MX record above.
Add the SPF record
SPF is a TXT record that lists the services allowed to send email from your domain, so receivers can spot forgeries.
- Type
- TXT
- Record name
- Leave this field empty
- Value
-
"v=spf1 include:spf.migadu.com -all"
- A domain must have only one SPF record. If you already have one, add include:spf.migadu.com to it instead of creating a second.
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Set up DKIM
DKIM publishes a public key so receivers can confirm your messages really came from you and were not changed on the way.
- Type
- CNAME
- Record name
-
key1._domainkey - Value
-
key1.yourdomain.com._domainkey.migadu.com
- The target includes your own domain name, so each domain's DKIM target is different.
- Migadu's example ends the target with a period. Add it only if your DNS host asks for fully qualified names.
- Type
- CNAME
- Record name
-
key2._domainkey - Value
-
key2.yourdomain.com._domainkey.migadu.com
- Type
- CNAME
- Record name
-
key3._domainkey - Value
-
key3.yourdomain.com._domainkey.migadu.com
In Amazon Route 53
- Select Create record.
- Enter the Record name (for example autodiscover) and choose CNAME.
- Enter the target in Value.
- Select Create records.
- Repeat for each CNAME record above.
Add the DMARC record (recommended)
DMARC tells receivers what to do with mail that fails SPF and DKIM, and where to send reports about it.
- Type
- TXT
- Record name
-
_dmarc - Value
-
"v=DMARC1; p=quarantine;"
- This is the value Migadu suggests. It asks receivers to treat failing mail as suspicious (usually spam), so make sure SPF and DKIM pass first.
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Check your setup
Once the records are saved, run a live check. We look up your domain in public DNS and tell you what is right, missing or wrong, with the fix in Amazon Route 53’s words.
Common mistakes with Migadu on Amazon Route 53
Using a DKIM target without your domain
Each DKIM CNAME points to a target that contains your own domain, like key1.yourdomain.com._domainkey.migadu.com. Copy the full target for your domain.
Adding only one DKIM record
Migadu uses three DKIM CNAME records: key1, key2 and key3. Add all three.
Adding a second SPF record
A domain must have only one SPF record. If you already have one, add include:spf.migadu.com to it.
Amazon Route 53: One TXT record per name
With simple routing, Route 53 keeps all TXT values for a name in the same record, one value per line. Add SPF next to a verification value instead of creating a second TXT record.
Amazon Route 53: Split long TXT values
A single quoted string can hold up to 255 characters. Split longer values, such as DKIM keys, into quoted pieces on one line: "part one" "part two".
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Migadu on Amazon Route 53, then send you the check results.
Migadu on Amazon Route 53: questions
Where do I add Migadu DNS records in Amazon Route 53?
Open the Route 53 console and select Registered domains, then your domain. Select Manage DNS, then the hosted zone for your domain. If no hosted zone exists, create one first. Add each record there, one at a time.
What goes in the Record name field at Amazon Route 53?
Leave it empty for records on your bare domain, such as MX and SPF. For the others, enter only the part before your domain, for example key1._domainkey. Amazon Route 53 adds your domain automatically.
Do I need to delete my existing MX records at Amazon Route 53?
Yes. Mail servers deliver to every MX record you publish, so keep only the Migadu MX records and delete the rest.
Where do I get my Migadu DKIM record?
Migadu DKIM records are CNAME records whose value includes your domain, for example key1.yourdomain.com._domainkey.migadu.com. Copy the exact values for your domain from the table on this page.
Sources
Every value and step on this page comes from these official pages. Dashboards change, so if something doesn’t match what you see, tell us.
- Connect your DNS records at Amazon Web Services (AWS) to Microsoft 365 (Microsoft Learn) Checked October 21, 2026
- Migadu API: Domains / Records Checked October 21, 2026
- RFC 7208: Sender Policy Framework (IETF) Checked October 21, 2026
- Supported DNS record types (Amazon Route 53 Developer Guide) Checked October 21, 2026
Migadu on other hosts
- Migadu on Bluehost
- Migadu on Cloudflare
- Migadu on DreamHost
- Migadu on GoDaddy
- Migadu on Hostinger
- Migadu on IONOS
- Migadu on Name.com
- Migadu on Namecheap
- Migadu on Network Solutions
- Migadu on OVHcloud
- Migadu on Porkbun
- Migadu on SiteGround
- Migadu on Squarespace Domains
- Migadu on Wix
- Migadu on WordPress.com
Other email providers on Amazon Route 53
- Fastmail on Amazon Route 53
- Google Workspace on Amazon Route 53
- Hostinger Email on Amazon Route 53
- iCloud+ Custom Email Domain on Amazon Route 53
- Microsoft 365 on Amazon Route 53
- Namecheap Private Email on Amazon Route 53
- Proton Mail on Amazon Route 53
- Rackspace Email on Amazon Route 53
- Titan Email on Amazon Route 53
- Zoho Mail on Amazon Route 53