Topic · Authentication
DMARC pct tag (legacy)
The DMARC pct tag was a historical policy sampling option in RFC 7489 and was removed by RFC 9989 in May 2026.
How it works
Under the older specification, pct attempted to apply requested handling to a percentage of failures; RFC 9989 instead defines a t testing tag with different semantics.
What can go wrong
Treating pct as a current DMARC control can produce misleading implementation advice and inconsistent handling across receivers.
What to check or do
Do not recommend pct for new records; consult RFC 9989 and use its t tag and staging guidance where appropriate.
How to investigate DMARC pct tag (legacy)
- Signal to investigate
- A historical record may still contain pct= even though this tag is obsolete in RFC 9989.
- Evidence to collect
- Check current DMARC record parsing against RFC 9989 and plan replacement with supported semantics if needed.
- Common wrong conclusion
- Do not present pct as a current standards-based way to apply arbitrary percentage-based enforcement.
How to interpret the evidence
RFC 9989 (May 2026) lists pct as historical and defines a different testing signal, t. Some mailbox-provider BIMI setup pages still mention pct=100 from older documentation. This mismatch is a documentation and implementation-compatibility consideration, not a reason to recommend percentage-based DMARC enforcement as a current standard.
What to change and how to verify it
For new records, use RFC 9989 syntax and stage deployment with authentication reports. When configuring BIMI, compare the latest provider requirements and actual receiver behavior; do not assume that older provider guidance about pct overrides the current DMARC specification.
Put this into practice
Run a focused check, then explore protection if your domain needs it.