or paste a hash
How this works
When a document is completed in Doc Sign Flow, the final sealed PDF's SHA-256 hash is recorded in its tamper-evident audit trail. Because any change to a file changes its hash, comparing a file's current fingerprint against the recorded one proves whether it's byte-for-byte identical to the document everyone signed. You can also compute the hash yourself (sha256sum file.pdf on Linux/Mac, certutil -hashfile file.pdf SHA256 on Windows) — no trust in this page required.