For the forwarder
Share the original certified message while keeping your own note separate.
Frank sends Toby a quotation. Toby uses Certified Forward to share it with Simon, who can check the original sender and unchanged files for himself.
Frank sends Toby the Northstar quotation. Toby needs Simon to review the original message and document.
Choose Certified Forward from the original message.
Toby adds Simon’s address and a note. The original sender, recipient, date and subject remain visible.
Toby’s note is separate from Frank’s original message.
The forwarded original identifies Frank as the sender and Toby as the forwarder, with the original recipient and timestamps.
Evidence is available. Simon still needs to verify it.
Simon downloads the evidence bundle containing the message, Northstar quotation and verification materials.
A record he can retain and check locally.
He extracts the downloaded ZIP and opens ProveThisMessage.html from the bundle.
The verification flow continues from files on his computer.
The local verifier asks for the provenance ZIP. Simon selects the bundle he downloaded.
The screenshot walkthrough shows the real verifier; it does not run verification itself.
The result confirms Frank’s original sent message bundle and that the included files have not been altered since sending.
Original bundle and file integrity verified. The public audit anchor is still pending in this capture.
Simon can verify the original sender and unchanged message and files, even though he was not the original recipient.
Share the original certified message while keeping your own note separate.
Retain the evidence and check the original sender and unchanged message and files.
An ordinary forward gives the next recipient the forwarder’s account. Certified Forward preserves the original context and evidence so the next recipient can check the original bundle and file integrity. The result shown here does not establish quotation approval or proof of receipt; its public audit anchor is pending.
Real product captures using sample documents and test recipients. This screenshot story shows a downloaded local verifier; the demo itself does not perform cryptographic verification or demonstrate a network-disconnected test.
All 8 demos →Supported Certified Forward provides provenance for the original message and files, checked under the original owning company’s key. A fresh export may be newly signed using that company’s current key. Forwarding context is separate, and the recipient still needs to establish trust in the relevant public key.
How company signing keys work →