Check a record against its seal
Verification takes proof. A record ID alone reveals nothing: not whether a record exists, and not its documents, times or later history. Open a record's verification page, then bring its signed receipt, a document, or an exported evidence package.
Signed receipt
Anyone who holds the receipt
The signature is checked in your browser against the published sealing keys. Esign Comply then reports proof status for that record.
Document
Anyone who holds a file
The file is hashed in your browser and compared with the document hashes sealed in the record. It is not uploaded.
Evidence package
Anyone who holds an export
The open-source verifier repeats every check offline with public keys only. It needs no account.
Verify offline
Run the verifier on an exported package. It works without network access and does not rely on this site.
$npx esigncomply-verify rec_Z4m8.zipOffline verifierEvidence package formatPublished sealing keys
What a pass shows, and what it does not
This result says whether the record matches its seal. It does not establish who signed or whether any agreement is valid or enforceable.
A pass shows
- The stored record still matches the hash Esign Comply sealed.
- The receipt was signed with a sealing key that Esign Comply publishes. A receipt signed with a test key never verifies as live.
- The external timestamp token, where one is attached, was issued over the record hash by an authority other than Esign Comply. It bounds when the record existed.
- The record's ledger entry is in a signed checkpoint, and the log has only been added to since.
A pass does not show
- Who the signer was, or the signer's capacity or authority.
- That the signer read the documents.
- When the person acted. A timestamp token bounds when the record existed.
- That any agreement is valid or enforceable. A court decides admissibility and weight.
- What the signer's screen looked like to a person. Esign Comply did not review the content of the documents.