The rua mailbox is empty
An empty rua mailbox usually means one of four things: the rua address is missing, mistyped, or lacks mailto:; the address is on another domain that hasn't authorized your reports; the mailbox is rejecting or filtering them; or you haven't waited a full reporting day. Some silence is also normal, because not every receiver sends reports. Work through the checks below in order. They start with the quickest. Each reason is explained in more depth in Why DMARC reports do not arrive.
The checklist
1. Is there exactly one DMARC record, and does it ask for reports?
Look it up from outside your network:
dig +short TXT _dmarc.example.com
You want exactly one answer starting with v=DMARC1 and containing rua=. If there are two DMARC records at that name, receivers discard them all. The DNS tree walk may still find a record higher in the tree (Why DMARC reports do not arrive). If there's no rua, receivers must not generate aggregate feedback reports. Setting up the record is covered in our DMARC setup guide and DMARC record explained: syntax, tags and examples.
2. Is the address written as a mailto: URI?
rua=mailto:dmarc-reports@example.com works. rua=dmarc-reports@example.com doesn't. The address must include mailto:. Malformed addresses are ignored, so a typo gives you silence, not an error. The full syntax is in rua, ruf, and report authorization.
3. Is the mailbox on a different domain? Check the authorization record
If reports go to an address in another organizational domain, even one you own, the destination must publish a TXT record saying it accepts your reports. Otherwise receivers ignore that address. For reports about example.com sent to reports@reports.example.net:
dig +short TXT example.com._report._dmarc.reports.example.net
It should return v=DMARC1. The destination host is the host part of the mailto: address, so here it's reports.example.net, not example.net. A wildcard, *._report._dmarc.reports.example.net, also works. If you use a reporting provider, ask exactly what it publishes.
4. Can the mailbox actually receive reports?
Send a test message to the report address from an outside account. Then check:
- The address exists and accepts mail from external senders. Some groups and shared mailboxes accept only internal senders.
- Your gateway or spam filter isn't quarantining XML or gzip attachments.
- The mailbox isn't full, and size limits won't block large reports.
If delivery fails, the receiver may cache that data and try again later, or may discard it. Reports lost this way may never come back.
5. Have you waited a full day of normal sending?
Reports usually cover a full UTC day and are sent after it ends. There's no published delay to quote. If you published rua this morning, an empty mailbox tonight is expected.
6. Is the mail coming from a subdomain with its own record?
A subdomain that publishes its own DMARC record gets its own reports, at its own rua. If that record has no rua, there are no reports for it, and the parent's mailbox won't see them either (Subdomain policy is not doing what we expected).
7. Is the silence coming from the receivers?
None of these are problems on your side:
- Reporting is optional. Receivers should send reports, but resource limits, policy, and privacy are reasons some don't.
- Microsoft 365 sends aggregate reports only "as long as the MX record for the Microsoft 365 domain points directly to Microsoft 365". Recipients behind a third-party gateway won't generate them (Microsoft 365 or Google Workspace setup issues).
- Low volume. Reports describe mail a receiver actually got. The number of reports "depends on" how much mail you send.
- Early rejections. Mail rejected on an SPF hard fail before DMARC is evaluated will never appear in aggregate DMARC reports.
8. Is it the ruf mailbox that's empty?
That's normal. Gmail doesn't support ruf, Microsoft 365 doesn't send failure reports, and many large providers don't send them (Aggregate (RUA) vs forensic (RUF) reports).
When the mailbox is only partly empty
| Pattern | Likely reason |
|---|---|
| Reports from Google, none from Microsoft | Your recipients' Microsoft 365 tenants route MX through gateways, or you send little to Microsoft 365 |
| Reports for the parent domain, none for one subdomain | That subdomain has its own record without rua (check 6) |
| Reports stopped after a DNS change | A second DMARC record, a broken mailto:, or a removed authorization record at the destination (checks 1–3) |
| Reports stopped after a mailbox change | New filtering, an internal-only group, or a full mailbox (check 4) |
Mistakes worth avoiding
- Writing
rua=withoutmailto:. - Expecting your own domain to publish the
_report._dmarcrecord. The destination publishes it. - Pointing reports at another domain you own without the authorization record there.
- Checking the same day you publish.
- Reading an empty mailbox as "nobody is spoofing us." It may only mean nobody is reporting.
Once reports arrive, A field-by-field walk-through of a DMARC aggregate report walks through what's in them.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
I added rua yesterday and the mailbox is empty. Is it broken?
Probably not. Wait a full UTC day of normal sending, then run the checklist.
My reports go to a provider on another domain. What's needed?
The provider must publish <your-domain>._report._dmarc.<provider-host> as a TXT record containing v=DMARC1.
I get Google reports but not Microsoft's. Why?
Microsoft 365 sends reports only for recipient domains whose MX points directly to Microsoft 365.
Why is my ruf mailbox always empty?
Gmail and Microsoft 365 don't send failure reports, and many other large receivers don't either.