Migadu + OVHcloud
Set up Migadu email on OVHcloud
The records Migadu needs, written with the field names OVHcloud uses (Subdomain, Target, 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 OVHcloud: Sign in to the OVHcloud Control Panel (ovh.com/manager). Under View all my activity, select your domain name. Open the DNS zone tab.
- 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 | Subdomain | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Subdomain | 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 | Subdomain | Leave empty | Value | aspmx1.migadu.com. | Priority | 10 | TTL | Default |
| MX records Where incoming email goes | Type | MX | Subdomain | Leave empty | Value | aspmx2.migadu.com. | Priority | 20 | TTL | Default |
| SPF record Which servers may send as you | Type | TXT | Subdomain | Leave empty | Value | v=spf1 include:spf.migadu.com -all | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Subdomain | key1._domainkey | Value | key1.yourdomain.com._domainkey.migadu.com. | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Subdomain | key2._domainkey | Value | key2.yourdomain.com._domainkey.migadu.com. | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | CNAME | Subdomain | key3._domainkey | Value | key3.yourdomain.com._domainkey.migadu.com. | Priority | n/a | TTL | Default |
| DMARC record What to do with fakes · recommended | Type | TXT | Subdomain | _dmarc | Value | v=DMARC1; p=quarantine; | Priority | n/a | TTL | Default |
Step by step in OVHcloud
Verify your domain
Your email provider needs proof that you control this domain before it accepts email for it.
- Type
- TXT
- Subdomain
- 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 OVHcloud
- Select the Add an entry tile.
- In Extended records, choose TXT.
- Fill in Subdomain (empty for your bare domain) and Value.
- Select Next, then Confirm.
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
- Subdomain
- Leave this field empty
- Priority
- 10
- Target
-
aspmx1.migadu.com.
- Type
- MX
- Subdomain
- Leave this field empty
- Priority
- 20
- Target
-
aspmx2.migadu.com.
In OVHcloud
- Select the Add an entry tile.
- In Mail records, choose MX.
- Leave Subdomain empty, enter the Priority and the Target (ending with a dot), and a TTL.
- Select Next, then Confirm.
- Delete older MX records with the trash icon in the Actions column.
- 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
- Subdomain
- 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 OVHcloud
- Select the Add an entry tile.
- In Extended records, choose TXT.
- Fill in Subdomain (empty for your bare domain) and Value.
- Select Next, then Confirm.
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
- Subdomain
-
key1._domainkey - Target
-
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
- Subdomain
-
key2._domainkey - Target
-
key2.yourdomain.com._domainkey.migadu.com.
- Type
- CNAME
- Subdomain
-
key3._domainkey - Target
-
key3.yourdomain.com._domainkey.migadu.com.
In OVHcloud
- Select the Add an entry tile.
- In Pointer records, choose CNAME.
- Fill in Subdomain and the Target (ending with a dot).
- Select Next, then Confirm.
- 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
- Subdomain
-
_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 OVHcloud
- Select the Add an entry tile.
- In Extended records, choose TXT.
- Fill in Subdomain (empty for your bare domain) and Value.
- Select Next, then Confirm.
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 OVHcloud’s words.
Common mistakes with Migadu on OVHcloud
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.
OVHcloud: End targets with a dot
By default OVHcloud treats a target without a final dot as relative and adds your domain to the end. End MX and CNAME targets with a dot, for example mx1.example.com.
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Migadu on OVHcloud, then send you the check results.
Migadu on OVHcloud: questions
Where do I add Migadu DNS records in OVHcloud?
Sign in to the OVHcloud Control Panel (ovh.com/manager). Under View all my activity, select your domain name. Open the DNS zone tab. Add each record there, one at a time.
What goes in the Subdomain field at OVHcloud?
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. OVHcloud adds your domain automatically.
Do I need to delete my existing MX records at OVHcloud?
Yes. Mail servers deliver to every MX record you publish, so keep only the Migadu MX records and delete the rest. By default OVHcloud treats a target without a final dot as relative and adds your domain to the end. End MX and CNAME targets with a dot, for example mx1.example.com.
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 OVH 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
Migadu on other hosts
- Migadu on Amazon Route 53
- 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 Porkbun
- Migadu on SiteGround
- Migadu on Squarespace Domains
- Migadu on Wix
- Migadu on WordPress.com