Topic · Authentication
DMARC ruf tag
The DMARC ruf tag identifies a destination for failure reports that some receivers may send for individual messages.
How it works
Unlike aggregate reporting, failure reporting can contain message-level information; many receivers restrict or omit it.
What can go wrong
Assuming every receiver sends ruf data can create blind spots; retained samples may expose personal information.
What to check or do
Treat ruf as optional, validate privacy handling and rely on aggregate reporting for broad visibility.
How to investigate DMARC ruf tag
- Signal to investigate
- An administrator expects every DMARC failure to arrive as a detailed forensic email.
- Evidence to collect
- Inspect ruf URI syntax, receiver reporting support, recipient authorization and actual RFC 9991 report availability.
- Common wrong conclusion
- Failure reports are optional and may be restricted for privacy, operational or abuse reasons.
How to interpret the evidence
Aggregate XML (rua) and individual failure reporting (ruf) are separate workflows. Failure reports can contain sensitive or partially redacted content and should not be treated as a complete incident log.
What to change and how to verify it
Protect report destinations, document retention and access controls, and rely on aggregate reporting plus mailbox logs for broader coverage.
Put this into practice
Run a focused check, then explore protection if your domain needs it.