Skip to content
DMARC Pulse
Guides

Hostinger

How to set up SPF, DKIM and DMARC for Hostinger

Set up SPF, the three DKIM CNAMEs and DMARC for Hostinger Email in hPanel's DNS Zone, or at your own DNS host, and fix the problems Hostinger users hit.

Before you start

This guide sets up SPF, DKIM and DMARC for Hostinger Email. SPF lists the servers allowed to send mail for your domain. DKIM signs with a private key; receivers verify using the public key in DNS. DMARC tells receivers how you want failures handled and asks them to send you reports.

Check your nameservers first. They are the servers that answer DNS queries for your domain. Records in Hostinger's DNS zone take effect only when the domain uses Hostinger nameservers. If your nameservers point elsewhere, add the same records at that provider.

To edit DNS in hPanel, Hostinger's control panel, open Domains, select your domain and open DNS Zone. Some Hostinger articles still call this screen DNS / Nameservers.

Automatic setup changes MX as well as SPF/DKIM. If mail currently routes through an external provider, keep that route and use manual authentication unless you have planned a full mail migration. With Hostinger nameservers you can also use automatic setup. In Emails, click Mailboxes next to your domain, open Domain settings, click Connect automatically and confirm with Yes, proceed. Hostinger says this adds the MX, SPF and DKIM records. DMARC is not on that list, so follow Step 3 either way.

Step 1: SPF

Create a TXT record with Name @ and this value:

TXT
v=spf1 include:_spf.mail.hostinger.com ~all

For a subdomain, enter its name in the Name field, such as shop.

A domain must have only one SPF record. If you already have one, add the include to it. Hostinger's own example merges a second sender on one line:

TXT
v=spf1 include:_spf.mail.hostinger.com include:OTHER-PROVIDER-INCLUDE ~all

Replace the placeholder with the value your other provider documents. If you send only through another provider, use that provider's include alone.

Step 2: DKIM

Hostinger's default DKIM uses three CNAME records. A CNAME makes one DNS name point to another:

  • hostingermail-a._domainkey → hostingermail-a.dkim.mail.hostinger.com
  • hostingermail-b._domainkey → hostingermail-b.dkim.mail.hostinger.com
  • hostingermail-c._domainkey → hostingermail-c.dkim.mail.hostinger.com

The first part of each name is the selector, the label a receiver uses to find the key. Add these as CNAME records. Hostinger warns that signing fails if you add them as TXT.

Hostinger also offers a custom DKIM key, published as a TXT record. In Emails, click Mailboxes next to your domain, go to Custom DKIM and click Generate. Hostinger says to use a custom record, in place of the default ones, when you send through a third-party service. Verification can take up to 6 hours. The status moves from Unverified to Verifying to Verified, or shows Verification failed.

Step 3: DMARC

Look for an existing _dmarc record first. If there is none, create a TXT record with Name _dmarc:

Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

Replace the address with your DMARC Pulse reporting address, so you get readable reports. p=none asks receivers to take no action on failures. It only collects data.

Step 4: Check the result

In Emails, open Mailboxes next to your domain and go to Domain settings. Each record shows as connected, missing or incorrect, next to the value Hostinger expects. Then run the SPF checker, DKIM checker and DMARC checker on your domain.

Next, read your reports for alignment. DMARC passes only when SPF or DKIM passes for a domain that matches your From address. RFC 9989 calls this identifier alignment. Hostinger does not document which domain it uses in the DKIM d= tag or in the envelope sender, so confirm both in a real message or in your reports.

Preserve any existing policy and report destinations. For a first deployment, monitor at p=none. After every legitimate sender passes with alignment, assess p=quarantine. Consider p=reject separately, including mailing-list and forwarding risks; it is optional. Receivers decide how to handle individual messages.

Common problems

  • Editing Hostinger's zone while the domain uses other nameservers. Hostinger saves the change, but it applies only once the nameservers point back to Hostinger. Make the change where your nameservers point.
  • Two SPF records after adding a service. Compare Reach’s combined value with your current record. Preserve every still-needed sender, merge the required include into one SPF and check lookup limits before saving. Never trust a generated value to inventory other services. See multiple SPF records.
  • A DKIM checker reports an empty key for selector b or c. On 2026-11-09, hostingermail-a.dkim.mail.hostinger.com returned a public key, while the b and c targets returned v=DKIM1;p=. In DKIM, an empty p= means the key is revoked. Hostinger does not explain how it uses the three selectors. Read the s= value in the DKIM-Signature header of a sent message and test that selector.
  • The Host field doubles your domain. Some DNS providers append your domain automatically. Enter only hostingermail-a._domainkey, with no trailing dot or space.
  • The Generate button is greyed out. Hostinger requires removing old DKIM records before generating a custom key. Schedule a maintenance window and pause affected sending, or keep a tested aligned authentication fallback, before deletion. Publish and verify the replacement before resuming; never remove another service’s active key.
  • Two DMARC records, or a DMARC record with no reports. Receivers discard every record when a name returns more than one. Hostinger Reach's sample record is v=DMARC1; p=none, and without rua receivers send no aggregate reports. Keep one record that includes your rua address.
  • Gmail shows "Gmail couldn't verify that [domain] actually sent this message (and not a spammer)". Hostinger attributes this message to a missing SPF record. Confirm the record exists where your nameservers point, then allow up to 24 hours.
  • Website forms send through PHP mail. Hostinger calls phpmail() unreliable and recommends it for one-time sending and testing only. Send regular site mail through SMTP, and check the result in your reports.
  • Mail lands in spam with correct records. Hostinger says a new domain can still land in spam until it builds a reputation. Its warm-up guidance covers the first two to three weeks. Passing SPF, DKIM and DMARC does not guarantee inbox placement.

Frequently asked questions

What is the SPF record for Hostinger Email?
Hostinger lists v=spf1 include:_spf.mail.hostinger.com ~all, as a TXT record at @. A domain must have only one SPF record, so add any other sender to that same record.
I saw include:_spf.hostinger.com somewhere. Which one is right?
Use include:_spf.mail.hostinger.com, the only value in Hostinger's SPF article. A lookup of _spf.hostinger.com on 2026-11-09 returned no TXT record, and an include with no record makes SPF return permerror.
Do I need all three Hostinger DKIM CNAMEs?
Create all three. Hostinger's setup table lists hostingermail-a, hostingermail-b and hostingermail-c, and it does not offer a shorter set. Each must be a CNAME record, because a TXT record there makes signing fail.
Does Hostinger add a DMARC record automatically?
Hostinger's automatic setup lists MX, SPF and DKIM. DMARC is not on that list, and the article recommends adding it yourself. Look for an existing _dmarc record first, because a domain must have only one.
Can I use custom DKIM and Hostinger's default DKIM together?
Yes. Hostinger says custom and default DKIM can be enabled at the same time and do not conflict. If you later remove the custom record, your mail goes back to the default DKIM record.
How long do DNS changes take at Hostinger?
Hostinger says most changes apply much sooner, but it allows up to 24 hours for DNS propagation. A custom DKIM key can take up to 6 hours to verify.

Sources consulted

RFC 9989: DMARC
checked 2026-11-09
RFC 7208: SPF
checked 2026-11-09
RFC 6376: DKIM
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.