pct is historic: how to phase in DMARC enforcement now
The pct tag is historic. The current DMARC standard, since May 2026, removed it because receivers rarely applied it accurately. Don't use it to phase in enforcement, and if an old record still has it, remove it. Gradual enforcement: Move from p=none to p=quarantine, then p=reject, checking your reports at each step. Roll out domain by domain, and, if you want a test period, use the testing flag t=y, which isn't a percentage. Reject remains a per-domain decision (When you are ready for p=reject).
What pct did
Under the older DMARC standard, pct took a value from 0 to 100, default 100: the percentage of mail the policy should apply to. With p=quarantine; pct=20, receivers were to quarantine no more than 20% of failing mail and handle the rest with their normal filtering. At reject, mail outside the sample was to be quarantined instead. Reports still covered all mail.
It was meant for slow rollout, and Google and Microsoft built their rollout advice around it.
Why the current standard dropped it
Operational experience showed that the pct tag was usually not accurately applied, unless the value specified was either 0 or 100 (the default), and the inaccuracies with other values varied widely from one implementation to another.
So pct=50 never reliably meant half. The value 0, though, picked up a useful side effect: some mailing lists and mailbox providers treated it as a signal to rewrite the From header, which helped domain owners measure how much of their mail went through intermediaries before they enforced. The current standard kept that behavior and gave it its own tag, t, with t=y and t=n analogous to pct=0 and pct=100. pct is no longer a current tag.
What t=y does
t=y is the current testing flag. It asks receivers not to apply your published policy and to use any special handling they have instead, such as From rewriting. You should then expect treatment one level below the policy:
| You publish | With t=y, expect |
|---|---|
p=quarantine |
handled as none |
p=reject |
handled as quarantine |
p=none |
no effect |
The tag doesn't change reporting. Aggregate reports in the current format show a testing field, and receivers can report policy_test_mode as the reason they didn't apply your policy. The default is t=n.
One honest caveat: Google, Microsoft, and Yahoo don't document whether they honor t=y. Treat it as a request that some receivers may ignore. Full tag reference: DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.
How to phase in enforcement now
Gradual enforcement: Move from p=none to p=quarantine, then p=reject, checking your reports at each step.
- Stage the policy.
p=nonewithrua, fix every legitimate source, thenp=quarantine, then decide on reject for each domain. Spend long enough at each stage to cover your sending cycle. The gates are in A safe rollout: p=none to quarantine to reject, When you are ready for p=quarantine, and When you are ready for p=reject. - Roll out by domain. Start with low-volume subdomains and save the parent domain for last. That gives you a smaller blast radius than any percentage did.
- Optionally, test with t=y. Publish the new policy with
t=y, watch reports, then removet=yto apply it. Don't leave it in place.
What to do with pct in an existing record
pct=100: it does nothing. Under the older standard, leavingpctout meant 100, so removing it doesn't change your policy.pctbelow 100: don't rely on it. Its effect varied by receiver. Decide whether the domain is ready for the full policy. If yes, removepct. If not, drop back to the stage you're actually ready for.- In old reports: older-format aggregate reports may show
<pct>and asampled_outoverride reason. Reports in the current format showtestinginstead. Check a report's date and format before reading anything into it (A field-by-field walk-through of a DMARC aggregate report).
Why provider docs still say pct
You'll still see it. Some provider rollout advice still suggests starting quarantine at a small percentage, with examples such as pct=5, and gradually increasing the percentage. Microsoft 365 still steps through pct=10, 25, 50, 75, 100, and its headers include values such as action=pct.quarantine. That advice follows the older standard. This article follows the current one.
pct, t=y, and BIMI
For BIMI, a pct value less than 100 percent is not accepted, and Google still requires that pct not be set below 100. Leaving it out meets both. There's no established rule for t=y and BIMI, so remove t=y before you rely on your policy for BIMI (BIMI requirements checklist).
Mistakes worth avoiding
- Leaving
pct=10in a record for months and assuming 10% is protected. - A
pctbelow 100 on a domain you want BIMI for. - Assuming
pct=0meant monitor-only. At quarantine, a receiver following the older standard applied its normal filtering to everything. For monitoring, usep=none. - Leaving
t=yin place after testing.
Free DMARC account
Ready to move from p=none to enforcement?
Check that your legitimate senders are aligned before you tighten your policy, and get help from our team if something blocks the move.
- See which senders aren't aligned yet
- Check results per sender before each policy step
- Talk to our team when a sender won't align
FAQ
Is the DMARC pct tag still valid?
The current standard removed it, and the tag is historic. Some older receivers may still read it. Don't add it, and remove it from existing records.
What replaced pct?
The t tag, for the pct=0 testing case. There's no percentage replacement.
Why does Google still tell me to use pct?
Gmail's published rollout advice still uses pct. Treat that as outdated guidance for a tag the current standard has dropped.
Can I use pct=100 with BIMI?
It's accepted, but it's redundant. Leaving pct out has the same effect.