Configuration6 min read · Updated Jun 2026

DomainScore: how it’s calculated and what it means

DomainScore gives you a single number (0 to 100) that summarises the email-authentication health of each domain in your account. Here is exactly how it is computed and what moves it.

Why a score?

Authentication health involves many variables (policy level, alignment rate, DKIM coverage, reporting completeness) that are hard to compare across domains at a glance. DomainScore collapses those into one number so you can instantly see which domains need attention and track improvement over time.

Score breakdown (100 points total)

ComponentWeightMax
SPF authentication
Valid record, under lookup limit, no PermError
20%20
DKIM coverage
% of emails signed with an aligned key
20%20
DMARC policy strength
none = 8 pts · quarantine = 18 pts · reject = 25 pts
25%25
Reporting and alignment
RUA/RUF configured, alignment rate on compliant sources
35%35

Grade bands

A90–100Protected
B75–89Good
C60–74Needs work
D40–59At risk
F0–39Exposed

How the score is updated

DomainScore recalculates once every 24 hours after the latest aggregate reports are processed. Policy changes (for example advancing from p=none to p=quarantine) are reflected immediately once your DNS change propagates and ClearDMARC detects the updated record.

What lowers your score most

  • Monitoring policy (p=none): contributes at most 8 of 25 policy points. Advancing to quarantine is the single biggest score jump available.
  • Unaligned sources: each percentage point of unaligned volume chips away at the reporting and alignment component.
  • SPF PermError: immediately zeroes the SPF component. Fix with ClearSPF.
  • Missing RUA address: you cannot score full points on reporting without an aggregate report destination configured.
Was this guide helpful?