PUBLIC VERIFICATION · FREE · NO ACCOUNT
Handed a SignSealShip document? Check it yourself.
Drop the PDF and get a cryptographic verdict in seconds — plus, for genuine documents, the full evidence timeline: consent, signatures, KMS seal, notarization, and physical delivery. No account, no envelope ID, no PIN.
FILES ARE VERIFIED IN MEMORY AND NEVER STORED
Drop the sealed PDF here
or pick it from your device — the check takes a few seconds
PDF ONLY · UP TO 25 MB · VERIFIED IN MEMORY, NEVER STORED
Your browser computes the file's SHA-256 locally so you can see what's being checked; the authoritative verdict comes from the server's cryptographic seal check. The uploaded bytes are discarded the moment the check finishes.
WHAT THIS CHECKS
Two hard checks. Four honest answers.
01 · THE SEAL
Cryptographic seal validation
Every completed document is sealed with an asymmetric key held in Google Cloud KMS. The verifier checks that seal over the document's bytes — change a single byte and it breaks, visibly.
02 · THE RECORD
Match against the system of record
A valid seal unlocks the second check: the file's SHA-256 is compared to the sealed artifact on record. A match returns the document's evidence timeline — digital and physical chains in one view.
03 · THE VERDICT
No guessing, no fuzzy matching
You get one of four answers: verified, sealed-but-modified, not a SignSealShip document, or unreadable. We never soften the crypto to "looks similar" — a near-match is a fail.
HOLDING PAPER?
A scanned copy of a printed document will not match — printing and re-scanning creates new bytes, and the seal only covers the original ones. That's tamper evidence doing its job. To verify a paper original, use the QR code printed on the document instead — it opens the same evidence record, no file required.
ONE TIMELINE, BOTH CHAINS
Who signed, who notarized, and where the paper went.
Other platforms make you enter an envelope ID and a signer's email, or wait for a PIN by email, to confirm a document — and none of them can show you what happened to the physical original. Because SignSealShip runs both the sealing and the shipping, a verified document shows one timeline: consent captured, each signature, the KMS seal, the notarization record, and carrier tracking for the shipped original. Signer identities appear masked — the public view proves the record without exposing anyone's personal details.
Verification questions, answered
What does a "Verified" result mean?
Two independent checks passed: the file carries a valid SignSealShip cryptographic seal (a CMS digital signature applied with our Google Cloud KMS key), and the file's SHA-256 hash matches the sealed document in our system of record. Together they mean this exact file was sealed by SignSealShip and hasn't changed by a single byte since.
Do you keep the files I upload?
No. Files are verified in memory and never stored — we check the seal, compare the hash, return the verdict, and discard the bytes. Verifiers are usually handling someone else's document, so the page is built on exactly that assumption.
Do I need an account, an envelope ID, or a PIN?
No — the document itself is the key. A valid SignSealShip seal can only exist on a file that actually went through our sealing process, so possessing the sealed file is what authorizes you to see its evidence timeline. Nothing to sign up for, nothing to look up, nothing emailed to you.
Why doesn't my printed-and-scanned copy verify?
Printing and re-scanning creates a brand-new file, so its bytes can never match the sealed original — that's the tamper protection working, not a bug. To check a paper document, use the QR code printed on it: it opens the same evidence record without needing the original file.
What does "Not a SignSealShip document" mean?
Only that the file you uploaded doesn't carry our cryptographic seal. It says nothing about whether the document is otherwise genuine — and by design it says nothing about whether SignSealShip has ever seen the file. The checker answers exactly one question: does this file carry our valid seal?
Can I verify the seal without this page?
Yes. Open the sealed PDF in Adobe Acrobat (the free Reader works) and check the signature panel — the CMS seal validates cryptographically with no SignSealShip involvement at all. What this page adds is the context Acrobat can't show: whose consent and signatures the record holds, when the notarization happened, and where the physical document traveled.
Want your documents to prove themselves like this?
Every document SignSealShip seals can be verified on this page by anyone you send it to — free, forever, no account required.
Send your own document