DMARC uses retired tags
Your record holds at least one of three tags that used to shape DMARC: pct, rf or ri. The result names the ones it found. RFC 9989, the DMARC standard since May 2026, removed these tags, and receivers that follow it ignore them. On their own they don't break the record, but any other finding on the same result still needs fixing.
DMARC uses retired tags
These tags no longer do anything: receivers that follow the current standard ignore them.
The current DMARC standard (RFC 9989) removed pct; receivers that follow it ignore them. Use t=y for testing mode.
| Tag | What it did under RFC 7489 | Under RFC 9989 |
|---|---|---|
pct | Applied the policy to a share of failing mail, such as pct=25 | Ignored. t=y marks the policy as a test |
rf | Chose the format of failure reports | Ignored. There is one format |
ri | Asked for a report interval | Ignored. Receivers choose; most send one report a day |
Details → on your result shows the record, or run dig +short TXT _dmarc.example.com with your domain in place of example.com. rf and ri are safe to delete today.
pct needs care
For a while, receivers will differ. One that still follows RFC 7489 applies your policy to the share pct names. One that follows RFC 9989 ignores pct and applies the policy to all failing mail. So p=reject; pct=25 already rejects every failing message at some receivers. The standard's own reason for dropping it (appendix A.6): pct "was usually not accurately applied, unless the value specified was either 0 or 100".
t=y replaces it for receivers that follow RFC 9989. With p=reject; t=y they quarantine failing mail instead of refusing it. Older receivers don't know t and apply p as written.
What to do depends on what the reports say:
- Every service you send through passes DMARC. Remove
pctand keep your policy. Older receivers move from a share to all failing mail. That includes mail through mailing lists and forwarding, which can fail DMARC without being forged, so check those reports before you removepct. Ansp=ornp=set toquarantineorrejectchanges the same way for subdomains, so check their mail too. - Some of your own mail still fails. Step down to a policy that is safe at both kinds of receiver: change
p=reject; pct=25top=quarantine; t=y, or top=noneif failing mail must still reach the inbox. Lowersp=andnp=the same way if the record has them. Fix the failing services, then removet=yor raise the policy. - You don't know. Change the policy to
p=none, andsp=andnp=too if the record has them, removepct, and read reports until you do. Connect DMARC reports sends them to MailGlo.
Then run the check again.
Last updated .