DMARC Forensic Reports (ruf) (DMARC Forensic Reports)
The Importance of DMARC Forensic Reports
Forensic reports provide granular detail about DMARC failures that aggregate reports do not. While an aggregate report tells you that 50 emails from a certain IP failed DMARC, a forensic report shows the actual headers of those messages - revealing what the From, Return-Path, and Subject were, and exactly which authentication checks failed.
This detail is valuable for diagnosing authentication problems. If a legitimate email service is failing DMARC, forensic reports show exactly which messages are affected and why. They also help identify targeted phishing campaigns by showing the content of spoofed messages.
However, forensic reports have significant limitations. Many major email providers (including Google) do not send them due to privacy concerns - the reports can contain personal data from email headers and content. Microsoft sends redacted forensic reports. Because of this inconsistency, aggregate reports (rua) are the primary source of DMARC data, and forensic reports (ruf) are a supplementary tool.
Testing Your Configuration
Add a ruf tag to your DMARC record: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; ruf=mailto:dmarc-forensic@yourdomain.com. Note that many receivers will not send forensic reports regardless of this configuration.