Skip to content
AdminKit

DMARC aggregate report (RUA)

What is DMARC aggregate report (RUA)?

A DMARC aggregate report (RUA) is the periodic XML summary mail receivers send to the address a domain's DMARC record names in its rua tag, listing SPF and DKIM results for mail claiming that domain, broken down by sending source. AdminKit's guide to reading these reports covers the staged rollout decisions they're meant to inform.

By AdminKit team, Netbase JSC · Updated

A DMARC aggregate report (RUA) is the machine-readable report a receiving mail server generates about the mail it saw claiming to come from a domain — volume, source IPs, and whether each message passed SPF and DKIM — and sends to the address the domain names in DMARC’s rua tag. Its XML schema is defined in RFC 9990, delivered as a gzip-compressed attachment; RFC 9989, the current core DMARC specification (tracked on the IETF Datatracker alongside its working-group history), recommends receivers send one at least every 24 hours. Unlike the raw DMARC policy record, which only sets what happens to failing mail, an aggregate report shows a domain owner which legitimate sending sources would actually fail before they move to enforcement — the same feedback loop NIST’s trustworthy-email guidance recommends domains rely on before tightening a DMARC policy. A separate, optional forensic report (RUF) covers individual failing messages but has far thinner receiver support. Its format and privacy limits are covered under DMARC failure report (RUF). Raw RUA XML is rarely read by hand; most domains feed it into a parsing dashboard instead. Google Workspace’s guide to DMARC reports recommends always using reports when turning on DMARC and lists what they show: which servers or third-party senders send mail for the domain, what percentage of its messages pass DMARC, and what action receiving servers take on its unauthenticated messages.

DMARC aggregate report (RUA) is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

How often should a receiver send a DMARC aggregate report?

RFC 9989, the current core DMARC specification, recommends receivers send one at least every 24 hours, though some send more often.

What does a DMARC aggregate report show that the DMARC policy record doesn't?

The policy record only sets what happens to failing mail; an aggregate report shows which legitimate sending sources would actually fail before a domain owner moves to enforcement.

What's the difference between an aggregate report (RUA) and a forensic report (RUF)?

RUA summarizes volume and SPF/DKIM results across all mail seen; RUF covers individual failing messages but has far thinner receiver support, so most domains rely on RUA.

Is raw DMARC aggregate report XML meant to be read by hand?

Rarely -- the reports arrive gzip-compressed per RFC 9990's schema, and most domains feed them into a parsing dashboard rather than opening the XML directly.