Topic · Investigation
Authentication-Results parsing
Authentication-Results parsing extracts receiver-recorded authentication verdicts and identities from standardized message headers.
How it works
A trusted receiving service records methods such as spf, dkim and dmarc together with evaluated domains and reasons.
What can go wrong
Attackers can inject forged upstream Authentication-Results headers; not every header in a raw message is trustworthy.
What to check or do
Anchor analysis on your trusted receiver’s added headers and correlate with DNS and delivery logs.
How to investigate Authentication-Results parsing
- Signal to investigate
- A message includes two Authentication-Results headers with conflicting DMARC results.
- Evidence to collect
- Identify trusted authentication service identifiers and the hop that inserted each header.
- Common wrong conclusion
- An attacker can prepend a fake Authentication-Results header before your receiver processes the message.
How to interpret the evidence
Authentication-Results communicates evaluator observations, not a universally trustworthy statement. Mail gateways may remove or annotate untrusted headers; multi-hop paths add legitimate repeated results.
What to change and how to verify it
Anchor interpretation to trusted receiving systems and preserve the original raw message during incident triage.
Put this into practice
Run a focused check, then explore protection if your domain needs it.