Skip to main content

Evidence integrity

Verify the files, then verify the claims.

This build includes a machine-readable manifest for 730 evidence files. Every row gives the exact relative filename, byte size, full 64-character SHA-256 digest, and UTC hashing time.

Download the SHA-256 manifest

What a matching hash proves

A matching digest shows that the downloaded file is byte-for-byte identical to the file hashed for this manifest. It can detect later alteration or corruption.

What a hash does not prove

A hash does not establish who created a document, whether every statement is true, whether an allegation is proven, or whether a court or agency reached a legal finding. Those questions require source and context review.

Manifest details

Algorithm
SHA-256
Files listed
730
Hashing began
July 17, 2026 at 8:36:46 PM UTC UTC

Runs entirely in this browser

Verify a local file without uploading it

Choose or drop a file below. Your browser calculates its SHA-256 digest locally with WebCrypto and compares it against the unified manifest for 1,869 preserved files. The selected file is not transmitted to this website.

Waiting for a local file.

Unified forensic manifest

Files indexed
1,869
Cross-check mismatches
0
Algorithm
SHA-256

Manifest root SHA-256: e7017b58eb3cfc556de314bf36160bc44ddc459abe92694b99a49465aeca6226

This root is a build-generated consistency digest. It is not an independent timestamp, digital signature, notarization, or proof of when any file first existed.

Review standard

  1. 1. Identify the exact file.
    Match the relative filename and byte size.
  2. 2. Calculate SHA-256.
    Use a trusted local hashing tool on the downloaded file.
  3. 3. Compare all 64 characters.
    An abbreviation or partial digest is not sufficient verification.
  4. 4. Check provenance and context.
    Review the source, date, surrounding correspondence, and any agency or court disposition.