How to add a DMARC record on Hostinger

📅 Last updated: June 2026

⏱ 3 min read

✅ All plans

Adding a Domain-based Message Authentication, Reporting, and Conformance (DMARC) rule entry is a mandatory protocol requirement to finalize your custom domain authentication loop. By deploying a DMARC policy framework, you authorize receiving mailbox servers to verify your inbound campaign headers, dramatically stabilizing your long-term deliverability metrics.

Step-by-Step Hostinger hPanel Configuration Loop

To establish a clean p=none; monitoring policy, copy the security parameters displayed within your SystemeScale DNS records modal popup window and deploy them inside Hostinger using this progression sequence:

Navigate to Hostinger DNS Management

Log directly into your central Hostinger account interface. Browse into your verified domain asset portfolio, select the target domain you are authenticating, click on the DNS / Nameservers menu option, and open the DNS records management area.

Select the TXT Record Type

Locate the primary Manage DNS records addition block form. Expand the type dropdown selector menu and choose strictly TXT.

Populate the Hostname and Value Parameters

Fill out the open text fields carefully using this structured formatting rule:

Name field: Enter exactly _dmarc
TTL field: Leave at the default auto/system value.
TXT value field: Paste your custom DMARC string framework incorporating your active postmaster reporting address tag (e.g., v=DMARC1; p=none; rua=mailto:example@example.com).

Commit the Record Node

Verify the character spacing across your text strings, then click on the Add record action button to validate and launch the rule on the nameserver network.

🛑

Strict Single-Record Architecture Rule

Your custom domain's active DNS zone **must contain only one single DMARC record row entry**. If you spot any pre-existing or outdated _dmarc entries within your Hostinger records log grid table, permanently delete the legacy row blocks and preserve only the new SystemeScale rule node to prevent validation failures.

Operational Insights: Data Reports & Monitoring Loops

Once your DMARC verification asset is visible to the public web network layer, corporate email provider servers will assemble and transmit automated telemetry logs summarizing your domain's outgoing activities. These XML diagnostic reports route straight to the inbox specified within your rua=mailto: variable definition.

💡

Dedicated Reporting Recommendations

Because ISPs submit reporting telemetry matrices on a daily cycle, these raw files can clutter your primary personal inbox. We strongly recommend setting up a dedicated management address (such as dmarc-reports@yourdomain.com) exclusively to capture these tracking files without filling up your primary commercial mail storage limits.

Please note that raw DMARC XML reports utilize a highly technical code format designed for specialized log analyzers. To learn how to parse and evaluate these files, review our guide: How to interpret raw DMARC report data.

Network Propagation Tracking

To verify that your newly deployed Hostinger text records are fully functional across international tracking channels, run a public scan using MXToolbox DMARC Analyzer. Input your root domain into the query search field; a green success confirmation layout indicates that your authentication loop is active and successfully established.

Was this article helpful?

📄Why aren't my emails being sent?→ 📄How to confirm your email sender address→ 📄How to improve the deliverability of my emails (advanced tips)→ 📄Why do my emails arrive in the Gmail 'promotions' tab?→ 📄How to authenticate your domain name on Hostinger→