Move DMARC from p=none to enforcement
Step your policy up to quarantine and then reject without losing legitimate mail.
2–4 weeks, mostly waiting
why this matters
At p=none, spoofed mail using your domain is still delivered. That fraud damages the sender reputation your own campaigns depend on.
Step by step
- 1
Clear your reports first
Every legitimate sender must show an aligned SPF or DKIM pass. Fix or remove the failures before you tighten anything, or you will block your own mail.
- 2
Quarantine a small share
The pct tag limits how much mail the policy applies to, so you can test safely.
v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc@example.com - 3
Ramp to 100% quarantine
Raise pct through 50 and 75 over a week or two, checking reports and your own inbox at each step.
- 4
Switch to reject
Once full quarantine is quiet, move to the final policy.
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
how to check it worked
- The record shows p=reject with no pct tag
- Reports show no aligned failures from your own senders
related guides
Publish an SPF record
Tell mailbox providers which servers are allowed to send email as your domain.
Merge multiple SPF records into one
Two SPF records is a permanent failure — combine them.
Set your SPF enforcement correctly
Replace +all or a missing all mechanism with -all.
Get SPF back under the 10-lookup limit
Flatten or consolidate includes so SPF stops returning permerror.