Set up SPF, DKIM, and DMARC on Hostinger
Add SPF, DKIM, and DMARC as TXT records in Hostinger's hPanel DNS Zone Editor, using @ for the root domain and _dmarc for DMARC — only works when the domain uses Hostinger's nameservers (ns1/ns2.dns-parking.com).
Where to add records on Hostinger
hPanel → top nav "Domains" → click the domain → left menu "DNS / Nameservers" → the "DNS records" section (the "Add new record" form). Alternate path for a domain attached to Hostinger hosting: hPanel → Websites → "Manage" → sidebar "Advanced" → "DNS Zone Editor".
- Log in to hPanel, open 'Domains' in the top navigation, and click the domain you're configuring (for a hosted site use Websites → Manage → Advanced → DNS Zone Editor instead).
- Open the 'DNS / Nameservers' page and confirm the domain actually uses Hostinger's nameservers (ns1.dns-parking.com / ns2.dns-parking.com). If the NS point elsewhere (e.g. Cloudflare), the DNS Zone Editor is ignored — add the records at that DNS provider instead.
- In the 'DNS records' section, use the 'Add new record' form and set the Type dropdown to 'TXT'.
- In the Name field, enter '@' for the root domain (SPF and the DMARC parent), '_dmarc' for the DMARC policy, or the provider's selector (e.g. 'selector._domainkey') for a third-party DKIM TXT key. Enter only the label — Hostinger appends your domain automatically, so do NOT type the full FQDN.
- Paste the record into the 'TXT value' field exactly as given, with no surrounding double-quotes.
- Leave TTL at the default 14400 (4 hours), or lower it (e.g. 300) while actively testing, then click 'Add Record' to save.
- Wait for propagation (Hostinger lists up to 24 hours) and verify with a DNS lookup tool before relying on the record.
The three records on Hostinger
SPF Sender Policy Framework
Type = TXT, Name = @ (the root domain — Hostinger uses @, not a blank field). For Hostinger's mailbox email the value is 'v=spf1 include:_spf.mail.hostinger.com ~all'. NOTE the product split: the newer Hostinger Reach uses a different include — 'v=spf1 include:_spf.reach.hostinger.com ~all' — so copy the exact value from your own email/Reach dashboard rather than assuming _spf.mail. Only ONE SPF record is allowed per domain, and if a domain on Hostinger nameservers has Hostinger Email/Reach enabled, Hostinger auto-adds a default SPF TXT to the zone — EDIT that existing record to merge all senders into a single v=spf1 string instead of adding a second SPF.
DKIM DomainKeys Identified Mail
DKIM keys come from your sending provider, not Hostinger's DNS panel — you paste what they give you. Mind the type split: Hostinger's OWN email service uses CNAME DKIM records, not TXT. Hostinger Email = three CNAMEs (hostingermail-a._domainkey, hostingermail-b._domainkey, hostingermail-c._domainkey → hostingermail-a/b/c.dkim.mail.hostinger.com, TTL 300); Hostinger Reach = two CNAMEs (reach-a._domainkey, reach-b._domainkey → reach-a/b.dkim.reach.hostinger.com). On Hostinger nameservers these are usually created automatically — add them as CNAME (not TXT) or signing fails. For a third-party provider (Google Workspace, etc.) you instead add a TXT record at their selector (e.g. 'google._domainkey') and paste the long public key as-is; Hostinger accepts the full key in one field, so don't split it.
DMARC reporting and policy
Type = TXT, Name = _dmarc (just '_dmarc' — Hostinger appends your domain, so do NOT enter '_dmarc.yourdomain.com'). Start with 'v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com' to monitor, then tighten p= to quarantine/reject once SPF and DKIM are passing. Only one DMARC record per domain.
Need the record values? Generate a valid SPF and DMARC record with the record generator, then learn what each one does: SPF, DKIM, DMARC.
Hostinger gotchas
- The DNS Zone Editor only controls DNS when the domain uses Hostinger's nameservers (ns1/ns2.dns-parking.com). If you've pointed NS at Cloudflare or another DNS host, records added here do nothing — and don't try to repoint NS in the zone editor; that's changed at the registrar.
- The root domain uses '@', not a blank/empty Name field, and Hostinger auto-appends your domain to whatever label you type — so enter '_dmarc' (not the full _dmarc.example.com) or you'll create _dmarc.example.com.example.com.
- Don't wrap TXT values in extra double-quotes. Hostinger stores the raw value; adding your own quotes can produce a double-quoted, invalid record.
- Only one SPF record is allowed, and when a domain on Hostinger NS has Hostinger Email/Reach turned on, Hostinger auto-adds a default SPF TXT — edit/merge it instead of adding a second SPF, or receivers will fail validation.
- Two different Hostinger email products = two different SPF includes and DKIM selectors: Hostinger Email (_spf.mail.hostinger.com / hostingermail-* CNAMEs) vs Hostinger Reach (_spf.reach.hostinger.com / reach-a,b CNAMEs). Using the wrong set silently breaks auth — copy the exact values from your own dashboard.
- Default TTL is 14400 seconds (4 hours) and propagation can take up to 24 hours; lower TTL to ~300 before changes if you want faster iteration while testing.
Records set. Now make sure you actually land.
SPF, DKIM, and DMARC on Hostinger get you authenticated, but inbox placement also needs sender reputation and domain warmup. Scheduler Zero handles both so your cold email reaches the inbox.