Provider guides
DMARC setup for Hostinger email
Identify the active Hostinger mail product, then configure SPF, DKIM and DMARC for the real sending path.
What Hostinger handles
Hostinger accounts may use different email products and DNS arrangements. Confirm the active mail service shown for the domain before applying record values.
A domain can use Hostinger mail while authoritative DNS is hosted elsewhere. The nameservers, not the web-hosting dashboard, determine where records must be published.
Configure SPF without creating a second record
Use the SPF value displayed in the active Hostinger email setup. Merge it with other authorized senders rather than publishing a second SPF record.
A domain must publish one SPF record. If another service already sends mail, merge its authorization into the existing record and evaluate the complete DNS lookup count.
Illustrative structure
v=spf1 include:provider.example include:approved-sender.example -allEnable and confirm DKIM
Publish the DKIM selector and value supplied for the specific domain and mail product, then confirm the service reports it as active.
Inspect a real outbound message because a visible DNS record does not prove the sending service is applying the corresponding signature.
DKIM is selector-specific. Confirm the selector shown by the provider resolves in public DNS and then send a message to a mailbox where you can inspect Authentication-Results.
Add DMARC on top
DMARC checks whether SPF or DKIM passes and aligns with the domain visible in the From address. Start with reporting while legitimate services are still being identified.
Move to quarantine and reject only after reports show that real senders authenticate correctly. Use pct for a controlled rollout, and review the sp policy when subdomains send mail.
Monitoring example
v=DMARC1; p=none; rua=mailto:[email protected]Enforcement target
v=DMARC1; p=reject; pct=100Account for third-party senders
Website forms and external platforms may not use the Hostinger mailbox path. Authenticate each independently or route it through a documented supported relay.
- List marketing, invoicing, support, recruitment and transactional systems.
- Confirm whether each service supports aligned DKIM, aligned SPF, or both.
- Use a dedicated subdomain where separation improves control.
- Do not authorize an entire provider when a narrower account-specific option exists.
Typical mistakes
Provider authentication covers that provider, not every system using the same visible From domain.
- Using instructions for a different Hostinger email product
- Editing a non-authoritative DNS zone
- Adding a separate SPF record for each platform
- Moving to reject before website and application senders are identified
Verify the result and keep it healthy
Check DNS from outside the provider dashboard, send representative messages and inspect both SPF and DKIM alignment. Then monitor aggregate DMARC reports as real traffic arrives.
Orillon groups sender evidence into recognizable services, explains failures and guides policy forward without treating a DNS record as proof that mail is protected.
- Confirm the active mail product and MX targets
- Resolve the supplied SPF and DKIM values publicly
- Test mailbox and website-generated messages
- Review aggregate reports before enforcement