Topic · Authentication
DMARC p=none policy
A DMARC p=none record asks receivers to report authentication outcomes without requesting quarantine or rejection for DMARC failures.
How it works
Receiving systems evaluate alignment and can send aggregate reports while generally leaving disposition to their own local policies.
What can go wrong
Monitoring-only status does not prevent unauthenticated mail from being delivered or spoofing from being attempted.
What to check or do
Use the reporting period to identify senders and prepare an evidence-based path toward enforcement.
How to investigate DMARC p=none policy
- Signal to investigate
- A monitoring-only domain receives reports but continues to be impersonated.
- Evidence to collect
- Query the applicable DMARC TXT record, inspect p=none and sample aggregate reports by source and alignment.
- Common wrong conclusion
- p=none gathers telemetry; it does not request quarantine or rejection of failed messages.
How to interpret the evidence
Monitoring is useful for source discovery, but a report stream must be interpreted and false positives resolved before enforcement. Attackers can continue sending mail that claims the domain during this period.
What to change and how to verify it
Separate authorized from unauthorized sending sources, fix legitimate alignment, and develop a measured enforcement plan with failure monitoring.
Put this into practice
Run a focused check, then explore protection if your domain needs it.