Verify a signed document
Confirm a PDF was really completed through Docracy's signing flow, and when — then check it a second way, independently of Docracy, on the Bitcoin blockchain.
- Checked against Docracy's records
- Independently checkable on Bitcoin
SHA-256 · computed in your browser · nothing ever uploaded
What this does and doesn't prove
A match confirms a document with these exact bytes was completed through Docracy's signing flow, and when — even one changed character produces a completely different hash, so this reliably detects tampering.
It does not verify who physically signed — Docracy's default signature is a Simple Electronic Signature (SES), not identity-verified. See Trust & security for details.
Every completed document's hash is also submitted to the free, public OpenTimestamps protocol, which anchors it to the Bitcoin blockchain — so this can be verified independently, without trusting Docracy's own records at all.