DEVELOPMENT ENVIRONMENT - Changes here do not affect production

Verify a Document

Confirm that a signed NDA is authentic and has not been altered, using its SHA-256 fingerprint.

🔒 Your file never leaves your device — verification runs entirely in your browser

Check a document automatically

No reference number? You can still verify manually below by comparing against the hash printed on your certificate or in your completion email.

What the two hashes mean

Signed document hash — the SHA-256 of the executed PDF that was emailed to all parties. Use this to verify the copy you hold.

Original document hash — the SHA-256 of the original unsigned NDA, taken when the request was created. This proves the underlying terms were not altered before signing.

Verify manually (no website needed)

You can compute a file's SHA-256 yourself and compare it to the hash on your certificate / email:

Windows (Command Prompt):

certutil -hashfile "your-document.pdf" SHA256

macOS (Terminal):

shasum -a 256 your-document.pdf

Linux (Terminal):

sha256sum your-document.pdf

If the value produced matches the hash on your certificate exactly, the document is authentic and unaltered. If even one character differs, the file has been changed.