Skip to content
  • There are no suggestions because the search field is empty.

What visual DMARC analysis should show you

Good DMARC analysis should show you each source sending mail as your domain, whether you've confirmed it as yours, how much of its mail passes or fails aligned SPF and DKIM, what receivers did with it, and how all of that changes over time. It should also be honest about what the data can't tell you. Aggregate reports are daily, they don't cover every receiver, and they say nothing about inbox placement. A view that hides those limits will mislead you at exactly the moment you decide whether to enforce.

Visual analysis exists because raw reports don't scale. The XML is not human readable in bulk, and reports are meant to be machine-parsed. Whether you use a service or build your own, the checklist below is what to expect from it.

What good DMARC analysis answers

Every item here maps to a field in the aggregate report format, so any honest DMARC dashboard can show it. Field details are in A field-by-field walk-through of a DMARC aggregate report.

A useful view shows… Built from The decision it supports
Sending sources grouped into services, with volume source_ip, count, DKIM domain and selector, envelope_from Your inventory (How to inventory sending sources). Reports don't carry service names, so any grouping or name is inferred by the tool or by you
Which sources you've confirmed as yours Your own inventory, matched to the sources What to fix and what to leave failing (Legitimate mail vs spoofing in reports)
Raw SPF and DKIM results next to aligned results auth_results vs policy_evaluated The "passes but doesn't align" gap, which points to a fix in the sender's setup
DMARC pass and fail volume and rate, overall and per source policy_evaluated and count Readiness for quarantine or reject (When you are ready for p=quarantine, When you are ready for p=reject)
Disposition and override reasons disposition and reason Whether receivers applied your policy request, and where forwarding and mailing lists appear
Each domain and subdomain separately policy_published domain, header_from Subdomain coverage (Subdomain policy (sp))
Your policy as receivers saw it policy_published Confirmation that a DNS change was picked up, and days that mixed old and new policy
Which receivers reported org_name Coverage. A missing reporter is a gap in the data, not clean mail
Trend over time date_range New sources appearing, pass rates after fixes, the effect of policy changes
Record errors receivers reported error Broken records, such as invalid tags or duplicate records
DKIM keys in use DKIM domain and selector Key rotation and vendor signing checks (DKIM selectors and DNS records, How to rotate a DKIM key)

The raw-versus-aligned row deserves special attention. Microsoft calls the gap between "authentication pass and alignment pass" the most important insight in aggregate reports. A chart that only shows DMARC pass and fail hides the reason a source fails, and the reason is usually what you need to fix it.

Metrics worth tracking at program level

For leadership or a 90-day review, a few numbers summarize the whole program. These are working recommendations, not standards:

  • Share of your domains with a published DMARC record and working report delivery.
  • Share at quarantine or reject, with a note on why the rest are still at p=none (Why staying at p=none is a problem).
  • Share of mail volume that passes DMARC with aligned DKIM.
  • Number of unidentified sources above a volume threshold, and how long it takes to classify new ones.

Limits a good view makes visible

  • Daily, not real-time. Reports typically cover one UTC day. A view built on aggregate data inherits that daily rhythm.
  • Partial coverage. Not every receiver sends reports. Microsoft 365 only sends them when the receiving domain's MX points directly to Microsoft 365, and mail rejected early in the SMTP transaction never appears (Why DMARC reports do not arrive).
  • No content, recipients, or placement. Aggregate reports carry no message content or individual addresses, and nothing about inbox or spam placement (Authentication vs inbox placement).
  • Last-hop IPs. Forwarded mail shows the forwarder's IP, not yours.
  • Untrusted input. Reports can be forged or malformed. Whatever processes them should defend against compressed or XML "bombs".
  • Out of scope. Lookalike domains and display-name abuse don't appear in the data, because DMARC only covers your exact From domain.

What visual analysis doesn't do

It informs decisions. It doesn't enforce them. Receivers apply your DMARC policy, and policies are requests, so no dashboard stops spoofing on its own. It also can't tell you that mail reached the inbox, or that you've seen every email sent as your domain.

Where BIMI Certifications fits

BIMI Certifications provides DMARC reporting and visual analysis: it receives your aggregate reports and presents them visually so you can see sources, authentication and alignment results, and trends. You can still open and download the original XML reports when you want to check a row against the walk-through in A field-by-field walk-through of a DMARC aggregate report.

Mistakes worth avoiding

  • Calling a domain healthy from one reporter or one day.
  • Charts that show only DMARC pass and fail, so the alignment fix stays invisible.
  • Treating "no data from receiver X" as "no failures at receiver X."
  • Reading forwarding and mailing-list failures as attacks (Reports show sources we do not recognize).
  • Stopping once you reach enforcement. New senders appear over time. Microsoft's advice is to review weekly during initial deployment and monthly once stable.

Free DMARC account

Turn raw DMARC reports into a readable dashboard

Point your rua address to our platform and read the results by sender and source instead of opening XML files.

  • Results grouped by sending source
  • SPF, DKIM and alignment results per sender
  • The original XML reports are still there to download

Create a free DMARC accountTalk to an expert

FAQ

What should I look at first in a DMARC dashboard?

The highest-volume sources that fail both aligned SPF and aligned DKIM, and whether they're yours.

Can a dashboard show real-time DMARC results?

Not from aggregate reports. They typically cover a day at a time.

Does visual analysis show whether my mail reached the inbox?

No. Aggregate reports don't include placement.

Why don't my numbers match what I sent?

Not every receiver reports, and some mail is rejected before it can be counted.

Do we need a tool, or can we build our own?

Either works. You can use a third-party service or your own tools. It's a question of time and resources. Learning the raw format first (Aggregate (RUA) vs forensic (RUF) reports, A field-by-field walk-through of a DMARC aggregate report) helps you judge any tool.