Analyze ARC headers

Gmail: ⋮ → Show original. Outlook: View → View message source or Message details. Thunderbird: View → Message Source. Headers alone are enough to check the structure and the seals; the complete message (headers and body, up to 1 MB) also lets the newest message signature be verified.

How it works

The headers (or the complete message) are uploaded in small pieces and analysed in stages: ARC sets are rebuilt by instance number and checked against RFC 8617, each signature’s key is looked up in DNS, every ARC-Seal and — with the complete message — the newest ARC-Message-Signature are verified with the mailauth library, and the authentication results each intermediary reported are compared hop by hop.

Stages

  • Parsing — header fields are unfolded and the three ARC fields are read with mailauth’s RFC 5322 and tag-list parsers.
  • Structure — sets are grouped by instance (i=), whatever their order: numbering from 1 without gaps, exactly one field of each type per set, required tags, and cv= consistent with RFC 8617 (none for i=1, pass afterwards).
  • DNS keys — each signature’s own <s>._domainkey.<d> is looked up through public resolvers (at most 20 different keys).
  • Cryptography — done by mailauth. Every ARC-Seal is verified on its own. The newest ARC-Message-Signature is verified when the complete message is supplied; older ones are not validated, as RFC 8617 specifies.
  • Reported results — what each intermediary recorded for SPF, DKIM and DMARC, compared hop by hop.

What cv= means

  • none — the first ARC set. pass — the sealer found the earlier chain valid. fail — the sealer found it invalid.
  • cv= is the sealer’s own statement. The analyzer compares it with what it can verify itself and reports differences.

Safeguards & responsible use

  • Your headers are kept in memory only for the analysis, never logged or stored, and deleted as soon as the result is ready. Reports and exports contain header fields and findings, not the message body.
  • Input is limited to 1 MB; only the keys named by the ARC signatures are looked up (at most 20, through public resolvers); no URLs are fetched.

Frequently asked questions

Why is the newest ARC-Message-Signature “not verified”?

It covers the message body. With headers only, the body hash cannot be checked; paste the complete raw message to verify it.

Does cv=pass mean the chain is valid?

No. cv= is what the sealer declared. The analyzer verifies the seals itself and reports when the declaration and the verification disagree.

Are the SPF, DKIM and DMARC results in the chain verified?

No. ARC-Authentication-Results are what each intermediary says it saw. They are only as trustworthy as the sealer; the final receiver decides whether to trust it.