StrategyCore
Back to Resources
07/cybersecurity 2 min read

Reviewing a move from DMARC monitoring to enforcement

Establish sender ownership, test indirect mail and plan recovery before tightening policy.

Moving beyond p=none is a change to a business-critical service. A useful migration plan states which domains are in scope, which legitimate senders have been tested and how the team will respond if delivery changes. It should not promise a risk-free switch or a fixed completion time.

An enforcement change plan

SC-TL-01 · REV A · 2026.07

01Inventory

owners and domains

02Test

alignment and forwarding

03Change

approved policy

04Monitor

delivery and recovery

No fixed timetable or delivery guarantee is implied.

Inventory, alignment testing, a controlled policy change and ongoing monitoring.
01

Build a sender inventory

Use aggregate reports alongside DNS records, application inventories and business-owner interviews. Reports describe observed traffic, not a complete list of every system that may send mail. Include seasonal campaigns, low-volume applications, subsidiaries and service accounts. Record who can approve changes for each sender and who owns the domain’s DNS.

02

Correct authentication and alignment

Test whether each legitimate source has an aligned SPF or DKIM pass. Check custom sending domains, DKIM key management and SPF evaluation limits. Include forwarded messages and mailing lists: indirect flows can change authentication results even when the original sender is legitimate. Retain test messages and receiver results so failures can be reproduced.

03

Use the current standard and check interoperability

RFC 9989 replaced RFC 7489 in May 2026 and removed pct-based percentage rollout. It introduces a testing tag, but receiver implementations and provider requirements must be checked before relying on it. Use controlled domains or subdomains, representative testing and observed reports to plan changes. Do not describe a percentage setting as a guaranteed safety mechanism.

04

Operate enforcement as an ongoing control

Agree acceptance criteria, a change window, monitoring and an authorised rollback procedure. Choose quarantine or reject with the organisation’s indirect mail flows and risk tolerance in mind; the receiver retains disposition control. Continue checking new services and configuration changes after rollout. Completion means an owned operating process, not just a stricter DNS record.

Sources and further reading

// Key Takeaways

What to remember

  • Inventory and test legitimate senders before changing policy.
  • The older pct rollout advice is not part of RFC 9989.
  • Keep monitoring, change ownership and recovery procedures in place.

// FAQ

Frequently asked questions

Q1

Can staged enforcement guarantee no legitimate mail is affected?

No. Sender inventories and tests reduce risk, but forwarding, mailing lists and unobserved services can still cause failures. Agree monitoring and recovery criteria before the change.

Q2

Should a new migration use pct=25?

RFC 9989 removed the pct tag. Check current receiver support and use controlled testing and observed results instead of assuming percentage-based enforcement is reliable.

Last updated:

Support Japanese prospects moving to DMARC enforcement.

StrategyCore’s pre-sales engineers work with your team and the prospect’s email administrators to identify legitimate senders, test authentication and plan DMARC policy changes. We agree who handles DNS changes, delivery checks, rollback and post-sales technical support before licensing.