DMARC p=none
DMARC p=none asks receivers to send reports without changing how failing messages are delivered. It is the correct starting policy—not a finished security control.
What this policy does
Receivers authenticate mail and report results, but failing messages are still delivered according to normal spam filtering—not DMARC enforcement.
v=DMARC1; p=none; rua=mailto:[email protected]; fo=1When to use it
Use p=none while you inventory senders, fix alignment, and confirm rua delivery. Do not leave critical brands on p=none indefinitely if spoofing risk is high.
Troubleshooting before you change policy
Check aggregate reports for unknown sources, SPF PermError, missing DKIM selectors, and From domains that do not match signing domains.
- Run a DMARC checker on the apex and major sending subdomains
- Validate SPF lookup count under 10
- Confirm DKIM for Microsoft 365 / Google / ESPs
- Fix or retire shadow IT senders
Microsoft 365 & Google Workspace
Policy lives in your public DNS, not inside the M365 or Google admin center. Ensure Exchange Online and Google Workspace mail are aligned before quarantine/reject.
How QuickDMARC helps
QuickDMARC monitors pass/fail trends and helps you change Managed DMARC policy when ready—without guessing from incomplete mailbox samples.
Frequently asked questions
Does DMARC p=none stop spoofing by itself?
No. p=none is monitoring only. Spoofed mail can still be delivered.
Do I still need rua?
Yes. Keep aggregate reporting enabled through every policy stage.
Related policies?
See p=none, quarantine, and reject guides plus the overall DMARC policy page.