Skip to content
AdminKit

ARC (Authenticated Received Chain)

What is ARC (Authenticated Received Chain)?

ARC (Authenticated Received Chain) lets each server in an email forwarding chain sign a record of what a message's SPF, DKIM and DMARC results looked like before that hop forwarded it onward. AdminKit's guide explains how ARC preserves authentication results across a forwarding chain that would otherwise fail SPF.

By AdminKit team, Netbase JSC · Updated

ARC (Authenticated Received Chain), defined in RFC 8617 (see its IETF Datatracker entry for the document’s status), lets each server in an email forwarding chain add a signed record of what the message’s SPF, DKIM, and DMARC results looked like before that hop forwarded it onward. A forwarded message typically fails SPF, and sometimes DKIM, by the time it reaches its final destination, because forwarding changes the connecting server’s IP and can alter the message in ways that break a DKIM signature; ARC gives the receiving mail system a verifiable record that the message passed authentication earlier in its path, so it can weigh the forwarder’s own reputation instead of rejecting on the final-hop failure. Both the forwarder and the final recipient’s mail system need to support ARC for it to help — support exists today among major providers including Gmail and Microsoft 365, but is not universal. Google Workspace’s ARC documentation gives the same rationale: forwarding can change a message’s content, so legitimate forwarded mail can fail SPF or DKIM, and ARC reduces the chance of that failure. ARC builds specifically on the SPF/DKIM/DMARC results it preserves, with DMARC itself defined in RFC 7489 (now RFC 9989).

ARC (Authenticated Received Chain) is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Does ARC fix SPF or DKIM failures caused by forwarding?

Not exactly -- ARC doesn't make the forwarded message pass SPF or DKIM itself; it gives the receiving mail system a verifiable record that the message passed authentication earlier in its path, so it can weigh the forwarder's reputation instead of rejecting on the final-hop failure.

Do both the forwarder and the final recipient need to support ARC?

Yes -- both ends of the chain need to support ARC for it to help, and while support exists today among major providers including Gmail and Microsoft 365, it isn't universal.

Why does a forwarded message typically fail SPF or DKIM in the first place?

Forwarding changes the connecting server's IP, which breaks SPF, and can alter the message in ways that break a DKIM signature -- the exact gap ARC is designed to work around.

Is ARC a replacement for DMARC?

No -- ARC builds on top of the SPF, DKIM, and DMARC results it preserves; DMARC itself (RFC 7489, now RFC 9989) still defines what a receiver does with the authentication outcome.