Publish a DMARC policy to protect your Microsoft 365 domain from spoofing and phishing by instructing receivers how to handle unauthenticated email.
TXT
_dmarc
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
Start with p=none to monitor before enforcing. Ensure SPF and DKIM pass first.
DMARC requires at least one of SPF or DKIM to pass and align. Verify both are set up for your Microsoft 365 domain.
Choose a mailbox or DMARC reporting service to receive aggregate (rua) and forensic (ruf) reports.
Add a TXT record in your DNS with host _dmarc and your policy value.
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1Monitor aggregate reports for 2-4 weeks. Ensure all legitimate senders (marketing platforms, CRM, etc.) pass SPF or DKIM with domain alignment.
Gradually tighten the policy: p=quarantine with pct=25, then pct=50, pct=100, and finally p=reject.
v=DMARC1; p=reject; rua=mailto:[email protected]; fo=1(no DMARC record)v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1After adding your DNS records, use our free DMARC checker to verify everything is configured correctly. DNS changes typically propagate within minutes, but can take up to 48 hours.
Yes. SPF and DKIM authenticate email, but DMARC tells receiving servers what to do when authentication fails. Without DMARC, receivers make their own decisions about unauthenticated mail.
Yes. Microsoft 365 (Exchange Online Protection) sends DMARC aggregate reports to domains that have a rua tag in their DMARC record.
The recommended final policy is p=reject, which instructs receivers to reject any email that fails DMARC authentication. Only move to reject after confirming all legitimate senders pass.