Topic · Authentication
ARC
Authenticated Received Chain preserves authentication assessments through trusted forwarding intermediaries.
How it works
Forwarders add signed ARC sets containing authentication results and seal information.
What can go wrong
ARC does not make a malicious message safe and receiver trust decisions vary.
What to check or do
Inspect ARC chain validity alongside original DMARC, SPF and DKIM results.
Practical scenario
A newsletter forwarded through a list manager loses its original DKIM validation after a footer is inserted. ARC may preserve intermediaries’ authentication observations, but the ultimate recipient still decides whether those intermediary results are trustworthy.
Verification checklist
- Read ARC-Authentication-Results at each hop.
- Verify ARC signature and chain validation outcomes.
- Identify the intermediate forwarding services and original sender.
- Avoid treating a passing ARC chain as an automatic override of spoofing indicators.
How to investigate ARC
- Signal to investigate
- Forwarding through a mailing list can alter a message after initial authentication.
- Evidence to collect
- Inspect ARC-Seal, ARC-Message-Signature and ARC-Authentication-Results across the relay chain.
- Common wrong conclusion
- ARC helps convey previous authentication context; receivers still decide whether they trust the intermediaries.
Put this into practice
Run a focused check, then explore protection if your domain needs it.