How to move DMARC from p=none to quarantine and reject

Move the DMARC policy from none to quarantine and then reject in stages, reading the reports before each step.

Last reviewed

Why it matters

A policy of none only asks for reports, so mail forging the domain is still delivered. Enforcement protects the domain only once every legitimate sender passes SPF or DKIM in line with the From domain, and getting there is the actual work.

How to fix it

Change only the p= tag of the existing record and keep everything else in it (rua, sp, adkim, aspf). The record now reads:

v=DMARC1; p=none

If it has sp=none, subdomains stay unprotected until you change that too.

Replace the highlighted values: v=DMARC1; p=none with your current DMARC record, dmarc-reports@example.com with a mailbox that receives DMARC reports, example.com with your domain.

Any DNS host

  1. Stay at none until every legitimate sender passes. In the aggregate reports, list every source; for each, confirm it is a real sender for the domain and that SPF or DKIM passes aligned. The usual gaps are invisible from the main mailbox: website contact forms, CRMs, invoicing and accounting tools, helpdesks, newsletter platforms, booking systems, a scanner that emails. Fix each by turning on DKIM signing with this domain in that service, or by giving it a custom return-path on this domain. Google's minimum is a week at none; for a client domain we suggest two to four weeks, so monthly senders such as invoice runs appear.

  2. Quarantine. Publish:

v=DMARC1; p=quarantine; pct=10; rua=mailto:dmarc-reports@example.com

Google suggests starting at 10% (1% for a large organisation); Microsoft suggests 10, 25, 50, 75, then 100. But the current DMARC standard, RFC 9989 (May 2026), removed pct, and receivers that follow it ignore it and quarantine every failing message at once. Treat pct as a hint, and only take this step when the reports show no legitimate sender failing. We suggest one to two weeks at each step and two weeks at full quarantine:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com
  1. Reject, after two to four weeks at full quarantine with no legitimate failures:
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com

With several sending subdomains, Microsoft suggests enforcing the quiet ones first and the parent domain last.

Sources: RFC 9989 (Appendix A.6 on pct), RFC 7489, Google's rollout, Microsoft: configure DMARC.

Cloudflare

Edit the record the same way under DNS > Records. If Email > DMARC Management is enabled, use its per-source view to confirm every sender passes SPF, DKIM and DMARC before each stage.

Source: DMARC Management.

Google Workspace

Google's rollout: none for a week, reviewing reports daily; quarantine with a small pct (its example is pct=5); raise pct to 100; then reject if you choose. Workspace mail aligns through DKIM only once Workspace DKIM is turned on.

Sources: recommended rollout, set up DMARC.

Microsoft 365

Microsoft's rollout is none, then quarantine (optionally stepping pct), then reject. Two things specific to it: outbound Microsoft 365 mail that fails DMARC under quarantine or reject goes through its high-risk delivery pool, and Microsoft 365 does not send forensic (ruf) reports. Enable DKIM for the custom domain first.

Source: Microsoft: configure DMARC.

Check that it worked

dig TXT _dmarc.example.com +short

Wait out the old record's TTL (the second column of the same command without +short), then run the Owl Keeper Email authentication check again. After each stage, watch a few days of reports for quarantine or reject on a source you recognise.

Test it now with the free DMARC checker. No account needed.

What can go wrong

  • Moving too fast drops real mail. Forms, CRMs, invoicing tools and newsletters that send as the domain without signing as it go to spam, or bounce under reject. Clients often notice weeks later, when an invoice run never arrived.
  • pct is not a safety net: receivers following RFC 9989 ignore it.
  • Forwarding and mailing lists break SPF, and some break DKIM, so some legitimately forwarded mail will fail. DKIM survives forwarding better.
  • Reports are not complete. Not every receiver sends them (Microsoft estimates they cover 70 to 90% of volume), and rare senders may not appear in a short window.