Back to Home

Document Verification Guide

How we verify every file and how you can validate it yourself

Verification Pipeline

Every document in the archive follows a consistent verification pipeline before publication. The goal is to preserve the original DOJ release while providing a transparent audit trail.

  1. Document sourced from official PDFs
  2. Extract text and metadata for indexing
  3. Generate a SHA-256 hash of the source file
  4. Cross-reference the file with public DOJ listings
  5. Publish the document with hash and source link

How You Can Verify a Document

You can independently validate any file using the same process we use internally.

  1. Download the file from the archive
  2. Calculate its SHA-256 hash locally
  3. Compare the hash with the one displayed on the document page
  4. Click the "Source" link to open the official DOJ PDF
  5. Confirm the content and metadata match exactly

Example Verification (MME-2012-10-15-E-001)

Example: MME-2012-10-15-E-001 is the "wife hunt" email exchange. Use the steps above to verify it.

1) Download the PDF from the archive collection page.

2) Generate a SHA-256 hash and compare to the hash shown on the document view.

3) Open the DOJ source link and confirm the metadata and text match the archive copy.

Red Flags

If you see any of the following, treat the document as unverified and report it.

  • No verifiable hash or hash mismatch
  • Metadata contradictions (date/participants do not align)
  • Unusual file formats or edited scans
  • Missing source links to official DOJ releases

Learn More