Analyst at a desk working out how to read DMARC reports on a monitor

How to Read DMARC Reports (RUA and RUF) and What to Fix First

If you want to know how to read DMARC reports, start with the aggregate (RUA) files. Each XML attachment is a summary from one receiving mail server showing which sources sent mail as your domain and whether those messages passed DMARC. RUF reports are different: they’re per-message failure reports, and many providers don’t send them. What to fix first is almost always the same: get your own legitimate senders passing and aligned, then deal with anything you don’t recognize.

Those attachments pile up quickly because, according to Google, every receiving server that gets your mail sends its own report, usually once a day, when your DMARC record includes a rua address. The XML looks intimidating, but it follows a fixed layout that the current standard, RFC 9990, defines as report metadata, your published policy, and one record per sending source. Failure reports exist to help diagnose the failures you spot in aggregate data and to reveal abuse of your domain. Don’t be surprised if your ruf mailbox stays empty, though. Gmail doesn’t support ruf at all.

This guide covers where the reports land and how to open them, then walks through an aggregate report field by field. It shows you how to sort every sending source into three buckets and gives you a practical order for fixes. It also explains when RUF reports are worth having, and how to tell from your data when it’s safe to move your policy from monitoring to quarantine or reject.

The short answer: what DMARC reports are and RUA vs RUF

DMARC reports come in two kinds. An RUA (aggregate) report is a summary of all the mail that claimed to come from your domain over a period of time. An RUF (failure) report describes a single message that failed DMARC. Start with RUA reports. They are the ones you will actually receive, and they show the whole picture.

RUA: the summary report

Aggregate reports are XML files. Receiving mail servers send them to the address you list in the rua tag of your DMARC record. The current standard for their structure and delivery is RFC 9990, the DMARC aggregate reporting specification.

Google’s guide to DMARC reports makes three practical points:

  • Reports usually arrive once a day.
  • If rua is set, every server that receives your mail sends its own report.
  • The most important thing to check in any report is whether mail from your domain passes DMARC.

RUF: the single-message report

Failure reports cover individual messages that failed DMARC. They are defined in RFC 9991, the DMARC failure reporting specification. Their job is to help you work out why a failure in your aggregate data happened and to spot abuse of your domain. You may also see them called forensic reports.

Why RUA comes first

According to Google’s DMARC setup instructions, Gmail does not support ruf. Gmail handles a large share of most senders’ recipients, so failure reports will usually be patchy or missing. For most senders, aggregate reports will be the main source of information about who is sending as your domain.

Report DMARC tag What it covers Defined in
Aggregate rua Summary of all mail claiming your domain RFC 9990
Failure (forensic) ruf One message that failed DMARC RFC 9991

Where the reports land and how to open them

Your reports go to whatever address is listed after rua= in your DMARC record. To find it, look up the TXT record at _dmarc.yourdomain.com using your DNS host’s dashboard or any DNS lookup tool. A record such as v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com means that mailbox receives the aggregate reports.

If you are setting this up fresh or the address points to someone’s personal inbox, change it. Google recommends a dedicated group or mailbox for DMARC reports. Google also notes that when the report address is on a different domain, that domain has to publish its own DNS record allowing it to receive your reports. This step is easy to miss and is a common reason reports never show up. The updated aggregate reporting standard describes how these external destinations are verified and lays out the report’s XML structure: a feedback wrapper containing report_metadata, policy_published and one or more record entries.

Once reports start arriving, expect a steady flow. According to Google’s overview of DMARC reports, reports are usually sent once a day, and every receiving server that handles your mail sends its own report. Each one is a raw XML file with metadata and records. The key information inside is whether your messages passed DMARC. Google recommends using a third-party service to store and analyze them. Opening dozens of XML attachments by hand gets old fast, and a parser makes patterns visible at a glance.

A quick refresher before you start reading: DMARC passes only when SPF or DKIM passes and the domain they checked lines up with the domain in the visible From address. That match is called alignment. It can be relaxed, where subdomains count, or strict, where the domains must match exactly. If you want the fuller picture, here is what SPF, DKIM and DMARC each actually do.

Reading a DMARC aggregate report field by field

An aggregate report looks dense, but only a few fields drive your decisions. The structure is defined in RFC 9990, the current DMARC aggregate reporting standard. Everything sits inside a feedback root element, which has three parts.

Section What it tells you
report_metadata Who sent the report and the date range it covers
policy_published The DMARC record the receiver found in your DNS
record (repeated) One entry for each group of messages the receiver saw

Inside each record

  • Source IP and count: the server that sent the mail and how many messages came from it.
  • policy_evaluated: the disposition the receiver applied, plus the DMARC result for DKIM and for SPF.
  • identifiers: the header From domain, which is the address your recipients actually see.
  • auth_results: the raw SPF and DKIM checks, showing which domain was tested and whether it passed.

The distinction that matters most

The raw checks in auth_results can pass while the DMARC result in policy_evaluated still fails. This happens when the domain that passed SPF or DKIM is not aligned with your header From domain. A typical case is a third-party platform that signs with its own domain instead of yours. When you see a raw pass next to a DMARC fail, you are looking at an alignment problem, not a broken record.

What changed in the newer schema

  • The pct field is gone from the published policy.
  • A new np field shows the policy for non-existent subdomains.
  • The DKIM selector is now required in auth_results, which makes it easier to see which key signed each message.
  • A policy_test_mode override reason has been added.

Some receivers may still send the older format. Read reports tolerantly, and don’t treat a missing new field or an extra old one as an error.

Hands at a laptop reviewing a DMARC aggregate report

Sort every sending source into three buckets

Before you change a single DNS record, sort every sending source in your reports into one of three buckets. This step is simple, and it keeps you from fixing the wrong thing first. Google notes that the key information in these reports is whether messages pass DMARC, so that question drives the sort.

Bucket What it looks like What to do
1. Yours, passing Your known senders, with SPF or DKIM passing and aligned Nothing. Leave them alone.
2. Yours, failing Your email platform, CRM, help desk or billing system failing DMARC Fix these first. This is real mail your customers expect.
3. Unknown IP addresses you don’t recognize Investigate. It could be spoofing, forwarding, or a tool someone set up and forgot.

Let volume set the order

Group your rows by source IP, then sort by message count. Your largest legitimate failures will rise to the top of Bucket 2, and those are where a fix does the most good. A failing billing system that sends thousands of invoices matters more than a test server that sent a handful.

When a known sender lands in Bucket 2, the cause is often alignment. The domain that sender authenticates with doesn’t match your visible From domain closely enough. Google explains how alignment works and how the aspf and adkim modes control it, which helps you see whether a strict setting is the cause.

Be patient with Bucket 3. Before you treat an unfamiliar IP as an attacker, check with your team. Marketing or support may have connected a new service without telling anyone.

What a pass does and doesn’t tell you

A DMARC pass confirms that a sender is authorized to use your domain. It doesn’t promise inbox placement, and it says nothing about your sender reputation. If your mail authenticates cleanly but still lands in spam, the next step is checking your domain reputation without a Gmail score.

What to fix first: a priority order

Start with the legitimate mail you send in the largest volumes, then work down to the edge cases. Each record in an aggregate report pairs a sending source with its SPF and DKIM results, so you can rank problems by message count and fix them in this order:

  1. High-volume legitimate senders failing DMARC. If your email platform, CRM or help desk shows up with heavy volume and a DMARC fail, turn on DKIM signing with your own domain inside each platform. This usually rescues the most mail for the least effort.
  2. DKIM passing for the platform’s domain, not yours. A DKIM pass signed with the vendor’s domain doesn’t help DMARC unless it aligns with your From domain. Fix the alignment by publishing the vendor’s DKIM key under your domain so its signatures carry your name.
  3. SPF passing only for the bounce domain. When SPF passes for the platform’s return-path domain, set a custom return-path on your domain if the platform offers one. If it doesn’t, aligned DKIM alone is enough for DMARC to pass.
  4. Your own aspf and adkim settings. Before blaming a vendor, check whether your record uses strict or relaxed alignment. Google explains that strict mode requires an exact domain match, while relaxed mode also accepts subdomains. A strict setting can make correctly configured subdomain mail fail.
  5. Forwarding and mailing-list failures. Treat these as lower priority. Forwarders and lists relay or modify your messages on servers you don’t control, so there is often little you can change on your end.
  6. Unknown sources. Confirm they are truly unauthorized before tightening your policy. A forgotten billing tool or a team’s newsletter account can look like spoofing until someone recognizes it.

For the exact DNS records behind each of these fixes, follow our step-by-step SPF, DKIM and DMARC setup for high-volume senders. If you’d rather have someone work through the list with you, you can book a free consult.

Team planning which DMARC alignment failures to fix first

RUF failure reports: when they help and why you may never see one

RUF reports are per-message failure reports. Many domain owners never receive one, and that is normal. Your aggregate (RUA) reports are still where most of the useful work happens.

Under RFC 9991, the DMARC failure reporting standard, a failure report describes a single message that failed DMARC. Aggregate reports show patterns across many messages. Failure reports zoom in on one message, so you can work out why a specific source is failing and spot abuse of your domain.

Tag What you get Best used for
rua Summaries of many messages Finding every source that sends as your domain
ruf Details on one failed message Diagnosing a specific failure or investigating spoofing

Treat the ruf mailbox as sensitive

Failure reports can include parts of the original message, sometimes including personal information about the sender or recipient. The standard addresses this directly in its privacy considerations. Whoever can open that mailbox can read fragments of real email, so limit access and decide in advance how long you will keep reports.

How delivery works

  • If you list several ruf addresses, report generators are expected to try each one.
  • If an address sits on a different domain than the one being reported on, that external destination must be verified before reports go there.

Why your inbox may stay empty

Not every mailbox provider sends failure reports. Google states plainly that Gmail doesn’t support the ruf tag, and it notes that these reports are also called forensic reports. If much of your audience uses Gmail, a quiet ruf mailbox tells you nothing about your authentication health.

Add a ruf address only if you have a secure place to receive and process these reports. If you don’t, leaving it out costs you little. Your RUA data will still show which sources are failing.

When the reports say you’re ready to tighten your policy

Your reports show you’re ready when every legitimate sending source passes DMARC with alignment, consistently, and the only failures left are mail you don’t recognize. Until you reach that point, leave your policy at p=none.

Google recommends starting at p=none and then moving to quarantine or reject as you learn how your mail authenticates. Because aggregate reports usually arrive once a day from each receiving server, one clean report isn’t enough. Wait for several reporting days of clean results before each step. That gives occasional senders, like a billing system or an event tool, a chance to appear in the data.

A quick readiness check

  • Every source you own or use is identified. Nothing in the “legitimate” bucket is still failing.
  • Passes are aligned. SPF or DKIM passes for your domain, not just for a vendor’s domain.
  • Results hold across several days. A single good day can hide a sender that only mails weekly.
  • Remaining failures are spoofing or unknown. These are exactly what quarantine and reject are meant to stop.

Keep reading after enforcement

Moving to reject is not the end of monitoring. Teams add new tools, vendors change their sending setups, and spoofers keep testing your domain. With an enforced policy, a new platform that someone forgot to authenticate can quietly lose mail. A quick weekly look at your reports catches that before customers notice.

If you send in volume, compare your setup against our plain-English Gmail and Yahoo bulk sender checklist. If authentication looks right but mail still isn’t landing where it should, an email deliverability audit can show what else is going on.

If your reports are hard to interpret, or you’re unsure whether a source is safe to block, you can book a free consult and we’ll go through them with you.

Keep researching on Digital Bulldogs

Frequently asked questions

How often are DMARC aggregate reports sent?

Usually once a day. According to Google’s overview of DMARC reports, every receiving server that gets mail claiming to be from your domain sends its own report when your record includes an rua address. If several mailbox providers handle your mail, expect several separate reports each day. Busy domains can collect a large stack of files quickly.

What is the difference between DMARC rua and ruf?

The rua tag tells receivers where to send aggregate reports. These are XML summaries that group your traffic by sending source and show pass and fail results. The structure of those summaries is defined in RFC 9990, the current aggregate reporting standard, which replaces RFC 7489. The ruf tag requests failure reports instead. These are per-message reports about individual emails that failed DMARC.

The two work best together. Aggregate reports show the overall pattern, and failure reports, when you receive them, add detail on specific messages.

Why am I not getting any failure (RUF) reports from Gmail?

Gmail doesn’t send them. Google’s DMARC setup guide states that Gmail doesn’t support the ruf tag, which means failure reports (also called forensic reports) won’t come from Gmail even if your record asks for them. Your rua aggregate reports from Google should still arrive normally. For most domains, those aggregate reports carry the information you need to act on.

Can I send DMARC reports to an address on a different domain?

Yes, but the other domain has to agree to receive them. Google’s setup guide, linked above, notes that a DNS record is needed when your report address sits on another domain. This applies when you send reports to an analysis service or to a parent company’s mailbox.

Under the current standard, receivers check for that permission before delivering to an external destination. If the record is missing, your reports may never arrive.

Do DMARC failure reports contain personal information?

They can. Failure reports describe individual messages, so they may include details such as addresses and message content. RFC 9991, which defines DMARC failure reporting, includes a section on the privacy considerations this raises. Send ruf reports only to a mailbox you control or to a provider you trust, and limit who on your team can open them.

If you’d like help deciding whether failure reports are worth enabling for your domain, you can book a free consult with Digital Bulldogs.

Sources

  1. RFC 9990: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting · IETF / RFC Editor · 2026-05-20
  2. RFC 9991: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting · IETF / RFC Editor · 2026-05-20
  3. About DMARC reports · Google Workspace Admin Help
  4. Set up DMARC · Google Workspace Admin Help

This article is general information, not legal advice. Laws and deadlines vary by state and change over time; check the linked sources or speak with a licensed attorney about your situation.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *