Integrity check
Verify a certificate
Every document version controlled in ProveWise carries a SHA-256 content hash, printed on its certificate and audit pack. Use this tool to confirm a file you hold is byte-for-byte the one that was signed — the file is hashed entirely in your browser and never uploaded.
Choose a file or drop it here
Computed locally with the Web Crypto API · nothing leaves this page
Hashing…
Computed SHA-256
How full verification works
- Content hash — recompute the file's SHA-256 (above) and match it to the hash on the certificate. Equal ⇒ the bytes are unchanged.
- Hash-chained audit — inside ProveWise, each audit entry is linked to the previous one, so the record of who did what, and when, is tamper-evident (21 CFR Part 11 §11.10(e)).
- Signature manifest — the audit-pack PDF manifests each electronic signature bound to that exact content hash, with signer identity, meaning, and UTC timestamp.
What this page does and doesn't do. It confirms a file matches a hash you already hold — privately, in your browser. It does not look up documents across customer accounts (that data is tenant-private). Full chain and signature verification is available to authorized users inside the application, and in every exported audit pack.