# No DMARC reports requested

Nobody sends you DMARC reports, because your record doesn't ask for them: its `rua=` tag is missing, or it has nothing after the `=`. Without reports you can't see which services send as your domain, which of them fail, or who is pretending to be you.

An aggregate report is one summary a day from each receiver that takes part. It lists each server that sent mail as your domain and whether that mail passed SPF, DKIM and DMARC. RFC 9989 section 4.7 says that when `rua` is missing, receivers "MUST NOT generate aggregate feedback reports for the domain" ([the section](https://www.rfc-editor.org/rfc/rfc9989.html#section-4.7)).

Without them, moving from `p=none` to `quarantine` or `reject` is a guess: a service you forgot stops delivering, and you hear about it from your customers. [Yahoo's rules for bulk senders](https://senders.yahooinc.com/best-practices/) (no date on the page; read 14 Nov 2026) call a working report address "strongly recommended".

On the result:

```
No DMARC reports requested
You won't learn which services send as you or which of them fail.
```

## Ask for reports

1. Pick an address that can take many small emails with attachments, such as `dmarc-reports@example.com`, or a DMARC service's address.
2. Read the record: open **Details →** on your result, or run `dig +short TXT _dmarc.example.com` with your domain in place of `example.com`.
3. At your DNS provider, edit the TXT record at `_dmarc.` in front of the domain you checked. Many DNS providers want only the part before your main domain: `_dmarc` for `example.com`, `_dmarc.mail` for `mail.example.com`. If it has an empty `rua=`, fill that one in: `rua=mailto:dmarc-reports@example.com`. If it has none, add the tag at the end. If the record has no `p=`, add `p=none;` after `v=DMARC1;` in the same edit. A report address alone can put a record receivers ignore today into force, and with it any `sp=` or `np=` set to `quarantine` or `reject`. Set those to `none` too unless you've checked your subdomains' mail. [DMARC has no policy](/docs/findings/dmarc-policy-missing/) explains why. Save the record. Never add a second `rua=`: a tag written twice makes receivers [ignore the whole record](/docs/findings/dmarc-record-ignored/).
4. If the address is at another domain, that domain must allow it, or receivers send nothing. A DMARC service does this for you. For a domain of your own, add a TXT record to the report address's domain. Its name is the domain you checked, then `._report._dmarc.`, then the report address's domain. For reports about `example.com` sent to `reports@example.net`, that is `example.com._report._dmarc.example.net`, with the value `v=DMARC1`. In the DNS zone of `example.net`, many providers want only `example.com._report._dmarc` ([RFC 9990 section 4](https://www.rfc-editor.org/rfc/rfc9990.html#section-4)). Check it with `dig +short TXT example.com._report._dmarc.example.net`; it should print `"v=DMARC1"`.

[Connect DMARC reports](/docs/connect-reports/) sends them to MailGlo, which reads each report and lists each service that sends as you and whether it passes.

You'll know it worked when the first reports arrive, usually a day or two after you publish the change.
