Your DMARC record asks for failure reports, and one arrives: a multipart email saying a message from your domain failed authentication. Somewhere in its fields are the answers — which check failed, for which domain, from which IP, and whether anything aligned with your From domain.
The AFRF Analyzer reads authentication failure reports in your browser and turns them into an SPF, DKIM and DMARC breakdown, explaining the failure only from what the report actually states.
What is AFRF?
In simple terms
An authentication failure report is a feedback report about a single message that failed SPF, DKIM or DMARC. It tells the domain owner what failed and includes the original message or its headers as evidence.
Technical background
RFC 6591 extends ARF (RFC 5965) with Feedback-Type auth-failure and fields such as Auth-Failure (adsp, bodyhash, revoked, signature, spf), DKIM-Domain, DKIM-Selector, DKIM-Identity, SPF-DNS and Delivery-Result. RFC 7489 adds the Auth-Failure value dmarc and the Identity-Alignment field for DMARC failure reports. Authentication-Results is required and should describe a single method.
Why use an AFRF analyzer?
Failure reports combine report fields, Authentication-Results syntax and original headers. The analyzer puts them side by side, shows which identity was evaluated and whether it aligned, and turns codes into plain explanations — so you can tell a missing SPF include from a mailing list that broke DKIM. It also validates the report itself, which helps when you generate failure reports or feed them into your own processing.
Who should use it?
Domain owners rolling out DMARC, email and security administrators reading ruf= reports, ESPs troubleshooting customer authentication, and developers producing or processing failure reports.
How the AFRF analyzer works
The report is parsed in your browser with the same engine as the ARF Report Analyzer. The RFC 6591 and RFC 7489 fields are combined with the reported Authentication-Results and the original message's DKIM-Signature headers. Failure scenarios are listed only with the evidence that supports them. Optional buttons check today's DKIM key or DMARC record through the DKIM Checker and DMARC Checker backends, sending only the domain and selector.
How to use the NetTools.tech AFRF Analyzer
- Save the failure report as .eml, or copy its full source.
- Open the AFRF Analyzer, paste or drop it, or load the example.
- Click Analyze Authentication Failure Report.
- Read the failure type, the scenarios and the SPF, DKIM and DMARC sections.
- Optionally check the current DKIM key or DMARC record, then export the analysis.
Understanding the results
The failure type section shows the Auth-Failure value, the Delivery-Result and the Identity-Alignment field. Scenarios such as "SPF fail", "DKIM body hash mismatch" or "Alignment failure" list their evidence. Items labelled "pattern" — forwarding or mailing lists — describe what the evidence is consistent with, not a stated cause. Every authentication result is marked as reported. Validation checks the report against RFC 5965, RFC 6591 and RFC 7489, separately from whether the reported results are correct.
Example: a mailing list breaks DKIM
A DMARC failure report shows Auth-Failure dmarc, Identity-Alignment none, SPF pass for lists.example and DKIM fail for sender.example, and the original headers carry a List-Id. The analyzer reports an alignment failure (SPF passed for the list's domain, not yours) and a pattern consistent with a mailing list modifying the message. The fix is not your SPF record — it is DKIM surviving the list, or the list using ARC.
Common use cases
- Reading DMARC failure reports while moving to p=reject.
- Finding a sending service that is missing from SPF.
- Spotting rotated or revoked DKIM keys.
- Recognising forwarding and mailing-list failures.
Troubleshooting
Auth-Failure is missing
The report is malformed; the analyzer shows everything else it contains.
No Authentication-Results in the report
Without them the analyzer can only explain the Auth-Failure type. Check the original headers section.
SPF failed for an unexpected domain
The envelope sender belongs to a forwarder or list, not to you. Look at Identity-Alignment.
DKIM key looks fine today
Keys change; the failure may have happened with an older key. Compare the selector in the report.
Common mistakes
- Adding forwarders' IPs to your SPF record.
- Treating reported results as verified.
- Assuming every failure report means spoofing.
- Ignoring Identity-Alignment when SPF or DKIM "passed".
- Requesting ruf= reports without a mailbox that can handle personal data.
Limitations
The analyzer explains what the report says and does not re-run authentication. Providers redact and format reports differently, and many send none. ARC chains are shown as reported; use the ARC Chain Analyzer for cryptographic validation. Reports over 10 MB are not accepted.
Security & privacy
Reports are processed in your browser and never uploaded or stored. The optional DNS checks send only a domain and selector. Exports omit the message body and shorten recipient addresses by default.
Related tools
- ARF Report Analyzer — all feedback report types.
- DMARC Checker — your published DMARC policy.
- DKIM Checker — the key for any selector.
- SPF Checker — your SPF record and its lookups.
- ARC Chain Analyzer — validate ARC headers.
Summary
Failure reports tell you exactly which check failed, if you can read them. The NetTools.tech AFRF Analyzer lays out SPF, DKIM and DMARC side by side, explains failures from the report's own evidence, and keeps everything in your browser.
Frequently asked questions
Is a DMARC failure report an AFRF report?
Yes. DMARC failure reports (requested with ruf=) use the AFRF format with Auth-Failure: dmarc and an Identity-Alignment field, as defined in RFC 7489.
Does the analyzer re-run SPF, DKIM or DMARC?
No. It explains what the report states. Optional DNS checks show today's DKIM key or DMARC record, which can differ from those at delivery time.
What does Identity-Alignment none mean?
Neither SPF nor DKIM produced an identity aligned with the From domain, so DMARC failed — even if SPF or DKIM passed for another domain.
Why does the analyzer say “pattern consistent with forwarding”?
SPF failing while DKIM passes is typical for forwarded mail. The report itself does not say the message was forwarded, so the analyzer names it as a pattern, not a cause.
Is the report uploaded?
No. It is parsed in your browser. Only the optional DNS checks send a domain and selector, and only when you click them.
Why do few providers send DMARC failure reports?
They can contain personal data from the original message, so many receivers send none or redact them heavily.