Skip to main content
Open DMARC → Reports to analyze report data across all monitored domains or filter it to one domain. Choose a 7-day or 30-day range from the top of the page.

​
Summary metrics

All rates are message-weighted. For example, a source record representing 10,000 messages contributes 10,000 assessments, while a record representing one message contributes one.
DMARC pass is not the same as both DKIM and SPF passing. One aligned authentication path is enough for DMARC.

​
Authentication volume

The daily chart separates DMARC-aligned messages from failing messages. Beneath it, dispositions show what receivers reported doing with the assessed mail:
  • Delivered (none) — no quarantine or rejection was applied
  • Quarantined — the receiver treated the message as suspicious, often placing it in spam
  • Rejected — the receiver reports rejecting the message
A failing message can still have a none disposition when the domain uses p=none, enforcement applies to only part of the traffic, or the receiver records a local policy override.

​
Latest observed policy

The policy card reflects the most recent aggregate report in the selected range. It can include:
  • Domain, subdomain, and non-existent-subdomain policies
  • DKIM and SPF alignment modes
  • The enforcement percentage
This is the policy reported by a receiver, not a live DNS lookup. Recent DNS changes may not appear until a new report arrives.

​
Sending sources

JetEmail groups source IPs using the DKIM and SPF domains contained in reports. Recognized providers may be combined under a name such as Google Workspace, Microsoft 365, Amazon SES, Mailchimp, SendGrid, Mailgun, Postmark, HubSpot, Salesforce, or Zoho Mail. Other IPs remain Unreviewed sending network entries. For each source, the dashboard shows:
  • Total message volume and share of the selected period
  • DMARC, DKIM, and SPF pass rates
  • Reported sending IPs
  • DKIM and SPF authentication domains
  • A status and suggested next action
Known providers with a DMARC pass rate of at least 95% are marked healthy. Lower rates are marked as needing attention. Unknown networks remain unreviewed regardless of pass rate.
Provider identification is a best-effort inference from authentication domains. A recognized name does not prove that the source is authorized to send for your organization.

​
Investigate a source

Select a source to open its detail panel, then:
  1. Confirm the provider or IP belongs to a service your organization uses
  2. Compare the visible From domains with the listed DKIM and SPF domains
  3. Check whether DKIM, SPF, or both need attention
  4. Follow the recommendation, then watch later reports for improvement
Aligned DKIM is usually the more resilient path because forwarding commonly breaks SPF while a valid DKIM signature can survive.

​
Receiver reports

Expand Receiver reports to inspect the aggregate files behind the analytics. Each row shows the policy domain, reporter, report period, assessed volume, and DMARC pass rate. Open a report to see:
  • Published policy and alignment settings reported by the receiver
  • Reporter metadata and external report ID
  • Message totals and normalized source records
  • Per-source evaluated DKIM, SPF, and disposition results
  • Authentication domains and DKIM selectors
  • Policy override reasons
  • The original decompressed aggregate XML and its SHA-256 digest
The report period describes when the receiver observed the mail. The received timestamp describes when JetEmail accepted the aggregate report, so the two times can differ.