Why you get DMARC reports every day, and where rua should point
Updated
If your DMARC record has a rua=mailto: address, that address gets mail every day from Google, Microsoft and mail systems you have never heard of, each with a small compressed attachment. Nothing is wrong. You asked for these reports when the record was published, often by a setup wizard. This guide explains who sends them, why there are so many, and which address they should go to.
What the reports are
Each one is a DMARC aggregate report: an XML file listing the IP addresses that sent mail with your domain in the From: header to that receiver, how many messages, and whether SPF, DKIM and DMARC passed. There is no message content and no recipient addresses in them. For the fields, see How to read DMARC aggregate reports.
They are not alerts. A report arrives whether everything passed or everything failed.
Who sends them
Every receiving mail system that supports DMARC reporting and saw mail claiming to be from your domain during the period. Google puts it this way: every mail server you send email to will send you a daily report. Microsoft 365 sends them too, typically once a day, when the receiving domain's MX points directly to Microsoft 365. Other mailbox providers, hosting companies and company mail gateways do the same.
Three things follow from that:
- One report per receiver per day. The reporting period is typically one UTC day, and each receiver sends its own file after the day ends. Some send more often.
- Spoofed mail counts. Reports cover all mail with your domain in From:, not only mail you sent. A domain that sends nothing still gets reports if someone else uses its name.
- Subdomains are included. Mail from
news.example.comis reported to the address in the record forexample.com, unless the subdomain has a DMARC record of its own.
Why they fill the inbox
The number of reports follows the number of receivers, not the number of messages. One newsletter to 2,000 customers at 150 different companies can produce dozens of reports the next day, and the same again after every send. Google says large organisations may get hundreds or even thousands of reports a day.
You cannot ask for fewer. The older DMARC specification had an interval tag (ri) for this. It is not among the tags in the current one, RFC 9989, and receivers send daily regardless. The real choice is between receiving the reports somewhere sensible and not receiving them:
- Removing
rua=stops the reports. It also removes the only way to see who sends as your domain, which you need before tightening the policy and after every change to your sending services. Lookproof explains what you lose under no aggregate report address. - Keeping
rua=and never opening the mail is the common outcome, and it is the same as having no reports.
The reports are meant for software. The specification says they are supposed to be processed automatically and are not human readable in bulk. One file can be read by hand. A month of them cannot.
Where rua should point
Not a person's mailbox
This is how most people meet the reports: the record was created with the administrator's own address in it. Google and Microsoft both advise against it. The reports bury other mail, and they stop being read when that person changes job.
A dedicated mailbox or group on your own domain
For example [email protected]. This is what Google and Microsoft recommend as a minimum, and it is enough for a small domain with a few sending services, if someone actually looks. Check three things:
- The address accepts mail from outside senders. Groups and shared mailboxes are often internal-only by default.
.gzand.zipattachments are not stripped or quarantined on the way in.- Someone owns it. Decide who looks, and how often. Once a week is fine while nothing changes; daily for the two weeks after you add a sending service or change the policy.
A reporting service
A service gives you an address on its domain, receives the files, and shows the totals per source over time. Google and Microsoft both suggest this when the volume is more than you can read. It is the practical choice once you get more than a handful of reports a day, or run several domains. The reports then go to a third party, so read what the service stores and for how long.
More than one address
rua takes a comma-separated list, each entry with its own mailto::
v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]
Receivers should send to every address, but each has its own limit on how many it will use, so keep the list to one or two. A list is useful when you move from one destination to another: publish both for a week, compare, then remove the old one.
A separate tag, ruf=, asks for a report per failed message. Gmail does not support it and Microsoft 365 does not send such reports, so leaving it out costs you little.
If the address is on another domain
When the rua address belongs to a different organisation's domain than the DMARC record, receivers first check that the destination has agreed to get your reports. They look for a TXT record on the destination's side:
example.com._report._dmarc.example.net. TXT "v=DMARC1"
Here example.com is your domain and example.net is where the reports go. If the record is missing, the receiver must ignore that address. There is no bounce and no error. The reports just never come.
In practice:
- Reporting services publish a wildcard record that covers all their customers, so there is nothing for you to do.
- Your own second domain is the usual trap. Reports for
example.orgsent to a mailbox atexample.comneed this record atexample.com, and nobody adds it. - Subdomains of the same domain need nothing. The check compares organisational domains, so
example.comcan report to[email protected].
Lookproof's page on DMARC rua to another domain has the exact record, how to check it and how to fix it. A rua value that receivers cannot use at all, such as an address without mailto:, fails the same silent way: see invalid report address.
After you change the address
- Expect the first reports at the new address after one to two days. Receivers report on a finished UTC day, and resolvers may hold the old record until its TTL runs out.
- Check that the large receivers you send to show up. If you send to Google Workspace or Gmail users daily and no report from Google arrives within a few days, the address is not accepting the mail or the external check above is failing.
- Keep the old address in the list until the new one has received reports, then remove it.
- Do not allowlist the report senders in your spam filter by name. Report mail must itself pass DMARC, so it should arrive without special rules.
Once the reports land somewhere you look, the next step is sorting what is in them: Why DMARC reports show sources you don’t recognise.
Senderward checks your domain's DMARC, SPF, DKIM, MX, MTA-STS and TLS-RPT every day and emails you, with the fix, when something gets worse. $7 per domain per month, 14 days free. See pricing