ARC & Email Forwarding Analyzer
Paste message headers to diagnose forwarding and ARC structure without claiming cryptographic verification.
Run a diagnostic
Report files remain in your browser; no reports are uploaded by these workflows.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to interpret this result
Paste message headers to diagnose forwarding and ARC structure without claiming cryptographic verification.
No. A header claim is not independent cryptographic verification and a receiver may not trust the sealer.
No sample results are used for your scan.
Evidence this tool can evaluate
Parse ARC-Seal, ARC-Message-Signature and ARC-Authentication-Results headers and check structural consistency, instance numbering and chain-validation tags. This is not a cryptographic signature verifier.
What to do with the findings
Check the original Authentication-Results and forwarding path, then use trusted receiver-side verification before relying on ARC claims. A claimed cv=pass alone is not proof of authenticity.
Need continuous authentication protection?
Method and limitations
Inspect ARC chain structure, forwarding evidence and reported SPF, DKIM and DMARC outcomes. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Does ARC cv=pass prove an email is legitimate?
No. A header claim is not independent cryptographic verification and a receiver may not trust the sealer.
Educational diagnostics, not a guarantee of deliverability or provider approval.