Glossary
DMARC Policy — none, quarantine, reject Explained
DMARC p=none is monitoring mode — it means your DMARC record exists but doesn't block or quarantine anything. Emails that fail DMARC are still delivered. You receive daily aggregate reports showing what's failing, but nothing is enforced until you change to p=quarantine or p=reject.
| Policy | What it does | Emails blocked? | When to use |
|---|---|---|---|
p=none |
Monitor only — collect reports | No — all email delivered | Starting out, first 2-4 weeks |
p=quarantine |
Send failures to spam folder | Partial — spam folder | After reports show clean senders |
p=reject |
Block failures entirely | Yes — hard reject | Full enforcement, all senders aligned |
The Three Policy Levels
- p=none — monitoring mode. Failures are reported but all email is delivered. Safe starting point.
- p=quarantine — failures go to spam folder. Partial protection.
- p=reject — failures are blocked entirely. Full protection. Use only after confirming all legitimate senders are aligned.
Recommended Rollout
- Week 1-4: p=none + rua= reporting
- Week 4-8: p=quarantine (review reports first)
- Week 8+: p=reject (once all senders clean)
Check your live DMARC TXT
Open DNS Preflight →FAQ
What is DMARC policy?
The p= tag in your DMARC record that tells receivers what to do with emails failing DMARC — monitor, quarantine, or reject.
What is the safest DMARC policy to start with?
p=none — it collects reports without affecting delivery. Use it to identify all your legitimate senders before enforcing.
When should I move to p=reject?
After at least 2-4 weeks of DMARC aggregate reports showing all legitimate senders are aligned with no failures.