Verify a sealed reportHand a hash to the court.
Hand a hash to the court.
It either matches, or it doesn't.
Public, no account required. Paste a ForensicBlock report number, evidence ID, or SHA-256 hash and we'll check it against the platform's append-only audit chain.
The hash matches, or it doesn't. No middle ground.
1. Hash at sealing
At generation time, every report's canonical bytes get a SHA-256 stamp. That hash is written to the platform's append-only audit chain.
2. Tamper-evident
Any change to the report — one character, one comma — changes the SHA-256. Verification surfaces a mismatch instantly.
3. Court-ready packet
Court-ready reports carry a Certificate of Authenticity prepared to support self-authentication under FRE 902(13)/(14). Admissibility is the court's determination, in every case.
What this page does not claim. This page verifies a SHA-256 match against a sealed record. It is not a determination that the underlying report is admissible in your matter. Admissibility depends on proper handling, jurisdictional rules, the facts of the case, and expert testimony. ForensicBlock provides the cryptographic evidence and a written Certificate of Authenticity to support self-authentication under FRE 902(13)/(14); the court rules on the rest.