DMARC pct= is less than 100
Your DMARC record contains a `pct=` value under 100, meaning your policy only applies to a fraction of mail.
Impact — Low impact
A pct<100 is a legitimate rollout tool (e.g., apply reject to 10% of mail at first), but if you left it in place long-term, you're giving spoofers a loophole for the remaining percentage.
What causes it
- You deployed DMARC with pct=10 as a soft rollout and never ramped up.
- You wanted to limit false-positive impact during a sender migration and left it low.
- A DMARC generator defaulted to pct<100 and you accepted the default.
How to fix it
Step 1: Check your DMARC reports
Review the last 2-4 weeks of DMARC aggregate reports. If no legitimate senders are failing alignment, you're safe to ramp pct up.
Step 2: Ramp gradually
Common schedule: pct=25 for a week, pct=50 for a week, pct=100 for a week. At each step, verify no deliverability regressions via reports.
Step 3: Remove the pct= tag
When pct=100 is working, you can either leave it or remove the tag entirely (DMARC defaults to pct=100 when absent). Removing it is slightly cleaner.
Fixed it? Run a fresh test to confirm.
Test my inbox →