Verify a Signed Document
Upload a signed PDF, or paste the envelope id and hash from its certificate of completion. The answer says whether the file is the one this platform sealed, whether each signature on it still covers unchanged bytes, and whether the audit trail behind it recomputes.
Nothing Checked Yet
Upload the signed PDF, or paste the envelope id and hash from its certificate of completion. The answer says whether the file is the one this platform produced and whether every signature on it still holds.
What This Page Checks
The File Itself
The SHA-256 of the bytes you supply is compared against the hash recorded when the file was sealed. One changed byte gives a different hash, so a re-saved or edited copy is reported as unrecognized.
Every Signature
Each signature is read straight out of the file: the range of bytes it covers is re-hashed, the signature is checked against the certificate inside it, and the timestamp token is verified.
The Audit Trail
Every recorded event carries the hash of the event before it. The whole chain is recomputed here, so a removed or altered entry shows up as a break at a numbered event.
What This Page Does Not Check
This seal was issued by this platform and sits on no public trust list. Chain validation against public trust lists is not performed here; open the file in Adobe Acrobat for that check. To have Acrobat trust this seal on your own computer, see Trust This Seal.
Anonymous checks have names shortened and the document title withheld. Somebody holding the file can read both off the file itself, so nothing is hidden from a recipient; a stranger quoting a hash learns nothing they did not already have.
Sending documents for signature starts at the home page.