Email provider
Migadu DNS records
Privacy-focused email hosting priced per domain, not per mailbox.
Where is your domain's DNS managed?
Each guide below uses that host's field names, steps and known problems.
- Amazon Route 53 Migadu on Amazon Route 53
- Bluehost Migadu on Bluehost
- Cloudflare Migadu on Cloudflare
- DreamHost Migadu on DreamHost
- GoDaddy Migadu on GoDaddy
- Hostinger Migadu on Hostinger
- IONOS Migadu on IONOS
- Name.com Migadu on Name.com
- Namecheap Migadu on Namecheap
- Network Solutions Migadu on Network Solutions
- OVHcloud Migadu on OVHcloud
- Porkbun Migadu on Porkbun
- SiteGround Migadu on SiteGround
- Squarespace Domains Migadu on Squarespace Domains
- Wix Migadu on Wix
- WordPress.com Migadu on WordPress.com
The records Migadu needs
These are the values for any DNS host. Field names differ between hosts, so use the host guides above for the exact boxes to fill in.
| Record | Type | Host / Name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Host / Name | @ | Value | Copy from Migadu admin Not yet confirmed by us | Priority | n/a | TTL | Default |
| MX records Where incoming email goes | Type | MX | Host / Name | @ | Value | aspmx1.migadu.com | Priority | 10 | TTL | Default |
| MX records Where incoming email goes | Type | MX | Host / Name | @ | Value | aspmx2.migadu.com | Priority | 20 | TTL | Default |
| SPF record Which servers may send as you | Type | TXT | Host / Name | @ | Value | v=spf1 include:spf.migadu.com -all | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Host / Name | key1._domainkey | Value | key1.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Host / Name | key2._domainkey | Value | key2.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Host / 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 | Host / Name | _dmarc | Value | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com | Priority | n/a | TTL | Default |
Notes on each record
What Migadu's documentation says about each record, in one place.
SPF SPF record
- 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.
DKIM DKIM
- 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.
DMARC DMARC record
- Start with p=none (no action) and read the reports for a while. Replace the report address with a mailbox you actually read.
- Migadu suggests v=DMARC1; p=quarantine; which asks receivers to treat failing mail as suspicious (usually spam). Move to it once SPF and DKIM pass.
Common Migadu mistakes
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.
Check your Migadu DNS
Enter your domain to see which records are in place.