DMARC policy tells receivers what your domain asks them to do when a message fails DMARC. The right policy depends on whether all legitimate senders are authenticated and aligned.
Scan the domain first, then use this guide to interpret whether p=none, quarantine, or reject is the next sensible stage.
Check the public sender-auth records mailbox providers expect.
Keep one URL with evidence, owner steps, and decisions.
Add human review, provider context, and verification steps.
Review DMARC policy strength before a high-volume send.
Overall sender readiness
Needs attention
Sample output: one warning and one fail mean this domain is not campaign-ready yet.
The scan becomes a focused work surface: evidence, owner action, verification, and the paid context a public lookup cannot infer.
p=none is monitoring mode. It helps a team collect DMARC aggregate reports and understand which services send mail for the domain. It does not ask receivers to quarantine or reject failing messages.
Use this stage to find every legitimate sender, confirm SPF or DKIM authentication, and check alignment with the visible From domain before enforcement.
p=quarantine asks receivers to treat failing mail with suspicion, often by placing it in spam or a similar review area. Receivers can still apply their own local rules, so this is a request, not a guarantee.
Teams often move to quarantine after report review shows that legitimate senders are aligned and that failures are mostly unauthorized or obsolete sources.
p=reject asks receivers to reject failing mail. This is the strongest common DMARC policy, but it should be used carefully because misconfigured legitimate senders may be blocked or rejected by receivers that honor the policy.
Not usually. Review legitimate senders first. Moving too quickly can disrupt tools that send real customer, billing, support, or marketing mail.
No. DMARC enforcement helps authenticate domain use. Mailbox providers still evaluate reputation, complaints, content, engagement, volume, and other signals.
Yes. DMARC supports the sp tag for subdomain policy. Review subdomain mail separately before enforcing a broad parent-domain policy.
The readiness audit path saves your scan and organizes the next actions. Access starts through the beta pricing and audit request path.