16:07:32 | records: 34602 | dups: 0 | errors: 1 | sources: cache:34602 messages:0 | imap status: idle | last imap fetch: 16:07:30

dmarc poc

DMARC aggregate report viewer (proof of concept)

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

Top 10 source IPs

networkcount
UK-MICROSOFT-20060601 5

Top 10 header-from domains

domaincount
uakari.example.com 3
lemur.example.com 2

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
uakari.example.com 3
100%
UK-MICROSOFT-20060601 total 3
IP PTR Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 3
Enterprise Outlook total 3

No DMARC failures from this reporter.

source IPheader-fromcount dispositionDKIMSPFreport begin
2a01:111:f403:c005::5 uakari.example.com 1 none pass fail 2026-04-09 02:00
2a01:111:f403:c005::5 uakari.example.com 1 none pass fail 2026-04-22 02:00
2a01:111:f403:c005::5 uakari.example.com 1 none pass fail 2026-08-11 02:00
lemur.example.com 2
100%
UK-MICROSOFT-20060601 total 2
IP PTR Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 2
Enterprise Outlook total 2

Top 10 failing source IPs

countsource IPPTR
2 2a01:111:f403:c005::5ⓘ
domaindispdkimspf#
lemur.example.comnonefailfail2
 		mail-westus2azlp170100005.outbound.protection.outlook.com
source IPheader-fromcount dispositionDKIMSPFreport begin
2a01:111:f403:c005::5 lemur.example.com 1 none fail fail 2026-05-12 02:00
2a01:111:f403:c005::5 lemur.example.com 1 none fail fail 2026-05-12 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
uakari.example.com 3 / 3
100%
UK-MICROSOFT-20060601 3 / 3
IP PTR Fail / Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 3 / 3

DKIM-only — SPF not aligned

Enterprise Outlook total 3

No DMARC failures from this reporter.

source IPheader-fromcountdispositionDKIMSPFreport begin
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-04-09 02:00
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-04-22 02:00
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-08-11 02:00
lemur.example.com 2 / 2
100%
UK-MICROSOFT-20060601 2 / 2
IP PTR Fail / Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 2 / 2

no DMARC alignment

Enterprise Outlook total 2

Top 10 failing source IPs

countsource IPPTR
2 2a01:111:f403:c005::5ⓘ
domaindispdkimspf#
lemur.example.comnonefailfail2
 mail-westus2azlp170100005.outbound.protection.outlook.com
source IPheader-fromcountdispositionDKIMSPFreport begin
2a01:111:f403:c005::5lemur.example.com1none fail fail 2026-05-12 02:00
2a01:111:f403:c005::5lemur.example.com1none fail fail 2026-05-12 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
04-09
04-22
05-12
08-11
uakari.example.com 3 / 3
100%
04-09
04-22
05-12
08-11
UK-MICROSOFT-20060601 new 3 / 3
IP PTR Fail / Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 0 / 3
Enterprise Outlook total 3

No DMARC failures from this reporter.

source IPheader-fromcountdispositionDKIMSPFreport begin
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-04-09 02:00
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-04-22 02:00
2a01:111:f403:c005::5uakari.example.com1none pass fail 2026-08-11 02:00
lemur.example.com 2 / 2
100%
04-09
04-22
05-12
08-11
UK-MICROSOFT-20060601 new failing 2 / 2
IP PTR Fail / Total DMARC failures share
2a01:111:f403:c005::5 mail-westus2azlp170100005.outbound.protection.outlook.com 2 / 2
Enterprise Outlook total 2

Top 10 failing source IPs

countsource IPPTR
2 2a01:111:f403:c005::5ⓘ
domaindispdkimspf#
lemur.example.comnonefailfail2
 mail-westus2azlp170100005.outbound.protection.outlook.com
source IPheader-fromcountdispositionDKIMSPFreport begin
2a01:111:f403:c005::5lemur.example.com1none fail fail 2026-05-12 02:00
2a01:111:f403:c005::5lemur.example.com1none fail fail 2026-05-12 02:00