Verify a document
Drop a signed PDF and this page checks its signature, what that signature covers, and whether anything has been added since. Drop a Thorium verification file and it re-derives the whole hash chain instead. Both run in your browser. Nothing is uploaded and you don’t need an account.
The PDF doesn’t have to come from Thorium. Any PAdES or Adobe-signed document will work.
Drop a signed PDF or a verification file
A signed .pdf — from anywhere, not just Thorium — to check its signature and what it covers. Or the .json export from Thorium, under Export on the audit log or on a document, to re-derive its hash chain. Both are read here in your browser. Nothing is uploaded.
How a signed PDF is checked
- The signature names the bytes of the file it covers. Those bytes are hashed here and compared with the hash the signature commits to.
- The signature over that hash is checked against the public key in the certificate carried inside the document.
- The range it covers is checked against the file's real length, because content added after a signature leaves the signature valid over the part it signed while the reader shows you the rest.
How an audit trail is checked
- Each entry commits to its own contents and to the digest of the entry before it.
- Re-deriving those digests from the file shows whether anything was edited, reordered or removed.
- Changing one entry invalidates it and every entry after it.
What neither check tells you
A hash chain shows a trail is internally consistent and unedited since export. It doesn’t show the file came from Thorium, because anyone can generate a self-consistent chain of their own.
A signature shows a document hasn’t changed since it was signed with a particular key, and which certificate that key belongs to. It doesn’t establish who holds the key. That needs a trust store and calls out to certificate authorities, which this page deliberately doesn’t make. Read the certificate it shows you and judge whether the name is the one you expected.