+8.2%
677,980
Total messages
Reporting period · 22 May – 21 Jun 2026
Email authentication for example.com
+1.3pt
97.2%
Aligned (DMARC pass)
2 new
11
Active sending sources
unverified
18,934
Messages that couldn't be verified
Compliant vs non-compliant volume
Daily messages over the last 30 days
Aligned
Failing
Plain-English summary
What changed this period
Authentication held strong at 97.2% aligned across 677,980 messages. Your four core senders — Google Workspace, Microsoft 365, Salesforce and Mailchimp — are fully aligned on both SPF and DKIM.
However, a new unrecognised source (185.220.41.7, Netherlands) sent 15,718 messages that could not prove they came from you — no DKIM signature and an SPF domain unrelated to yours. A second source in Russia (45.155.205.18) also failed to verify — worth a look.
Recommended Legitimate mail is fully aligned, so you're safe to advance toward p=reject. This will block the unverified streams outright with no impact on real delivery.
Sending sources
Who is sending as you, and whether each message could be verified
| Source | IP | Country | Messages | SPF | DKIM | DMARC |
|---|
Each cell shows two things.
First, whether the check succeeded — ✓ it did, ✕ it didn't. A ✕ usually
means the sender isn't listed in your SPF record, the message was altered in transit so
its signature no longer verifies, or it carried no signature at all.
Second, whose domain the check was for — = yours · ≠ someone else's ·
○ none was present.
DMARC only counts a message as verified when a check both passes and is for your
domain.
Amber cells are information, not problems: DMARC still
verified those messages and nothing is being rejected. Red cells are where mail is
actually at risk. Hover any cell for the specific reason.
Top countries
By message volume
Policy advisor
Time to enforce
Current published policy
v=DMARC1; p=none; rua=mailto:rua@…
p=noneMonitoring · you are here
p=quarantine · pct=25Recommended next — ramp 25→50→100%
p=rejectFull enforcement — spoofing blocked