# Check a record against its seal

> Check an Esign Comply record against its seal. A record ID alone reveals neither existence nor details; verification takes the signed receipt or an exported evidence package.

Source: https://esigncomply.com/verify

Verification

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.

**Interactive on the HTML page:** a form with the field Record ID or verification link and the button "Open". Open https://esigncomply.com/verify to use it.

## 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.zip`

[Offline verifier](https://esigncomply.com/docs/sdk/verify) · [Evidence package format](https://esigncomply.com/docs/concepts/verification#package-format-summary) · [Published sealing keys](https://esigncomply.com/.well-known/jwks.json)

Limits

## 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.

---

Every page on esigncomply.com has a Markdown version at the same URL plus `.md` (the home page is `https://esigncomply.com/index.md`). https://esigncomply.com/llms.txt lists them.
