In this sample, a report row counts 35 messages whose SPF check passed—but the SPF domain is unaligned, and DKIM failed. A DMARC report analyzer helps turn that XML row into a practical next step: identify the sending system, confirm its owner, and fix or investigate its authentication before changing policy.

A DMARC report analyzer parses aggregate XML sent to the address in your domain’s rua tag and groups results by source. It shows message counts, source IPs, SPF and DKIM outcomes, alignment, and reported disposition. It does not validate DNS records or identify the owner of an unfamiliar IP; those require separate checks and investigation.

What a DMARC report analyzer does—and what it does not do

Aggregate DMARC reports arrive as XML and summarize authentication results observed by receiving mail systems. An analyzer makes that data easier to review by grouping records and displaying fields such as source IP, message count, and authentication results. It is a way to inspect reported traffic, not a verdict on who sent it or why a message failed.

Three tools answer different questions:

  • A DMARC aggregate-report analyzer parses report XML and organizes the sending sources and results it contains.
  • A DMARC record checker looks up DNS and checks the published DMARC record. It cannot tell you which sources appeared in reports.
  • An email-header analyzer examines authentication results for one message. It cannot summarize a reporting period across receivers.

For example, a DNS checker can confirm that a rua tag is present, while an analyzer can show whether a receiver sent a report to that address and what its records contain. To check DNS setup, use our DMARC record check guide. The aggregate-report format is defined in RFC 7489.

What a DMARC aggregate report contains

A RUA report is an aggregate summary sent to the reporting destination named in rua in your DMARC record. It typically contains report metadata, a published-policy snapshot, and one or more records describing groups of messages. It is not a message-by-message archive, and it does not include message bodies.

A report can contain the reporting organization, a report ID, and a time range; the domain’s published policy and alignment modes; and traffic records with source IPs, counts, dispositions, and SPF and DKIM results. An analyzer may display the fields in tables, but the underlying values are still useful when you need to trace a result back to the XML.

Here is a shortened illustrative <record> with a common diagnostic pattern:

<record>
  <row>
    <source_ip>198.51.100.24</source_ip>
    <count>35</count>
    <policy_evaluated>
      <disposition>none</disposition>
      <dkim>fail</dkim>
      <spf>fail</spf>
    </policy_evaluated>
  </row>
  <identifiers>
    <header_from>example.com</header_from>
  </identifiers>
  <auth_results>
    <spf>
      <domain>bounce.vendor.example</domain>
      <result>pass</result>
    </spf>
    <dkim>
      <domain>vendor.example</domain>
      <result>fail</result>
    </dkim>
  </auth_results>
</record>

Read the fields together. source_ip is the observed sending IP; count is the number of messages represented by this record. auth_results says SPF passed for bounce.vendor.example, but policy_evaluated says SPF did not pass DMARC, because that authenticated domain did not align with the visible example.com From domain. DKIM failed too, so neither authentication path provided an aligned pass. The disposition value is the receiver’s reported handling—not a statement about who controls the IP.

How to analyze a DMARC report step by step

The useful output is a sender inventory with an owner and an action for each source—not simply a percentage of passes. Start with the report’s domain, reporting organization, and time range so you know what data the rows cover.

  1. Open the XML. Import the attachment into a parser or inspect it locally. Confirm the report covers the domain you are investigating and note its time period.
  2. Group by source and count. Sort records by IP and message volume. A source representing 800 messages merits prompt owner identification; a row with one message still deserves review if the source is unexplained.
  3. Match expected systems. Compare IPs and authentication domains with your mail, billing, support, marketing, and application-service inventory. Ask the system owner if an integration is unclear.
  4. Compare authentication and alignment. Review both the raw auth_results and policy_evaluated values. A raw SPF pass is not a DMARC pass when its domain is unaligned.
  5. Record a decision. Mark the source as known and passing, known but misconfigured, or unresolved. Assign a person to confirm the system or correct its authentication, then compare later reports.

For instance, an illustrative inventory might look like this:

SourceCountReport findingTriage action
Campaign provider, identified by your team800DKIM passes and aligns; DMARC passesRecord its owner and signing domain; retain as an approved sender
198.51.100.24, not yet identified35SPF passes for bounce.vendor.example but is unaligned; DKIM failsAsk service owners whether they use the vendor; check its DKIM and From-domain configuration before enforcement

The IP in the sample is a documentation-only address, not a real sending service. In a live investigation, use the actual address from your report. Start with reverse DNS, for example dig -x IP_ADDRESS +short, then check WHOIS or RDAP registration data and an ASN lookup to learn which network announces the address. These lookups can suggest a hosting provider, but they do not prove which customer or application sent the mail. Ask internal system owners and the named provider to confirm.

How to interpret failures, alignment, and DMARC policies

SPF and DKIM results describe authentication checks; DMARC also compares authenticated identities with the visible From domain. A message passes DMARC when at least one path both passes and aligns. A raw SPF pass or DKIM pass alone is not enough.

For SPF, the authenticated domain is commonly associated with the envelope sender or return path. For DKIM, inspect the signing domain shown in the report. In relaxed alignment, a subdomain can align with its organizational domain; strict alignment requires an exact domain match. For example, mail.example.com can align with example.com in relaxed mode but not strict mode. The aspf and adkim tags control SPF and DKIM alignment modes.

The policy values describe the domain owner’s requested handling of messages that fail DMARC:

  • none requests no specific enforcement action and is useful for observing results while investigating senders.
  • quarantine asks receivers to treat failing messages as suspicious; receiver handling can differ.
  • reject asks receivers to reject failing messages.

A failure does not by itself prove spoofing. The sample’s SPF pass and DMARC failure have a concrete explanation: the SPF domain differs from the visible From domain, while DKIM also fails. Forwarding or a legitimate third-party sender with incomplete configuration can produce other failures. Check the source, identities, and policy override details before deciding what the row means. Our DMARC record enforcement guide covers the policy side of that decision.

What to do when a report shows an unknown sender or failure

Treat an unfamiliar source as an investigation, not an automatic block list. Look up its IP with reverse DNS, WHOIS or RDAP, and an ASN lookup; compare the result with your vendors and infrastructure. Then ask the likely service owner whether the system sends mail using your domain. A network provider’s name is a clue, not final attribution.

If the owner confirms a legitimate sender, inspect its SPF authorization, DKIM signing domain, and return-path configuration. The specific fix depends on which identifier is misaligned: a DKIM failure may require correcting the service’s signing setup, while an SPF pass that is unaligned may require a return-path or domain configuration the service supports. Do not add a vendor to your SPF record or change DMARC policy based only on an unfamiliar IP.

Volanea is built on Amazon SES, and we provide guided setup for SPF, DKIM, and DMARC with automatic checks of domain authentication. In our experience, a provider-level SPF pass is not enough to establish DMARC alignment: the report’s authenticated domain still has to match the visible From domain under the domain’s alignment mode. Check the actual auth_results identifiers and policy_evaluated outcome for the sending setup rather than assuming a passing check means the whole path aligns. Details about our SES-based setup are on our Amazon SES comparison page.

Free DMARC report parser or ongoing monitoring software?

For a one-off XML review, parsedmarc is a concrete option: its documentation shows parsed report output and field-level results. It is a self-managed parser rather than a hosted dashboard, so the software license cost is $0; you still need to account for setup, compute, storage, and someone to interpret findings. A browser-based parser can be faster for a single file, but the report is being uploaded to that service.

Ongoing monitoring is more useful when reports arrive from many receivers, teams add senders frequently, or you need history across domains. A named hosted option is DMARC Analyzer, which focuses on aggregate-report analysis and monitoring. Hosted service prices and plan limits vary, so compare the specific product’s current pricing and retention terms with your reporting volume before committing.

ApproachExampleBest fitMain tradeoff
Self-managed parsingparsedmarcEngineering teams that want to process XML under their own operational controlsYou maintain the parsing workflow and review process
One-off browser parsingAn online DMARC XML parserA single report or a quick investigationYou must assess upload handling and repeat the review manually
Hosted monitoringDMARC AnalyzerTeams that need reports collected and compared over timeCost and features depend on the service’s plan

Choose a one-off parser when you have a small number of files and an owner who can follow up. Consider monitoring when report collection, sender changes, or cross-team handoffs are making manual review unreliable. Either way, use your own inventory to establish whether a source is authorized; a dashboard cannot know which business system your company intended to send mail.

Privacy and security when uploading DMARC XML

Aggregate XML does not expose message bodies, but it can reveal operational details: your domain, source IPs, report timestamps, message counts, reporting organizations, and authentication identifiers. A file may therefore show that a particular service sends mail for your organization, even if it contains no message content.

Before using an online parser, check who can access uploaded files, whether processing is temporary or retained, and whether deletion is available. For example, a report covering a production domain with several vendors may disclose more about your sending architecture than a test report from a domain with one sender. If your organization does not allow that data to leave approved systems, parse locally with a tool such as parsedmarc or use an approved monitoring service.

From report findings to a safer DMARC policy

Use repeated report evidence to confirm the legitimate sender inventory before moving from none to quarantine or reject. For each known service, record its owner, visible From domain, SPF and DKIM identifiers, and whether at least one result aligns. For a failed row, document whether the next step is a configuration fix, an owner check, or investigation of unexplained traffic.

Make policy changes only after legitimate systems have a working aligned path, and review later reports for unexpected results. If a source is still unresolved, keep that investigation separate from sender fixes; a stricter policy can affect legitimate mail when a forgotten service has not been configured. Our DMARC record builder can help prepare a valid policy record once you know what policy you intend to publish.

When the report points to a sender-configuration task, Volanea brings transactional email, campaigns, and automated workflows together on Amazon SES, with guided domain authentication and automatic checks. Start free with 1,000 emails a month if you want to configure a sending setup and review its authentication status alongside your email workflow.

FAQ

How can I tell whether an unknown IP is a legitimate sender?

Start with reverse DNS, then use WHOIS or RDAP and an ASN lookup to identify the network associated with the address. Those results can narrow the search but do not name the customer or application behind the IP. Compare the report’s authentication domains and time range with your service inventory, then ask the likely system owner to confirm.

When should I move from p=none to quarantine or reject?

Move only after you have identified the legitimate senders and confirmed that each has an aligned SPF or DKIM path. A record showing 800 passing campaign messages is useful evidence for that sender, but it says nothing about a separate 35-message source. Resolve those sources and review subsequent reports before tightening enforcement.

What does a DMARC report analyzer cost?

parsedmarc has a $0 software license cost as a self-managed parser, although setup and operating infrastructure still require resources. Hosted monitoring products have their own pricing and plan terms; there is no single market-wide rate. Compare the service’s current plan against the number of domains, report history, and workflow features you need.

Does an SPF pass mean the message passes DMARC?

No. SPF can pass for an authenticated return-path domain that does not align with the visible From domain. In the sample record, SPF passes for bounce.vendor.example, but DMARC evaluates SPF as failing for example.com; DKIM also fails. The message needs at least one passing, aligned SPF or DKIM result to pass DMARC.