The email deliverability platform that finds the failing sender

DMARC aggregate reports are the receivers' own record of your mail: who sent it, how much, and whether it passed SPF and DKIM. That makes them the ground truth for deliverability work — instead of guessing why campaigns land in spam, you see which sending platform is failing authentication and fix that.

Compliant mail passed DMARC — it authenticated and aligned with your domain. Failed mail came from a source that didn't authenticate correctly. Unknown volume traces to no confirmed sender, which can mean a shadow tool or spoofing. Forwarded mail passed through an intermediary that often breaks SPF on the way — expected, and tracked separately so it doesn't read as an attack.

Their requirements center on authentication: SPF and DKIM, a DMARC policy, and alignment for bulk senders. Palisade's job is exactly that — getting every legitimate sender authenticated and your policy enforced — and the compliance view shows where each domain stands.

No — placement here is continuous, drawn from real traffic. A seed test sends one message and checks where that message lands; Palisade reads what receivers report about every message, so you see placement by provider alongside which real sender is failing and when it started. The free Email Deliverability Test covers the one-shot check.

That's the point of the trend view. A platform that starts failing DKIM shows up in report data as failed volume — and as a ticket — while the damage is still building, so the fix can ship before the spam-folder complaints arrive.

Sending sources are detected from real report traffic, whatever they are — ESPs, CRMs, helpdesks, billing systems, marketing automation. You confirm the legitimate ones, and anything new that appears later opens a ticket for review.