Add a DMARC record in Hostinger

Updated 2026-09-30 · Setup Guides

If your domain's nameservers end in dns-parking.com — ns1.dns-parking.com, cosmos.dns-parking.com and similar — Hostinger's own help pages say that typically means Hostinger manages the domain's DNS zone. You publish the record in Hostinger's DNS editor. One thing to do before anything else: look for an existing DMARC record. Hostinger's email setup can add one for you, and a domain may have only one.

The record you're publishing

The Value is your DMARC policy. If you're setting up monitoring with DMARCmetric, Add your first domain generates the full value for you, including your workspace's unique rua= reporting address — copy it from the wizard with the copy button rather than retyping it. p=none is the right starting policy: it monitors everything and blocks nothing.

The steps below add a new record, for a domain with no DMARC record yet. If _dmarc already has one, don't add another — edit the one you have instead.

Step by step

1. Sign in to Hostinger. In the left sidebar, choose Domains, then DNS, and select your domain. (Hostinger's help pages also reach the same records as Domains → your domain → DNS / Nameservers, and, for a site on a hosting plan, Websites → your site → Advanced → DNS Zone Editor.)
2. Look through the records already listed for a TXT record named _dmarc. If there is one, stop here and edit it instead.
3. In the form for a new record, set Type to TXT.
4. In Name, type _dmarc — only the part in front of your domain. Hostinger's own instructions do the same (shop for shop.domain.tld); it adds your domain for you.
5. In the value field, paste your v=DMARC1; … value exactly as generated. Hostinger's pages label that field TXT value, Content or Points to, depending on the screen.
6. Leave TTL on the default and click Add Record.

Hostinger says DNS changes can take up to 24 hours to take effect.

If you already have a DMARC record

A domain can have only one DMARC record, so don't add a new record — change the one that's there. Never add a second _dmarc record next to the old one: with two, email providers ignore both.

1. In the DNS records list, find the existing TXT record whose Name is _dmarc.
2. Edit that record.
3. What you change depends on what DMARCmetric shows you — check which of these two it is before you touch anything:
   • If DMARCmetric shows only an address (mailto:rua+…, shown when it couldn't read your DNS at that moment), don't replace anything. Add that address to your existing rua= tag, separated by a comma. If the record has no rua= tag, add one: rua= followed by the address, separated from the tag before it by a semicolon. Leave your policy and every other tag as they are.
   • If DMARCmetric shows a full record (starting with v=DMARC1), replace the record's whole Value with it. That value is built from your existing record: your policy and tags are kept, and it includes your DMARCmetric reporting address.
4. Save the record.

If there are several. If the list shows more than one TXT record at _dmarc that starts with v=DMARC1, delete the extras and keep one, then change the one you keep exactly as in step 3: if DMARCmetric shows a full record, that record becomes its Value; if it shows only an address, add the address to its rua= tag. Until only one is left, receivers treat the domain as having no DMARC policy at all.

Verify it's live

From a terminal:

dig TXT _dmarc.example.com +short

You should see your v=DMARC1; … value echoed back in quotes. No terminal handy? Run your domain through the free DMARC checker — it fetches the live record and validates the syntax, which dig won't do. And if you added the record as part of DMARCmetric onboarding, press Verify DNS in the wizard; Verify your domain explains each result it can give you.

Common mistakes

• Adding a second record next to Hostinger's. If Hostinger's email setup already published a _dmarc record, a new one beside it leaves you with two — which receivers treat as no DMARC policy at all. Edit the existing one.
• Editing while the domain uses other nameservers. Records in Hostinger's DNS editor only take effect while the domain uses Hostinger's nameservers. If the nameservers point somewhere else, publish the record there.
• Resetting the DNS zone. Hostinger's reset puts every record back to its defaults, which removes a _dmarc record you added. The same goes for importing a zone file in Replace mode: all existing records are removed first.
• Not checking what was published. Hostinger's pages don't say whether its editor adds quote marks around a TXT value. After saving, run the checker: if it shows a stray " inside your record, edit the record and remove it.
• Editing the value by hand. A missing semicolon between tags, mailto; instead of mailto:, or a mangled reporting address all invalidate the record or send your reports nowhere. Copy-paste the whole value, then confirm with the checker.

If some of your domains live at other providers, the same record works everywhere — the Cloudflare and GoDaddy walkthroughs cover those panels.