Opens in a new tab

DMARC external report authorisation: the _report._dmarc record

When your rua= address is on another domain — a reporting service, a parent company — receivers first check that the other domain agreed to receive your reports. Without that record, they drop the reports without telling you.

Syntax<your domain>._report._dmarc.<their domain> TXT "v=DMARC1"
Published byThe domain receiving the reports
RecordTXT at <your domain>._report._dmarc.<their domain>, containing v=DMARC1
Without itReports are not sent
Defined inRFC 9990

What it does

Without the check, anyone could publish a DMARC record pointing reports at a victim’s mailbox and flood it. So a receiver takes the domain of the report address, prepends your domain and _report._dmarc, and looks for a TXT record there starting v=DMARC1.

Reporting services publish a wildcard (*._report._dmarc.<their domain>) so every customer is authorised at once; for your own second domain you publish the record yourself.

Examples

example.com._report._dmarc.reports.example.net. TXT "v=DMARC1"

reports.example.net agrees to receive example.com’s reports.

See what your own DMARC record says

Every term of your published record, read and explained — including this one.

Common mistakes

  • Pointing rua at a mailbox on another of your own domains and never publishing the authorisation — the reports never arrive.

What we recommend

Our DMARC checker tests every external report address in your record for this authorisation.

Check your report addresses are authorised →

Sources

Checked on 25 September 2026 against these official sources:

Know when your records change

Add your domain and we monitor its SPF, DKIM and DMARC every day, read the DMARC reports receivers send you, and email you when a record changes or a sender starts failing. Free for your first domain.

Create a free account