Checking signature and archived response…
Verify authenticity
The remote verifier signs an attestation that this HTTP response came from the named website over TLS, recording the time on its own clock. TLSNotary uses secure multiparty computation (MPC) to authenticate the response while keeping its contents private from the verifier; this browser checks the signature and matches the saved response to the signed fingerprint.
When OpenTimestamps is also enabled, its Bitcoin timestamp covers this receipt and saved response, proving that the attestation and content fingerprints existed by the confirmed block’s timestamp.
Verifier signing key
ArchiveBox includes the public signing key for tlsnotary.zervice.io with its TLSNotary plugin. This browser used that key to check the verifier’s signature. For a self-hosted verifier, enter the public key supplied by its operator through a trusted channel.
To verify independently, download both files and open tlsnotary.zervice.io. This preview verifies the saved files in your browser.