[ Sending-service guides ]

Authenticate email sent through Hostinger Email: configuration and verification

Configure the Hostinger Email record family, distinguish default CNAMEs from custom DKIM, and verify the messages the account actually sends.

By the EmailAuth research team · 4 min read

[ Key points ]

  • Confirm Hostinger Mail rather than Titan or another account product.
  • Distinguish default CNAME records from custom DKIM TXT.
  • Resolve selector conflicts without deleting unrelated signers.
On this page
  1. Key points
  2. Takeaway
  3. By role
  4. Frequently asked questions
  5. Sources
  6. Glossary
  7. Related guides

[ Takeaway ]

Resolve selector conflicts without deleting unrelated signers.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Compare active selectors

Default CNAMEs and custom TXT keys follow different workflows.

Next steps

  1. Record the selected mode.
  2. Preserve unrelated keys.
  3. Inspect a received signature.

CISO / SecOps

Protect shared domain trust

An authentication example must not overwrite wider policy.

Next steps

  1. Review SPF dependencies.
  2. Approve report recipients.
  3. Require evidence before enforcement.

Founder / Non-technical

Keep the right product in scope

A shared account does not make every email product interchangeable.

Next steps

  1. Confirm the service with the mailbox owner.
  2. Schedule any signing change.
  3. Keep staff mail available.

[ FAQs ]

Frequently asked questions

Are these the Titan Email records?

No. Confirm that the domain uses Hostinger Email or Hostinger Mail before using this record family.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Why are three default DKIM CNAMEs listed?

That is Hostinger’s documented default configuration. Publish the full set shown for the domain rather than only the first record.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Where are the domain status checks?

In Emails, open Mailboxes for the domain and then Domain settings.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Is custom DKIM another default CNAME?

No. The documented custom workflow generates a TXT record and requires verification.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Should all DKIM records be deleted if Generate is disabled?

No. Resolve the specific Hostinger conflict with support; unrelated services’ selectors must be preserved.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

What happens when custom DKIM is removed?

Hostinger documents a return to default DKIM. Verify the resulting signature in a controlled message.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Can I paste the sample DMARC reporting address unchanged?

No. Use an authorized, functioning reporting destination and retain an existing approved policy unless its owner approves a change.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

Why inspect the selector in the received message?

It identifies the key actually used, which may differ from the default records you expected to test.

Set up a domain for Hostinger Mail manually How to add a custom DKIM record for Hostinger Email RFC 7208 SPF RFC 6376 DKIM RFC 9989 DMARC

[ Sources ]

Sources

  1. Set up a domain for Hostinger Mail manually

    Sections Domain settings144–176; SPF189–194; three CNAME195–202; DMARC203–208

  2. How to add a custom DKIM record for Hostinger Email

    Sections Generate137–144; verification147–149; fallback158 and coexistence160

  3. RFC 7208 SPF

    Sections §3.2; 3.3; 4.6.4

  4. RFC 6376 DKIM

    Sections §3.5; 3.6.2; 6.1

  5. RFC 9989 DMARC

    Sections §4.4; 4.7; 4.10; 5

[ Glossary ]

Glossary

SPF
DNS authorization for an SMTP identity, subject to a limit of ten evaluated DNS-causing terms including nested evaluations.
DKIM selector
The label identifying the DNS public key used to verify a message signature.
DMARC alignment
The relationship between the visible From domain and a passing SPF or DKIM authentication domain.
Authoritative DNS
The delegated service publishing the domain’s live DNS answers.
Return-Path
The recorded reverse-path used for delivery failure handling, distinct from the visible From address.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base