The "DMARC policy not enabled" warning means your domain has no DMARC record, or has one set to p=none, which only monitors and does not ask receiving servers to act on fake emails. To clear it, check that SPF and DKIM pass, then edit the _dmarc TXT record in hPanel and change p=none to p=quarantine, and later to p=reject.
It is a warning, not an outage. Your emails still go out. But until the policy is enforced, anyone can send messages that claim to come from your domain, and mailbox providers have no instruction to filter them. Here is how to fix it without blocking your own mail.
Where the warning comes from
The wording comes from email checking tools such as MxToolbox, which shows "DMARC Quarantine/Reject policy not enabled" when it finds a missing record or a p=none policy. Other scanners use similar phrasing.
Hostinger domains trigger it often for a simple reason: Hostinger's own help article suggests starting with v=DMARC1; p=none; rua=mailto:[email protected]. That is a sensible first step, because p=none lets you collect reports before enforcing anything. It just isn't meant to be the last step.
Is it urgent?
Not in the sense that something is broken today. The warning tells you one protection is switched off:
- With
p=none: receiving servers check your emails but take no action on failures. A spoofed message pretending to be from your domain is treated like any other message. - With
p=quarantine: messages that fail DMARC are sent to the spam folder. - With
p=reject: they are refused outright.
Gmail and Microsoft only require a DMARC record (even p=none) from senders above 5,000 messages a day. Moving to an enforced policy is therefore a choice, but it is the one that actually protects your name.
Step 1: check your current record
Open a terminal and run:
nslookup -type=TXT _dmarc.yourdomain.comYou should see exactly one line starting with v=DMARC1. Note the value of p=. If nothing comes back, you have no DMARC record yet: add one with p=none first (see Step 4) and come back in a week.
You can also run our free DMARC checker, which reads the record and explains each tag in plain English.
Step 2: make sure SPF and DKIM are in place
DMARC only passes when SPF or DKIM passes for your own domain. If you enforce DMARC before they are set up, you will send your own emails to spam.
If you use Hostinger Email
Open the Email Domain Settings page for your domain in hPanel. It lists four records (MX, SPF, DKIM and DMARC) with a status of connected, missing or incorrect, next to the values Hostinger expects. If your DNS is hosted at Hostinger, the page can apply the missing records for you. For reference, Hostinger's manual setup uses:
- SPF (TXT on
@):v=spf1 include:_spf.mail.hostinger.com ~all - DKIM (three CNAME records):
hostingermail-a._domainkey,hostingermail-b._domainkeyandhostingermail-c._domainkey, pointing to the matching names underdkim.mail.hostinger.com
If you send through another provider
If your mailboxes are on Google Workspace or Microsoft 365, use the SPF and DKIM values from that provider instead. Remember any other tool that sends as you: newsletter, invoicing, booking or e-commerce platform. Each one needs to pass SPF or sign with DKIM for your domain. Your domain must have only one SPF record, so merge their include: values into it. Check the result with our SPF checker.
Check your domain for free. AttackScout reads your DMARC, SPF and public DKIM records, flags anything that would make enforcement risky, and gives you the exact value to paste in hPanel. Run the free check
Step 3: read your reports for a week or more
With p=none and a rua address, mailbox providers send you daily XML reports. Look for any service sending as your domain that fails both SPF and DKIM. Fix those first. Google suggests at least a week of monitoring with daily review before moving on; a longer period is safer if you send rarely.
Step 4: change the policy in hPanel
- In hPanel, go to Domains and click your domain.
- Open DNS / Nameservers.
- Find the existing TXT record named
_dmarcand edit it. If there is none, click Add record, choose TXT and enter_dmarcas the name. Set the value to:
v=DMARC1; p=quarantine; rua=mailto:[email protected]- Leave the TTL at its default and click Save.
Edit the record you already have rather than adding a second one. Two DMARC records on the same name cancel each other out, and receivers then ignore DMARC entirely.
Hostinger says DNS changes can take up to 24 hours to apply everywhere. On the Email Domain Settings page, a policy stricter than Hostinger's default may no longer match the value it expects; we could not confirm how hPanel labels that case, so rely on a DNS lookup to confirm your change.
When to move to p=reject
After a few weeks at quarantine with clean reports, you can change p=quarantine to p=reject in the same record. This gives the strongest protection against spoofing, but a mistake here means lost emails, not just misfiled ones. Take your time.
If your DNS is not hosted at Hostinger
Records you add in hPanel only take effect when the domain uses Hostinger's nameservers. If your domain points to Cloudflare, your registrar or another DNS host, make the same change there. Our GoDaddy DMARC guide covers one common case.
Step 5: confirm the warning is gone
Run the nslookup command again, or re-run your checker. The record should now show p=quarantine or p=reject. Then send an email to a Gmail address, open it, choose Show original, and check that SPF, DKIM and DMARC all show PASS.
Frequently asked questions
Will changing to quarantine stop my emails being delivered?
Not if SPF or DKIM already pass for your domain. Messages that pass DMARC are unaffected. Only messages that fail are moved to spam, which is why you read the reports first.
Should I keep pct in my record?
Some guides suggest pct= to enforce the policy on part of your mail. The updated DMARC standard published in May 2026 (RFC 9989) removed that tag, so do not rely on it as your only safety net. Reading reports before each step is the real safeguard.
Do I need a separate DMARC record for subdomains?
No. Without an sp= tag, your main policy also applies to subdomains.
Check your domain for free. In under a minute and without an account, AttackScout shows whether your DMARC policy actually protects your domain, and what to fix next. Check my domain
Technical details
Exact configuration. A TXT record on the _dmarc name of your domain:
_dmarc.your-domain.com TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Why. DMARC (RFC 7489) tells the receiving server what to do with an email that claims to come from your domain but passes neither SPF nor DKIM with that same domain name (alignment). p=none observes without blocking; p=quarantine sends to spam; p=reject refuses. rua receives the aggregate reports that show who sends in your name: tighten the policy only after reading them.
To check it yourself. Exactly one line must start with v=DMARC1:
dig +short TXT _dmarc.your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7489
Sources
Accessed 12 November 2026.
- Hostinger, How to add a DMARC record for Hostinger Email: https://www.hostinger.com/support/8412851-how-to-add-a-dmarc-record-for-hostinger-email/
- Hostinger, Set up a domain for Hostinger Email manually: https://www.hostinger.com/support/8671319-set-up-a-domain-for-hostinger-email-manually/
- Hostinger, Email domain settings: https://docs.hostinger.com/emails/domain-settings
- Hostinger, DNS management: https://docs.hostinger.com/domains/dns
- Hostinger, How to manage TXT records: https://www.hostinger.com/support/1583664-how-to-manage-txt-records-at-hostinger/
- MxToolbox, DMARC Policy Not Enabled: https://mxtoolbox.com/problem/dmarc/dmarc-policy-not-enabled
- IETF, RFC 7489 (DMARC): https://www.rfc-editor.org/rfc/rfc7489.html
- IETF, RFC 9989 (DMARC, May 2026): https://www.rfc-editor.org/info/rfc9989
- Google Workspace, Recommended DMARC rollout: https://knowledge.workspace.google.com/admin/security/recommended-dmarc-rollout
- Google, Email sender guidelines: https://support.google.com/mail/answer/81126?hl=en
- Microsoft, Fix NDR error 550 5.7.515 in Outlook.com: https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com