Guide
Moving DMARC from p=none to p=reject
A safe, step-by-step path to full DMARC enforcement without losing legitimate mail.
Updated
p=none is where every domain should start with DMARC, and where far too many stay.
It meets the minimum Gmail, Yahoo and Microsoft ask of bulk senders, but it protects nothing:
mail spoofing your domain is still delivered. Getting to p=reject takes a few weeks of
work, mostly finding every service that sends as you. Here’s the plan.
Step 1: Publish p=none with reports
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com The rua address receives aggregate reports: XML files, usually daily, from each mailbox
provider that got mail claiming to be from your domain. Each lists the sending IP addresses, how many
messages came from each, and whether SPF, DKIM and DMARC passed.
A busy domain gets many reports a day, and raw XML is hard to read. A DMARC reporting service (many have free tiers) turns them into a list of sources. If the address is on another domain, that domain must authorise it; the DMARC checker checks for that.
Step 2: Find every legitimate sender
Give it two to four weeks so monthly mail (invoices, statements, reminders) shows up. Then go through every source in the reports that fails DMARC and sort it:
- A service you use (newsletter, CRM, helpdesk, billing): set up DKIM signing with your domain in that service, and add it to SPF if it sends with your domain in the return path. Then watch for it to start passing.
- Forwarding (a university or old ISP forwarding to Gmail, say): SPF breaks here, but DKIM usually survives. If DKIM passes, these will be fine.
- Not yours: spoofing. This is what enforcement will stop.
Don’t move on while any real sender is still failing. A missed one, say the payroll system that sends payslips once a month, is the classic way enforcement causes trouble.
Step 3: Quarantine
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com Failing mail now goes to spam rather than being refused, so a sender you missed is recoverable.
Some people ramp up with pct= (for example pct=25, applying the policy
to a quarter of failing mail), though receivers apply it inconsistently and the next version of
the DMARC standard drops it. Watch the reports and your own team’s complaints for another two to
four weeks.
Step 4: Reject
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com Mail that fails DMARC is now refused. Keep the report address: new services get added, and the reports are how you spot one that wasn’t set up properly.
Subdomains
Without an sp= tag, subdomains get the same policy as the domain. That’s usually
what you want at the end. During rollout, you can hold subdomains back with sp=none, but don’t leave it there: attackers will simply spoof billing.example.com instead.
If something breaks
Drop back a step (reject to quarantine, or quarantine to none). The change takes effect as fast as the record’s TTL allows. Fix the sender, then move forward again. DMARC changes are fully reversible; nothing is lost by stepping back for a week.
New to the three records? Start with SPF, DKIM and DMARC explained.
Related tools
All toolsDMARC Record Checker
Read a domain’s DMARC policy in plain words and see what to change before tightening it.
SPF Record Checker
Validate an SPF record, follow every include and count DNS lookups against the limit of 10.
DKIM Record Checker
Find DKIM keys under common selectors, or check your own, with key size and problems.
More guides
- SPF, DKIM and DMARC explained What each record does, how they work together, and the order to set them up in.
- Gmail, Yahoo and Microsoft sender requirements What the big mailbox providers require of senders, and how to check you meet it.
- Fix “SPF permerror: too many DNS lookups” Why SPF stops at 10 lookups, how to count yours, and four ways to get under the limit.