What does it mean when the file does not match?

Either the PDF was changed after it was sealed, or it was not signed with SignElectronically. When the file still names one of our envelopes, the result says that it is a changed copy and shows the fingerprint of the sealed original, so you can ask the sender for that file.

Do you keep the file I upload?

No. The file is read once to calculate its SHA-256 fingerprint and to inspect the digital seal, then it is removed. Only the result is shown to you.

Can I check the seal without this page?

Yes. Every completed document carries a digital seal inside the PDF. A PDF reader that shows signature details reports a broken seal when the content changed after sealing. This page adds a second check against our records, which also proves the document was completed here.

Where do I find the SHA-256 hash of a document?

It is printed on the certificate of completion attached to every signed PDF and shown to the sender on the envelope page. You can also calculate it yourself with the checksum tool of your operating system and compare the two values.

Does a match prove who signed?

A match proves the file is the sealed original. Who signed, when, from which IP address and how each signer was verified is listed on the certificate of completion inside that file, backed by a hash chained event log.

Document verification

Verify a Signed PDF

To verify a signed PDF, upload it here. We compare its SHA-256 fingerprint with the one stored when the document was sealed and tell you whether the file is the untouched original or was changed after signing.

Works for every document completed with SignElectronically
No account needed, the file is checked and removed
Also reads the digital seal embedded in the PDF

How the check works

Two independent proofs in every signed PDF

Fingerprint on record

When the last signer finishes, the final PDF is sealed and its SHA-256 fingerprint is stored. This page recalculates the fingerprint of your copy and compares the two values.

Seal inside the file

The PDF carries a digital seal that covers the whole document. A PDF reader reports a broken seal as soon as the content changes, with no connection to us.

Hash chained event log

Every step, sent, opened, consent, signed, sealed, is an event that includes the hash of the event before it. Removing or editing one event breaks the chain.

Questions about verifying a signed PDF

Upload the PDF on this page or paste its SHA-256 hash. We calculate the fingerprint of your file and compare it with the fingerprint stored when the document was sealed. A match means the file is byte for byte the sealed original. Any difference, even one changed character, gives a different fingerprint and the check fails.

Read how the audit trail is built and what makes signatures valid under ESIGN and UETA.

Send documents that anyone can verify

Every envelope ends with a sealed PDF, a certificate of completion and a fingerprint on record.

See pricing