18:56:50 | records: 36644 | dups: 0 | errors: 1 | sources: cache:36644 messages:0 | imap status: idle | last imap fetch: 18:56:48

dmarc poc

DMARC aggregate report viewer (proof of concept)

schlittermann.de
EN | DE
clear
records
1
parse errors
1
unique source IPs
1
report date range
2026-08-04 — 2026-08-04 02:00:00

Top 10 source IPs

networkcount
YANDEX-V6-c0e--48 1

Top 10 header-from domains

domaincount
weasel.example.com 1

Phase 1 — Discovery: who is sending mail from your domains? ⓘYou have published p=none and are collecting data. Nobody is being blocked yet.

Focus on message volume, not IP count — a source sending 50 000 messages is urgent; one sending 3 is noise.

Both-fail sources (DKIM fail AND SPF fail) are either spoofing attempts or services that were set up without telling you. Surface these first.

Expand a domain, then open "By source IP" to see the quadrant breakdown per prefix group.

Sender landscape
both pass SPF fail DKIM fail both fail
weasel.example.com 1
100%
UNKNOWN total 1
IP PTR Total DMARC failures share
2a02:6b8:c0e:500:1:45:d181:d100 forward100a.mail.yandex.net 1
google.com total 1

No DMARC failures from this reporter.

source IPheader-fromcount dispositionDKIMSPFreport begin
2a02:6b8:c0e:500:1:45:d181:d100 weasel.example.com 1 none pass fail 2026-08-04 02:00

Phase 2 — Hardening: what would break if you tightened the policy? ⓘYou understand your sender landscape and want to move from p=none toward p=quarantine or p=reject. The risk is collateral damage to legitimate mail.

Policy readiness % = share of messages that would survive a reject policy today.

SPF-only sources need DKIM signing added in their sending platform.

DKIM-only sources need their SPF record aligned with your From: domain.

No DMARC alignment sources send all mail failing — configure or block.

Inconsistent sources have mixed results — investigate per-IP.

DMARC readiness
both pass SPF fail DKIM fail both fail
weasel.example.com 1 / 1
100%
UNKNOWN 1 / 1
IP PTR Fail / Total DMARC failures share
2a02:6b8:c0e:500:1:45:d181:d100 forward100a.mail.yandex.net 1 / 1

DKIM-only — SPF not aligned

google.com total 1

No DMARC failures from this reporter.

source IPheader-fromcountdispositionDKIMSPFreport begin
2a02:6b8:c0e:500:1:45:d181:d100weasel.example.com1none pass fail 2026-08-04 02:00

Phase 3 — Steady state: did something break? Is anyone spoofing you? ⓘYou have a tight policy in place (p=quarantine or p=reject). Watch for anomalies.

New sources — an IP appearing for the first time in the last 30 days that was not seen before. Could be a new legitimate sender nobody configured, or the start of a spoofing campaign.

Active failures — sources still failing DMARC under a strict policy in the last 30 days. Persistent failures with high volume are either spoofing or a misconfigured legitimate service that needs fixing.

If a major reporter (Google, Microsoft) stops appearing, your rua= address may be bouncing.

Alignment health — last 30 days
both pass SPF fail DKIM fail both fail
08-04
weasel.example.com 1 / 1
100%
08-04
UNKNOWN new 1 / 1
IP PTR Fail / Total DMARC failures share
2a02:6b8:c0e:500:1:45:d181:d100 forward100a.mail.yandex.net 0 / 1
google.com total 1

No DMARC failures from this reporter.

source IPheader-fromcountdispositionDKIMSPFreport begin
2a02:6b8:c0e:500:1:45:d181:d100weasel.example.com1none pass fail 2026-08-04 02:00