The DNS records
The targets are the same for every domain; only the host changes when you sign mail for a subdomain. Hostinger's DKIM article lists the records with a TTL of 300 seconds.
Selector hostingermail-a
Type: CNAME · Host: hostingermail-a._domainkey
hostingermail-a.dkim.mail.hostinger.com
Selector hostingermail-b
Type: CNAME · Host: hostingermail-b._domainkey
hostingermail-b.dkim.mail.hostinger.com
Selector hostingermail-c
Type: CNAME · Host: hostingermail-c._domainkey
hostingermail-c.dkim.mail.hostinger.com
For a subdomain such as shop.example.com, Hostinger uses hosts like hostingermail-a._domainkey.shop with the same targets.
Set it up and turn on signing
- In hPanel, open Emails, click Mailboxes next to the account and choose Domain settings to see the DKIM records Hostinger expects.
- If the domain's nameservers point to Hostinger, click Connect automatically and you're done.
- If they point elsewhere, delete any existing DKIM records for Hostinger at that DNS host first, then add the three CNAMEs above.
- Enter only
hostingermail-a._domainkeyin the host field, without trailing dots, spaces or capital letters, at hosts that append your domain. - Return to Domain settings to check the status. Hostinger says new records can take a few hours, and up to 24 hours, to work.
DMARC alignment
All three selectors are published under your own domain's _domainkey name, so once they resolve, a receiver verifies Hostinger's signature against a key tied to your domain, which is what DMARC needs for an aligned DKIM pass. Hostinger's records cover mail sent through Hostinger Email only: for a newsletter tool or website plugin that sends through another service, Hostinger says to use that sender's own DKIM record instead of the defaults.
Key length and rotation
With three CNAMEs pointing into dkim.mail.hostinger.com, the keys themselves live in Hostinger's zone, so Hostinger can replace a key there without asking you to touch your DNS. Its help articles don't state a key length or a rotation schedule, and they don't say which of the three selectors signs at a given time, so publish all of them.
Common mistakes
- Entering the records as TXT. Hostinger says its DKIM records must be CNAMEs; a TXT record or a typo can break signing.
- A doubled domain. Some DNS providers append your domain to the host, turning
hostingermail-a._domainkeyintohostingermail-a._domainkey.example.com.example.com. - Leftover DKIM records. Hostinger asks you to delete existing DKIM records before adding the defaults at an outside DNS host.
- Adding records at the wrong provider. They only count where the domain's nameservers point; otherwise hPanel keeps showing the domain as not connected.
Check your Hostinger DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
Do I need all three Hostinger DKIM CNAME records?
Yes. Hostinger's default DKIM setup lists hostingermail-a, hostingermail-b and hostingermail-c together, and its articles don't say any of them is optional. Add all three so whichever selector signs your mail resolves.
How do I set up Hostinger DKIM for a subdomain?
Add the subdomain to the host part of each record. For shop.example.com, Hostinger's example uses hostingermail-a._domainkey.shop, hostingermail-b._domainkey.shop and hostingermail-c._domainkey.shop, with the same targets as for the main domain.
Can I use Hostinger's DKIM records for mail sent by a third-party service?
No. They sign only mail sent through Hostinger Email. Hostinger says to use a custom DKIM record from the third-party sender instead, so that sender's mail is signed with a key it controls.
Sources
- Hostinger Help: What are the DKIM records for Hostinger Email?
- Hostinger Help: Set up a domain for Hostinger Mail manually
- Hostinger Help: Set up domain for Hostinger Mail
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Hostinger's documentation on November 3, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Hostinger
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated