Understanding DMARC
Moving to quarantine and reject
How to tighten your policy step by step without blocking your own mail.
p=none gives you visibility, but it does not protect anyone. Protection starts at p=quarantine and is complete at p=reject. The aim is to get there without blocking your own mail.
When you are ready
- Every legitimate sending source passes DMARC, and you know what each one is.
- Compliance for your own services is consistently near 100%. Remaining failures are spoofing or forwarding, not your systems.
- You have watched at least a few weeks of reports, covering monthly and quarterly mail.
A typical path
p=quarantine; pct=10: a tenth of failing mail goes to spam. Watch reports and complaints for a week.p=quarantine; pct=50, thenpct=100.p=reject; pct=10, rising top=rejectwith nopcttag.
Small organisations with few, well-understood senders can move faster. The reports tell you when it is safe.
Subdomains
By default subdomains inherit your policy. If you send from subdomains (mail.example.com), check them too. You can set a separate subdomain policy with sp=, for example to reject on subdomains that never send mail.
If something breaks
Reports show exactly which source failed. Fix that sender, or step back to the previous level while you do. With hosted DMARC this is a setting, not a DNS change.
Next: Life after p=reject.
See it on your own domain.
Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.
Start free