RegSecure Evidence Verifier

Independent, local verification of a RegSecure evidence bundle. Nothing is uploaded; nothing is fetched.

This page works entirely offline. Save it and open the file directly. It makes no network requests; you can verify that with your browser's network inspector or by disconnecting before use.

What this verifies

  1. Every audit entry's hash, recomputed from the entry's own content. Proves no entry was altered.
  2. The Merkle root, recomputed over all entry hashes. Proves the set of entries is complete and unmodified.
  3. Document hashes (optional). Select the original document and/or the derived signed PDF to compare their SHA-256 against the bundle.
Why a simple "prevHash chain walk" is the wrong check for these bundles

Each participant's device writes audit entries chained against its own local view of a live multi-device session. The exported log merges those views, so prevHash is a per-writer causal pointer and is not expected to form a single linear chain across the merged export. A failed linear walk is the expected shape of a sound multi-party bundle. Integrity is established by checks 1 and 2 above: any altered, inserted, or removed entry breaks its own hash or the Merkle root.

1. Evidence bundle (JSON)

regsecure-evidence-<timestamp>.json

2. Documents (optional)

original document → document.hash

derived signed PDF → derivedDocument.hash

Results

Select an evidence bundle to begin.