Calculator Inputs
Paste the DMARC record, enter observed message counts, and review how your policy settings translate into measurable enforcement strength.
Example Data Table
| Domain | Policy Snapshot | Alignment Rate | Coverage | Estimated Posture |
|---|---|---|---|---|
| alpha-mail.com | p=reject; sp=reject; pct=100; adkim=s; aspf=s | 98.40% | 100% | Excellent, low-risk enforcement profile |
| beta-ops.net | p=quarantine; sp=quarantine; pct=75; adkim=r; aspf=r | 92.10% | 75% | Moderate control with partial enforcement |
| gamma-cloud.org | p=none; pct=100; rua only | 89.70% | 100% | Weak monitoring-only posture |
| delta-secure.io | v=DMARC1; p=reject; sp=reject; rua+ruf; fo=1 | 96.80% | 100% | Strong posture with high visibility |
Formula Used
Alignment Rate = (Aligned Messages ÷ Total Messages Reviewed) × 100
Action Rate = ((Rejected Suspicious + Quarantined Suspicious) ÷ Total Suspicious Messages) × 100
Subdomain Coverage = (Protected Subdomains ÷ Tracked Subdomains) × 100
p or sp = none → 25 points, quarantine → 75 points, reject → 100 points
Strict alignment scores 100. Relaxed alignment scores 70.
Overall Score = 10% Version + 20% Policy + 10% Subdomain Policy + 10% Subdomain Coverage + 10% Alignment Mode + 10% pct Coverage + 10% Reporting + 10% Observed Alignment + 10% Suspicious Action
The overall score is a weighted policy-health model. It combines record correctness, enforcement strength, reporting readiness, domain coverage, and actual message-handling performance.
How to Use This Calculator
- Enter the domain you want to evaluate.
- Paste the full DMARC TXT value exactly as published or proposed.
- Add message review totals from your mail platform or DMARC reporting tool.
- Enter suspicious, rejected, and quarantined message counts for the same review period.
- Track your active subdomains and how many are covered by the intended policy.
- Submit the form to generate the score, parsed tag review, recommendations, and policy chart.
- Download the CSV for raw metric sharing or export the PDF for documentation.
Frequently Asked Questions
1. What does this checker actually measure?
It measures DMARC record quality, enforcement strength, reporting readiness, subdomain coverage, and observed handling performance from the numbers you provide.
2. Does a high score guarantee spoofing protection?
No. A strong score helps, but real protection also depends on correct SPF, DKIM, sender inventory control, and accurate mailbox reporting.
3. Why is p=reject scored higher than p=quarantine?
Reject blocks failing mail before delivery. Quarantine is still useful, but it usually leaves more room for risky messages to reach users.
4. Why does pct matter?
pct controls how much of your mail stream receives enforcement. Lower values reduce risk during rollout, but they also leave some traffic less protected.
5. Should every domain publish rua?
In most cases, yes. Aggregate reports help you see legitimate senders, track failures, and validate the impact of stronger DMARC enforcement changes.
6. Is strict alignment always better?
Strict alignment is more protective, but only when your sending infrastructure is clean and consistent. Some environments need relaxed alignment during transition.
7. Can I use this for proposed records?
Yes. It works well for draft policies. Paste the planned record, add estimated mail data, and compare rollout options before publishing changes.
8. Does this tool perform a live DNS lookup?
No. It evaluates the record text and metrics you enter. That makes it suitable for audits, planning, and offline security reviews.