Skip to content
  • There are no suggestions because the search field is empty.

Why DMARC reports do not arrive

If you're not receiving DMARC reports, the break is in one of four places: your DMARC record (no rua, a malformed address, or a broken record), the authorization an external report address needs, the mailbox the reports are sent to, or the receivers themselves, which don't all send reports. Some silence is normal. Reports usually cover a full UTC day, not every receiver sends them, and some mail never gets far enough to be counted. Check your side first, in the order below, before you conclude that nobody is reporting.

If your mailbox is empty right now and you want the short version, see The rua mailbox is empty.

1. Check your DMARC record first

  • No rua, no aggregate reports. If the tag is not provided, receivers must not generate aggregate feedback reports.
  • Missing mailto:. Each address needs the mailto: scheme: rua=mailto:dmarc-reports@example.com, not rua=dmarc-reports@example.com. The address must include mailto:. Malformed URIs should be ignored, so a typo means silence, not an error message.
  • Record not found or not valid. It must sit at _dmarc.example.com and start with v=DMARC1. If there are two DMARC records at that name, receivers discard them all, so the record you meant to publish, rua included, is ignored. The DNS Tree Walk may still find a record higher in the tree. This can happen when a vendor adds a second record. Setting up the record is covered in our DMARC setup guide and DMARC record explained: syntax, tags and examples.
  • The wrong place in the tree. A subdomain that publishes its own DMARC record gets its own reports, sent to its own rua. If that record has no rua, the parent's address won't receive that subdomain's data (Subdomain policy (sp), Subdomain policy is not doing what we expected).
  • DNS not visible yet. Query the record from outside your own network to confirm what receivers see.

The full rua syntax is in rua, ruf, and report authorization.

2. External addresses need authorization

If your rua (or ruf) address is in a different organizational domain from the one publishing the policy, receivers check that the destination agreed to receive your reports. Without that, anyone could point floods of reports at a victim's mailbox.

The check is a TXT lookup at:

<your-domain>._report._dmarc.<destination-host>

The destination host is the host part of the mailto: address, which may be a subdomain. The record must contain v=DMARC1. If it isn't there, the receiver must ignore that address. The same check applies to ruf.

Two details trip people up:

  • The destination publishes it, not you. For example, if your record is on shop.example and reports go to dmarc-reports@personal.example, the TXT record goes on the receiving side, at shop.example._report._dmarc.personal.example, with the value v=DMARC1;.
  • A wildcard is allowed. A destination willing to take reports for any domain can publish *._report._dmarc.example.com. If you use a reporting service, ask it exactly what it publishes.

This applies to your own domains too. Reports for example.com sent to reports@reports.example.net need a record at example.com._report._dmarc.reports.example.net (the host of the mailbox, not just example.net).

If you've seen a reference that points to the wrong place for this authorization check, the rule is the one above: the destination must publish the TXT record, or that address is ignored.

3. Check the mailbox

  • The address doesn't exist or bounces. If delivery fails, the receiver may cache that data and try again later, or may discard it. Lost reports may never be resent.
  • Size limits. Reports can be large, and uncompressed ones can exceed SMTP size limits.
  • Filtering. Report mail has to pass DMARC itself, but your gateway or spam filter may still quarantine XML or gzip attachments, or bulk mail from senders it doesn't know. Check quarantines and transport rules.
  • Groups that only accept internal senders. If reports go to a group or shared mailbox, check whether it accepts mail from external senders.

Google and Microsoft both recommend a dedicated mailbox or group rather than someone's own inbox. A quick test: send a message to the report address from an external account and see whether it lands.

4. Some silence comes from the receivers

None of these are problems on your side:

  • Not every receiver sends reports. Receivers should send them at least once every 24 hours. Resource limits, local policy, and privacy are common reasons for opting out. Yahoo strongly recommends a rua tag for monitoring, but doesn't describe Yahoo's own reporting.
  • Microsoft 365 has a condition. Microsoft 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 or with hybrid routing won't generate them (Microsoft 365 or Google Workspace setup issues).
  • Failure reports are rare. Gmail doesn't support ruf, and Microsoft 365 doesn't send failure reports. An empty ruf mailbox is normal (Aggregate (RUA) vs forensic (RUF) reports).
  • Timing. Reports usually cover one UTC day and are sent afterwards, so nothing arrives the same hour you publish. There's no published delay to quote. Allow at least a day or two of normal sending before you start troubleshooting.
  • No mail, no report. Reports describe mail a receiver actually got from your domain. A domain that sends little, or only to receivers that don't report, may get few reports or none.
  • Mail rejected early is never counted. Messages rejected early in the SMTP transaction, for example on an SPF -all hard fail, will never appear in aggregate DMARC reports. See Softfail vs fail (~all vs -all).

Quick check, in order

  1. Look up _dmarc.<your-domain>. There should be exactly one record, starting with v=DMARC1, with rua=mailto: spelled correctly.
  2. External address? Look up <your-domain>._report._dmarc.<destination-host> and confirm it returns v=DMARC1.
  3. Send a test message to the report address from an outside account. Check quarantines and group settings.
  4. Wait at least a full UTC day of normal sending.
  5. Getting reports from some providers but not others? Remember that Microsoft 365 recipients behind gateways don't send them, and that not all receivers report.
  6. Subdomains with their own record: check their rua too.

Mistakes worth avoiding

  • Writing rua=dmarc@example.com without mailto:.
  • Having two DMARC records after a vendor added its own.
  • Expecting the policy domain to publish the _report._dmarc record. The destination does.
  • Using a personal mailbox with aggressive filtering or a full quota.
  • Reading silence as safety. No reports doesn't mean no one is spoofing you. It may only mean no one is reporting.

Once reports are flowing, start with A field-by-field walk-through of a DMARC aggregate report to read them and How to inventory sending sources to turn them into a list of your senders.

Free DMARC account

Turn raw DMARC reports into a readable dashboard

Point your rua address to our platform and read the results by sender and source instead of opening XML files.

  • Results grouped by sending source
  • SPF, DKIM and alignment results per sender
  • The original XML reports are still there to download

Create a free DMARC accountTalk to an expert

FAQ

I published rua yesterday. Why is the mailbox empty?

Reports usually cover a full UTC day and are sent after it ends. Give it a day or two of normal sending, then work through the checks above.

My reports go to a DMARC provider. What do they need to publish?

A TXT record at <your-domain>._report._dmarc.<provider-host> containing v=DMARC1, or a wildcard *._report._dmarc.<provider-host>, where the host is the host part of the provider's report address. The provider publishes it, not you.

Why do I get Google reports but none from Microsoft?

Microsoft 365 only sends aggregate reports for recipient domains whose MX points directly to Microsoft 365.

Why do I never get ruf reports?

Many large receivers don't send them, and Gmail and Microsoft 365 don't.

Could a strict SPF hide failures from my reports?

Yes. Mail rejected early on an SPF hard fail never appears in aggregate reports.