Migadu + Hostinger
Set up Migadu email on Hostinger
The records Migadu needs, written with the field names Hostinger uses (Name, Mail server, TXT value, Content), 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 Hostinger: In hPanel, go to Domains and click Manage next to your domain. Open DNS / Nameservers on the left. Use the Manage DNS records section.
- 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 | Name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Name | @ | Value | Copy from Migadu admin Not yet confirmed by us | Priority | n/a | TTL | 14400 seconds (4 hours) |
| MX records Where incoming email goes | Type | MX | Name | @ | Value | aspmx1.migadu.com | Priority | 10 | TTL | 14400 seconds (4 hours) |
| MX records Where incoming email goes | Type | MX | Name | @ | Value | aspmx2.migadu.com | Priority | 20 | TTL | 14400 seconds (4 hours) |
| SPF record Which servers may send as you | Type | TXT | Name | @ | Value | v=spf1 include:spf.migadu.com -all | Priority | n/a | TTL | 14400 seconds (4 hours) |
| DKIM A signature on every message | Type | CNAME | Name | key1._domainkey | Value | key1.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | 14400 seconds (4 hours) |
| DKIM A signature on every message | Type | CNAME | Name | key2._domainkey | Value | key2.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | 14400 seconds (4 hours) |
| DKIM A signature on every message | Type | CNAME | Name | key3._domainkey | Value | key3.yourdomain.com._domainkey.migadu.com | Priority | n/a | TTL | 14400 seconds (4 hours) |
| DMARC record What to do with fakes · recommended | Type | TXT | Name | _dmarc | Value | v=DMARC1; p=quarantine; | Priority | n/a | TTL | 14400 seconds (4 hours) |
Step by step in Hostinger
Verify your domain
Your email provider needs proof that you control this domain before it accepts email for it.
- Type
- TXT
- Name
-
@ - TXT 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 Hostinger
- In Manage DNS records, choose TXT as the type.
- Enter the Name (@ for the root, or only the prefix such as _dmarc) and the TXT value.
- Click Add Record.
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
- Name
-
@ - Priority
- 10
- Mail server
-
aspmx1.migadu.com
- Type
- MX
- Name
-
@ - Priority
- 20
- Mail server
-
aspmx2.migadu.com
In Hostinger
- In Manage DNS records, choose MX as the type.
- Enter @ as the Name, your provider's mail server, and the Priority. Keep the default TTL unless your provider asks otherwise.
- Click Add Record.
- 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
- Name
-
@ - TXT 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 Hostinger
- In Manage DNS records, choose TXT as the type.
- Enter the Name (@ for the root, or only the prefix such as _dmarc) and the TXT value.
- Click Add Record.
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
- Name
-
key1._domainkey - Content
-
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
- Name
-
key2._domainkey - Content
-
key2.yourdomain.com._domainkey.migadu.com
- Type
- CNAME
- Name
-
key3._domainkey - Content
-
key3.yourdomain.com._domainkey.migadu.com
In Hostinger
- In Manage DNS records, choose CNAME as the type.
- Enter the name (only the prefix) and the content your provider gives you.
- Click Add Record.
- 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
- Name
-
_dmarc - TXT 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 Hostinger
- In Manage DNS records, choose TXT as the type.
- Enter the Name (@ for the root, or only the prefix such as _dmarc) and the TXT value.
- Click Add Record.
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 Hostinger’s words.
Common mistakes with Migadu on Hostinger
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.
Hostinger: Delete Hostinger Email's MX records
If the domain was set up for Hostinger Email, the zone contains MX records for mx1.hostinger.com and mx2.hostinger.com. Delete them before adding another provider's MX records.
Hostinger: Clear out old email records
Hostinger recommends removing any existing MX, SPF, DKIM and DMARC records that point to other email services, because conflicting records cause delivery problems.
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Migadu on Hostinger, then send you the check results.
Migadu on Hostinger: questions
Where do I add Migadu DNS records in Hostinger?
In hPanel, go to Domains and click Manage next to your domain. Open DNS / Nameservers on the left. Use the Manage DNS records section. Add each record there, one at a time.
What goes in the Name field at Hostinger?
Enter @ 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. Hostinger adds your domain automatically.
Do I need to delete my existing MX records at Hostinger?
Yes. Mail servers deliver to every MX record you publish, so keep only the Migadu MX records and delete the rest. If the domain was set up for Hostinger Email, the zone contains MX records for mx1.hostinger.com and mx2.hostinger.com. Delete them before adding another provider's MX records. Hostinger recommends removing any existing MX, SPF, DKIM and DMARC records that point to other email services, because conflicting records cause delivery problems.
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.
How long until Migadu email works on Hostinger?
Hostinger says DNS changes can take up to 24 hours to fully propagate.
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.
- Hostinger Email MX records (Hostinger Help) Checked October 21, 2026
- How to manage DNS records at Hostinger (Hostinger Help) Checked October 21, 2026
- How to manage MX records at Hostinger (Hostinger Help) Checked October 21, 2026
- How to manage TXT records at Hostinger (Hostinger Help) Checked October 21, 2026
- How to set up a domain for Google Workspace Email at Hostinger (Hostinger Help) 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 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