NIRAVI
Records — document verification

Verify an executed document

Drop the PDF you were given. Its SHA-256 fingerprint is computed in your browser — the file never leaves your device — and compared against the fingerprint sealed into the record.

Verification reference:
Drop the PDF here
or click to choose a file

What protects a Niravi record

  1. Tamper-evident seal — electronically signed documents are sealed with a digital certificate on completion; any change to the file after sealing is detectable in any PDF reader's signature panel.
  2. Signing certificate — the final pages record every signer's identity, e-mail, IP address and sent/viewed/signed timestamps (for wet-ink counterparts, an execution certificate with the scan's fingerprint).
  3. SHA-256 content fingerprint — the exact bytes of the executed file are hashed and stored in the record; that is what this page checks.
  4. RFC 3161 trusted timestamp — an independent timestamping authority (DigiCert) attests the sealed file existed at completion time; the token is filed with the record and verifiable with openssl ts -verify.
  5. Template provenance — the instrument's unfilled template is pinned by git commit and content hashes, so what was signed is reproducible.
  6. Immutable record — executed records are locked in Niravi Records; changes require a new instrument, never an edit.
Niravi Inc. · a Delaware corporation · Questions or a mismatch? Write to [email protected] with the verification reference.