Skip to content
DMARC Pulse

Email errors

DMARC reports not received: causes and how to fix it

DMARC reports not received? Check the rua tag, the _report._dmarc record for outside addresses, the mailbox and whether the receiver sends reports.

What this means

DMARC reports not received? The causes are few: a wrong or missing rua tag (the reporting address in your DMARC record), an outside address without permission, a mailbox that cannot take the report, too little time, or a receiver that sends none. An aggregate report is an XML summary, usually daily, of the mail a receiving server (the receiver) saw using your domain.

If a lookup finds no record at all, see no DMARC record found. Missing failure reports from the ruf tag are expected. Receivers may skip them, Gmail does not support the tag and Microsoft 365 does not send them.

Why it happens

  • No rua tag. Without it, receivers must not generate aggregate reports. A subdomain with its own DMARC record needs its own rua.
  • Two records at one name. Receivers discard them all.
  • A malformed address. rua takes a URI, so dmarc@example.com without mailto: is malformed and receivers should ignore it.
  • An outside address without permission. An address outside your Organizational Domain (usually the domain you registered) needs a permission record at the destination. Without one, receivers must ignore it.
  • A mailbox that cannot take them. If delivery fails, the receiver may retry later or discard the report. A report can also exceed an attachment size limit.
  • Too little time or traffic. A report typically covers one UTC day and needs at least one record element, so a receiver that saw none of your mail sends nothing.
  • The receiver does not report. RFC 9989 does not oblige receivers to send reports. Microsoft 365 sends none when the recipient's mail reaches another service first.

How to fix it

  1. Read your record on a public DNS server. For a subdomain with no record of its own, query its Organizational Domain (usually the domain you registered). Its reports arrive under that domain's name.

    nslookup -type=TXT _dmarc.example.com 1.1.1.1

    If two answers begin with v=DMARC1, merge them into one record and delete the other. If rua is missing or lacks mailto:, correct it in that record:

    TXT
    v=DMARC1; p=none; rua=mailto:dmarc@example.com

    Caution: edit the existing record, because a second one makes receivers discard both. p=none is only a sample. If the record works today, change only rua and keep p and every other tag, such as sp and t, exactly as they are. Repairing a broken or duplicated record with quarantine or reject in p or sp enforces that policy as soon as receivers read it. In that case, publish p=none first without sp and tighten it after reviewing reports.

  2. An address under the same registered domain as the record, such as dmarc@reports.example.com, needs no permission, so go to step 4.

  3. For an outside address, query the permission record. Its name is the domain that publishes your DMARC record, then _report._dmarc, then the full host after @. For rua=mailto:dmarc@reports.example.net on example.com:

    nslookup -type=TXT example.com._report._dmarc.reports.example.net 1.1.1.1

    You want a TXT answer (a text entry in DNS) that begins with v=DMARC1. If none appears, the destination's owner must publish it, so ask your reporting service. If you run that domain, add this value at that name and check the saved name, because some DNS hosts add the zone automatically:

    TXT
    v=DMARC1;
  4. Send a normal message to the rua address from an outside account. If it bounces or vanishes, fix the mailbox or its routing first. A reporting service's address can discard ordinary mail, so ask the service instead. Then search the mailbox and spam folder for Report Domain:, which begins the subject line, and check that filters let compressed attachments through.

  5. Send mail and wait at least one full UTC day.

Confirm the fix

  1. Repeat the queries, or run the DMARC checker on the domain that publishes the record. It flags a missing rua, a malformed address, two records at one name and an outside address with no permission record.

  2. If a new permission record does not show up, DNS servers may hold the earlier empty answer until its cache time runs out. Query again later.

  3. Look for the first report.

  4. Silence from everyone after several days of steady mail to many outside recipients points back to your record or mailbox.

Check it now

Look up and validate a DMARC record

Frequently asked questions

How long do DMARC reports take to arrive?
No RFC sets an exact delay. RFC 9989 asks receivers to send reports at least every 24 hours, and RFC 9990 says a report typically covers one UTC day. Google and Microsoft both describe reports as normally daily. Allow at least one full UTC day after you publish or change rua. A receiver may pick up the change in a later period, so a fix made on Monday can first appear in the report for Tuesday. RFC 9989 removed the ri tag that used to request an interval between reports.
Where do I publish the _report._dmarc record?
In the DNS of the domain that receives the reports, published by that domain's owner. For reports about example.com sent to dmarc@reports.example.net, the TXT record goes at example.com._report._dmarc.reports.example.net with the value v=DMARC1;. A rua tag inside that record replaces your address and must keep the same host, or the receiver sends no report to either one. Failure-report (ruf) addresses on another domain go through the same check.
Do I need permission for an address on my own subdomain?
No. RFC 9990 runs the check only when the Organizational Domain of the record differs from that of the address, so dmarc@reports.example.com works for example.com without it. An address on a separate domain you also own still needs the record.
Does p=none stop DMARC reports?
No. The p tag says how to treat failing mail and the rua tag asks for reports. RFC 9989 describes p=none with a rua address as the usual way to start.
Why do only some providers send me reports?
Reporting is voluntary. RFC 9989 names resource constraints, local policy against sharing data and user privacy as the most common reasons to opt out. Microsoft 365 sends aggregate reports only when the recipient organization's MX record points directly to Microsoft 365, so mail routed first through a non-Microsoft service or an on-premises environment produces none. Microsoft says not all receivers send reports and puts typical coverage at 70 to 90% of total mail volume.
Can I list two addresses to find out which one fails?
Yes. Put both in rua, separated by a comma, each with mailto:. RFC 9990 requires receivers to attempt every remaining valid address, up to their own limits. If reports reach only one address, check the other one's permission record and mailbox. A receiver's limit on addresses can also explain it.

Sources consulted

RFC 9989 §4.7 (rua tag)
checked 2026-11-08
Google: About DMARC reports
checked 2026-11-08
Google: Set up DMARC
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.