Hostinger Email + Cloudflare
Set up Hostinger Email email on Cloudflare
The records Hostinger Email needs, written with the field names Cloudflare uses (Name, Mail server, Content, Target), in the order to add them.
- 4 steps
- 7 DNS records
- Sources checked October 21, 2026
Before you start
- Have your Hostinger Email account ready. Some values are unique to your account and come from the Hostinger hPanel.
- Open DNS at Cloudflare: Sign in to the Cloudflare dashboard and select your domain. Open the DNS Records page.
- 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 Hostinger hPanel” are unique to your account.
| Record | Type | Name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| MX records Where incoming email goes | Type | MX | Name | @ | Value | mx1.hostinger.com | Priority | 5 | TTL | Auto |
| MX records Where incoming email goes | Type | MX | Name | @ | Value | mx2.hostinger.com | Priority | 10 | TTL | Auto |
| SPF record Which servers may send as you | Type | TXT | Name | @ | Value | v=spf1 include:_spf.mail.hostinger.com ~all | Priority | n/a | TTL | Auto |
| DKIM A signature on every message | Type | CNAME | Name | hostingermail-a._domainkey | Value | hostingermail-a.dkim.mail.hostinger.com | Priority | n/a | TTL | Auto |
| DKIM A signature on every message | Type | CNAME | Name | hostingermail-b._domainkey | Value | hostingermail-b.dkim.mail.hostinger.com | Priority | n/a | TTL | Auto |
| DKIM A signature on every message | Type | CNAME | Name | hostingermail-c._domainkey | Value | hostingermail-c.dkim.mail.hostinger.com | Priority | n/a | TTL | Auto |
| DMARC record What to do with fakes · recommended | Type | TXT | Name | _dmarc | Value | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com | Priority | n/a | TTL | Auto |
Step by step in Cloudflare
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
- 5
- Mail server
-
mx1.hostinger.com
- Hostinger's manual guide uses the host's default TTL.
- Type
- MX
- Name
-
@ - Priority
- 10
- Mail server
-
mx2.hostinger.com
In Cloudflare
- On the DNS Records page, select Add record.
- Choose MX as the Type.
- Fill in Name, Mail server and Priority.
- Select Save.
- Delete any other MX records: select Edit on each one, then Delete, and confirm.
- 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
-
@ - Content
-
v=spf1 include:_spf.mail.hostinger.com ~all
- Keep a single SPF record. If you also use a marketing or sending service, merge it into the same line, for example v=spf1 include:_spf.mail.hostinger.com include:emailmktprovider.tld ~all.
- When moving DNS manually, delete any old SPF record before adding this one.
In Cloudflare
- On the DNS Records page, select Add record.
- Choose TXT as the Type.
- Fill in Name and Content.
- Select Save.
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
-
hostingermail-a._domainkey - Target
-
hostingermail-a.dkim.mail.hostinger.com
- Type
- CNAME
- Name
-
hostingermail-b._domainkey - Target
-
hostingermail-b.dkim.mail.hostinger.com
- Type
- CNAME
- Name
-
hostingermail-c._domainkey - Target
-
hostingermail-c.dkim.mail.hostinger.com
In Cloudflare
- On the DNS Records page, select Add record.
- Choose CNAME as the Type.
- Fill in Name and Target.
- Set Proxy status to DNS only (grey cloud).
- Select Save.
- 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 - Content
-
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
- Replace the report address with a mailbox you read.
In Cloudflare
- On the DNS Records page, select Add record.
- Choose TXT as the Type.
- Fill in Name and Content.
- Select Save.
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 Cloudflare’s words.
Common mistakes with Hostinger Email on Cloudflare
Adding a second SPF record
Hostinger says a domain should have a single SPF record. Merge every sender into one line.
Adding only one DKIM record
Hostinger Email uses three DKIM CNAME records: hostingermail-a, -b and -c. Add all three.
Cloudflare: Keep email CNAMEs on DNS only
Set Proxy status to DNS only (grey cloud) for DKIM and verification CNAME records. Cloudflare says records used for email or domain verification should not be proxied, and may block proxying DKIM CNAMEs.
Cloudflare: Turn off Cloudflare Email Routing first
If Email Routing is on, Cloudflare has added locked MX records (route1, route2 and route3.mx.cloudflare.net) and an SPF record with include:_spf.mx.cloudflare.net. Unlock them or disable Email Routing (Compute > Email Service > Email Routing > your domain > Settings) before switching to another provider. Email Routing can't be used with an outside mail server.
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Hostinger Email on Cloudflare, then send you the check results.
Hostinger Email on Cloudflare: questions
Where do I add Hostinger Email DNS records in Cloudflare?
Sign in to the Cloudflare dashboard and select your domain. Open the DNS Records page. Add each record there, one at a time.
What goes in the Name field at Cloudflare?
Enter @ for records on your bare domain, such as MX and SPF. For the others, enter only the part before your domain, for example hostingermail-a._domainkey. Cloudflare adds your domain automatically.
Do I need to delete my existing MX records at Cloudflare?
Yes. Mail servers deliver to every MX record you publish, so keep only the Hostinger Email MX records and delete the rest. If Email Routing is on, Cloudflare has added locked MX records (route1, route2 and route3.mx.cloudflare.net) and an SPF record with include:_spf.mx.cloudflare.net. Unlock them or disable Email Routing (Compute > Email Service > Email Routing > your domain > Settings) before switching to another provider. Email Routing can't be used with an outside mail server.
Where do I get my Hostinger Email DKIM record?
Use the value shown in 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.
- Cloudflare DNS: TXT, CNAME, MX Records (Zoho Mail Help) Checked October 21, 2026
- Connect your DNS records at Cloudflare to Microsoft 365 (Microsoft Learn) Checked October 21, 2026
- Create zone apex record (Cloudflare Docs) Checked October 21, 2026
- Email Routing: domain configuration (Cloudflare Docs) Checked October 21, 2026
- Hostinger Email MX records (Hostinger Help) Checked October 21, 2026
- Manage DNS records (Cloudflare Docs) Checked October 21, 2026
- Proxy status (Cloudflare Docs) Checked October 21, 2026
- Set up a domain for Hostinger Mail manually (Hostinger Help) Checked October 21, 2026
- What is the SPF record for Hostinger Email? (Hostinger Help) Checked October 21, 2026
Hostinger Email on other hosts
- Hostinger Email on Amazon Route 53
- Hostinger Email on Bluehost
- Hostinger Email on DreamHost
- Hostinger Email on GoDaddy
- Hostinger Email on Hostinger
- Hostinger Email on IONOS
- Hostinger Email on Name.com
- Hostinger Email on Namecheap
- Hostinger Email on Network Solutions
- Hostinger Email on OVHcloud
- Hostinger Email on Porkbun
- Hostinger Email on SiteGround
- Hostinger Email on Squarespace Domains
- Hostinger Email on Wix
- Hostinger Email on WordPress.com