# How to Read DMARC Reports: XML Fields, Sorting Your Senders and Deciding When to Move to p=reject

> How to read DMARC reports: decode every rua XML field, aligned vs raw SPF/DKIM results, classify your senders and know when p=reject is safe, in 7 steps.

Source: https://digitalbridge.com.tr/en/blog/how-to-read-dmarc-reports.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Business Email & Documents
Published: 2026-10-04 · Updated: 2026-10-22

[DMARC reports](https://digitalbridge.com.tr/en/glossary.html#dmarc-report) are XML files that receiving mail servers send you, grouping messages seen under your domain by source IP with their SPF, DKIM and DMARC results. To read one, ask three questions of every row: which source sent it, how many messages, and did it pass in alignment with your visible From domain? The answers show whether `p=reject` is safe.

## Key takeaways

- An aggregate (rua) DMARC report usually arrives once a day, separately from each reporting provider, as a compressed XML attachment defined by RFC 7489.
- The DMARC verdict depends on the aligned SPF and DKIM results under `policy_evaluated`, not the raw results under `auth_results`.
- Every sending source falls into one of five groups: healthy traffic, misaligned SaaS tool, uninventoried sender, forwarding, or domain impersonation.
- Once nearly all legitimate mail volume passes in alignment for several weeks, move first to `p=quarantine`, then to `p=reject`.
- [EasyDMARC's 2026 DMARC Adoption Report](https://easydmarc.com/blog/easydmarc-releases-2026-dmarc-adoption-report/) found 52.1% of domains have a DMARC record, but only about 23% enforce it.

## Why DMARC reports sit unread

The usual story goes like this. Someone in IT, or an outside contractor, published a `_dmarc` record with `p=none` and a `rua` address. What SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail) and DMARC (Domain-based Message Authentication, Reporting and Conformance) records are, and how to publish them, is covered in our [SPF, DKIM and DMARC guide](https://digitalbridge.com.tr/en/blog/spf-dkim-dmarc-explained.html). From then on, compressed XML attachments arrive every day from Google, Microsoft, Yahoo and others. Nobody opens them, the mailbox fills up and the policy stays in monitoring mode for months.

With DMARC reports, the obstacle is interpretation rather than technology. Raw XML is a wall of IP addresses, Unix timestamps and nested pass/fail values. Nothing tells you at a glance which row is your accounting software's invoice notification and which is a fraudster sending in your name. This article gives you a method for telling them apart.

## What does it cost to leave DMARC reports unread?

Leaving DMARC at `p=none` leaves your domain open to impersonation: a monitoring policy reports spoofed mail but does not stop it. [EasyDMARC's 2026 DMARC Adoption Report](https://easydmarc.com/blog/easydmarc-releases-2026-dmarc-adoption-report/), which scanned 1.8 million domains, found that 52.1% have a DMARC record but only about 23% enforce a quarantine or reject policy.

> The same report found that only around 9% of domains combine an enforcement policy with reporting. ([EasyDMARC, 2026 DMARC Adoption Report](https://easydmarc.com/blog/easydmarc-releases-2026-dmarc-adoption-report/))

The gap has a price. According to the [FBI IC3 2025 Internet Crime Report](https://www.ic3.gov/AnnualReport/Reports/2025_IC3Report.pdf), [phishing](https://digitalbridge.com.tr/en/glossary.html#phishing)/spoofing was the most-reported crime type in the US in 2025, with 191,561 complaints. A spoofed "our bank details have changed" email sent from your own domain to your customers is the shortest route to [bank detail change fraud](https://digitalbridge.com.tr/en/blog/bank-detail-change-email-fraud.html).

Leaving DMARC reports unread hurts deliverability too. According to [Microsoft's announcement for high-volume senders](https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%e2%80%99s-new-requirements-for-high%e2%80%90volume-senders/4399730), from 5 May 2025 domains sending more than 5,000 emails a day to Outlook.com, Hotmail and Live addresses need SPF, DKIM and a DMARC policy of at least `p=none`, aligned with SPF or DKIM. [Google's email sender guidelines](https://support.google.com/a/answer/81126?hl=en) have likewise required SPF, DKIM and DMARC since 1 February 2024 from anyone sending more than 5,000 messages a day to Gmail accounts.

If nobody reads the reports, a legitimate sender that fails alignment also goes unnoticed, and nobody can explain why its mail lands in junk. Our guide to [emails going to spam](https://digitalbridge.com.tr/en/blog/emails-going-to-spam-fix.html) treats report reading as one part of that wider deliverability picture.

## Which fields does an aggregate (rua) DMARC report contain?

An aggregate DMARC report is an XML document defined in [RFC 7489](https://www.rfc-editor.org/rfc/rfc7489). It usually arrives once a day from each reporting provider, compressed as gzip or zip. It has three top-level parts: report metadata, the published policy and one `record` per sending source. The fields that matter:

| Block / field | What it tells you | What to look for |
|---|---|---|
| `report_metadata` → `org_name`, `date_range` | Who sent the report and the period it covers (UTC, Unix time) | Are the big providers reporting every day? |
| `policy_published` → `p`, `sp`, `adkim`, `aspf`, `pct` | The policy the receiver saw in your DNS that day | Is it the record you expect; is the subdomain policy (`sp`) right? |
| `row` → `source_ip`, `count` | Which IP sent how many messages | High-volume IPs you do not recognise |
| `policy_evaluated` → `disposition`, `dkim`, `spf` | The **aligned** DMARC result and what the receiver did | High-volume rows showing `fail` |
| `identifiers` → `header_from` | The visible From domain | Are your subdomains appearing too? |
| `auth_results` → `domain`, `result` under `dkim` / `spf` | The **raw** SPF and DKIM result and the domain it passed for | Is that domain yours, or your provider's? |

The key to reading DMARC reports lies in the last two rows of the table: the difference between `policy_evaluated` and `auth_results`. A common mistake is to see `spf result=pass` under `auth_results` and relax. If SPF passed for your newsletter platform's own domain, `policy_evaluated` still shows `spf` as `fail`, because DMARC requires the authenticated domain to align with `header_from`. What counts is the aligned result, not the raw one.

The `disposition` field under `policy_evaluated` shows what the receiver actually did: `none`, `quarantine` or `reject`. Seeing `none` while your policy is `p=none` is expected. Sometimes a `reason` such as `forwarded` or `mailing_list` appears, meaning the receiver deliberately relaxed your policy for that traffic.

### What do forensic (ruf) DMARC reports contain?

Alongside aggregate data you can also request forensic reports (`ruf`) for individual messages that fail DMARC. These carry message headers and sometimes fragments of content. Many large providers do not send them for privacy reasons. Where forensic reports do arrive, the addresses and subject lines they contain are personal data, so set access and retention rules within your [data protection compliance programme](https://digitalbridge.com.tr/en/blog/kvkk-compliance-steps.html); in Turkey that means the KVKK, the country's GDPR-style data protection law.

## How to read DMARC reports: a seven-step working method

1. **Confirm the reports are arriving.** If your `rua` address sits on another domain (a report analysis service, for example), that domain must publish a `_report._dmarc` verification record showing it accepts reports for you; otherwise providers will not send them.
2. **Do not read XML by hand; parse it.** Extract the attachments and load them into a table: provider, date, `source_ip`, `count`, `header_from`, aligned and raw results. Combine several weeks of data before drawing conclusions.
3. **Turn IP addresses into senders.** Use reverse DNS (PTR) and network ownership to label each source: "our mail server", "e-invoicing provider", "CRM", "unknown".
4. **Put aligned and raw results side by side.** Raw `pass` with aligned `fail` means the problem is domain matching, not authorisation.
5. **Place every source in one of five groups.** The source classification table sets out the groups.
6. **Fix it with whoever owns the source.** Ask the service provider to sign with DKIM on your own domain, or move the envelope sender (Return-Path) to one of your subdomains.
7. **Track the aligned pass rate weekly.** When almost all legitimate volume passes in alignment, move to `p=quarantine`; once that holds steady, go to `p=reject`, using `pct` to phase the change if needed.

### How do you classify the sources in a DMARC report?

| What you see | Likely meaning | Action |
|---|---|---|
| Your own IP, aligned DKIM and SPF `pass` | Healthy legitimate traffic | None; keep monitoring |
| Known service, raw `pass`, aligned `fail` | SaaS tool signing with its own domain | Custom-domain DKIM and Return-Path in that service |
| Known service, SPF and DKIM `fail` | Sender missing from your inventory | Add to SPF, publish its DKIM key in DNS |
| SPF `fail`, aligned DKIM `pass`, source is a forwarding server | Forwarding or a mailing list | DMARC still passes via DKIM; make sure DKIM is on for every source |
| Unknown IPs, everything `fail`, scattered networks and countries | Someone impersonating your domain | Do not "fix" these; p=reject exists to stop them |

The hardest call is telling "unknown" apart from "forgotten". Watch a suspicious IP for a week: if its volume follows office hours and someone remembers a tool, it is probably a forgotten sender. The usual suspects are web forms, invoice notifications and old multifunction printers; the invoicing side is covered in our guide to [e-invoice integration in Turkey](https://digitalbridge.com.tr/en/blog/e-invoice-integration-turkey.html).

One attack never appears in your reports at all: mail from a domain that merely looks like yours. That domain is not yours, so its reports do not come to you. We deal with that gap in [lookalike domain attacks](https://digitalbridge.com.tr/en/blog/lookalike-domain-attacks.html).

## How Digital Bridge handles DMARC reporting

Most of a DMARC project is not writing records but reading reports and fixing senders with their owners. Within our [cyber security consultancy](https://digitalbridge.com.tr/en/consultancy/cyber-security.html), we run it like this:

- **Discovery:** We review the SPF, DKIM, DMARC and PTR records for your domains, parse the reports you already have and build a list of sources.
- **Classification and fixes:** We label each source with your teams. Where mail from an ERP, CRM or custom application needs changing, our [system integrations](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) team corrects the sending configuration.
- **Pilot domain:** We move a low-volume domain or subdomain to `reject` first to prove the method, then tackle the main domain.
- **Ongoing visibility:** If you want report data in your own reporting environment, we can turn the aligned pass rate into a metric on a [BI dashboard](https://digitalbridge.com.tr/en/data-analytics/bi-dashboard.html); which metrics earn their place is discussed in [BI dashboard KPIs](https://digitalbridge.com.tr/en/blog/bi-dashboard-kpis.html). If you centralise security events, DMARC summaries can also feed your [SIEM and log management](https://digitalbridge.com.tr/en/blog/siem-log-management-basics.html) pipeline.

If you are changing mail platforms, the old server's IPs will keep appearing in reports for a while; sequencing the move as in our [email migration guide](https://digitalbridge.com.tr/en/blog/email-migration-guide.html) cuts down on false alarms. We do not sell off-the-shelf packages: after a needs analysis, we set out scope, phases and fees in a written proposal.

## Two-way visibility with Smart360 and SmartMail

DMARC reports show how other people's servers treat your mail. **[SmartMail](https://digitalbridge.com.tr/en/smart360/smartmail.html)**, the business email product in Digital Bridge's [Smart360](https://digitalbridge.com.tr/en/smart360.html) family, makes those reports readable and also handles the other half: how you treat incoming mail.

- **Domains and DNS in one panel:** Domains and DNS settings are managed from the Smart360 admin panel alongside users and departments, so fixing a gap a report reveals does not mean switching tools.
- **Reports in readable form:** For domains on SmartMail, DMARC reports arrive at SmartMail's own collector address, are opened automatically, converted into a readable format and archived month by month. You do not have to unpack raw XML attachments by hand for step two of the seven-step method, and the Smart360 team prepares and verifies the MX, SPF, DKIM and DMARC records, along with the recommended MTA-STS and TLS-RPT records.
- **The same logic on inbound mail:** SmartMail puts every incoming message through identity, structure and content checks; on the identity side it calculates SPF/DKIM/DMARC and PTR results itself rather than trusting a result written by another server along the way. Lookalike domains, display-name impersonation and Reply-To mismatches are weighed too, so a message that passes DMARC from a domain resembling yours is still flagged. The outcome is a report with written reasons.

In SmartMail, authentication and domain checks run in software, so they keep working even when the AI usage allowance runs out. Product details are on SmartMail.com.tr; to buy SmartMail, use the [Smart360 purchase page](https://smart360.com.tr/satin-al?urun=smartmail). For user-side warning signs, see [how to spot phishing emails](https://digitalbridge.com.tr/en/blog/how-to-spot-phishing-emails.html).

## Your next step

Collect the last month of DMARC reports sent to your `rua` address and work through the first three steps of the seven-step method; the shorter your list of unknown sources, the easier the reject decision becomes. If you are configuring a domain from scratch, [setting up email with your domain](https://digitalbridge.com.tr/en/blog/set-up-email-with-your-domain.html) shows the right order, and if you are re-evaluating your provider, read [how to choose business email](https://digitalbridge.com.tr/en/blog/business-email-how-to-choose.html). To parse your reports together and draw up a p=reject timeline, [get in touch](https://digitalbridge.com.tr/en/contact.html). More on this subject is collected in our [Business Email & Documents hub](https://digitalbridge.com.tr/en/blog/topic/kurumsal-eposta.html).

## Frequently Asked Questions

### How often do DMARC reports arrive?

Aggregate (rua) reports usually arrive once a day, as a separate email attachment from each reporting provider. You can request a different interval with the ri tag in your DMARC record, but the standard's default is 86400 seconds, or one day, and most providers stick to it. Low-volume domains may get no report from some providers at all, which can simply mean no mail was sent to them.

### What does disposition=none mean in a DMARC report?

disposition=none means the receiving server applied no action to the message under your DMARC policy. Seeing it on every row is normal while your policy is p=none, so even mail that failed DMARC may have been delivered. quarantine means the message was set aside as suspicious, and reject means it was refused. A reason of forwarded or mailing_list shows the receiver deliberately relaxed your policy.

### Why does my report show SPF pass but DMARC fail?

Because DMARC looks at alignment, not the raw result. SPF may have passed for the domain in the envelope sender, but if that domain does not align with the domain in your visible From address, SPF counts as a failure for DMARC. This usually happens when a sending service uses its own domain, and a custom-domain setting fixes it.

### My report shows IP addresses I do not recognise. Has my domain been hacked?

Probably not. Nobody needs access to your server to send mail in your name; they only need to type your address into the From line. Such messages cannot pass SPF or DKIM in alignment with your domain, so they appear as fail in your reports. It is still good practice to review account passwords and who can access your DNS management. Once you move to a p=reject policy, receiving servers will refuse them.

### When should I move to p=reject?

When several weeks of reports show that nearly all of your legitimate senders pass in alignment, and the remaining failures come from sources you do not recognise. Start with p=quarantine, phased with the pct tag if needed. Keep reading the reports after the switch, because new tools and suppliers add new senders.

### Should I turn on forensic (ruf) reports?

They can help you inspect individual failing messages, but many large providers do not send them for privacy reasons. Those that arrive may contain personal data such as headers and addresses. If you enable them, route them to a mailbox with restricted access and set a retention period.

### Do I need a DMARC report analyser, and what drives the cost?

For a couple of domains with few senders, parsing reports into a spreadsheet may be enough. As domains, senders and report volume grow, an analysis tool that merges reports automatically, maps IPs to senders and raises alerts saves real time. Cost depends on the number of domains, monthly mail volume, data retention period and how much consultancy support you need.
