Document Forensics
Analyze PDF metadata to verify document authenticity. Identify creation software, authorship, modification history, and chain-of-custody gaps.
In practice: This is how I proved that seven lab reports were created on a desktop computer — not in a laboratory.
What problem it solves
Document Forensics digs into the metadata of PDFs and other documents to verify their authenticity. It identifies the software used to create them, the author field, modification timestamps, font inconsistencies, and chain-of-custody gaps. When institutions submit documents that were supposed to come from labs, agencies, or official sources — this tool tells you where they actually came from.
Who it is for
Investigators and litigants who suspect documents have been forged or altered.
What you need before starting
- The original digital PDF when possible—not a photo of a printout (metadata is often lost in photos)
- What the other side claims about the document (who made it, when, and on what system)
- A safe place to store reports that may describe sensitive case material
Step-by-step (plain language)
- 1
What this tool needs
A file you received electronically, or the earliest copy you can obtain. The more generations away from the original (resaves, forwards), the less metadata may mean.
- 2
What you upload or prepare
Drop the file into the analyzer (or run the command your operator gives you). Keep a copy untouched in case you need to prove chain of custody later.
- 3
What the tool does automatically
Reads embedded PDF properties: creation and modification times, producer software, author fields, and related technical flags when present.
- 4
What you review manually
Compare those fields to the story about the document. Ask: does “Created with Microsoft Word at home” match “generated by Lab X”? Flag mismatches for your lawyer.
- 5
What you get at the end
A structured report you can attach to a declaration draft or give to counsel—it explains what the file says about itself, not what a witness says.
- 6
When to stop and ask for help
Stop if you might break a protective order or discovery rule by analyzing a file, or if you need an expert affidavit—use counsel or a qualified forensic examiner for court.
Deployment and how it runs
Technical sequence (for operators)
- 01Upload a PDF or document for analysis
- 02Review the metadata report: creation date, author, software, modifications
- 03Compare metadata against claimed provenance
- 04Generate a forensic analysis report for sharing with counsel
- 05Batch scan multiple documents for systematic anomalies
Example outputs and proof
- A 'Digital Fingerprint' report of the document
- A list of all hidden metadata fields (Author, Software, Timestamps)
- A red-flag report highlighting common signs of document alteration
Sample excerpt (illustrative, not from a live case)
Metadata summary (illustrative — not from a real case) ------------------------------------------------------ File: lab-report-2024.pdf Producer: Adobe Acrobat 23.x / macOS PDF engine Creator tool: Microsoft Word for Microsoft 365 Created (claimed): 2024-02-10 14:22 UTC Modified: 2024-02-11 09:05 UTC Author field: J. Doe (home account) Flags for review: consumer authoring tool vs. stated institutional origin
Visual proof
These are conceptual wireframes, not live product screenshots. They explain layout only—we will swap in real UI captures when available.
Limitations and safety boundaries
- No public download or hosted runner is linked from this site yet—see distribution note below.
- Cannot detect changes made to a physical paper document that was then scanned
- Some privacy-focused software can strip metadata before you receive the file
- Requires the original digital file for most accurate results
Public vs verified vs compute-limited
Public path: use and docs are aimed at open access where deployed. Heavier or managed use may still require verification. Nora's Law is a platform and framework—not legislation. These are software tools, not votes or statutes.
Public tools stay public first. Join is for trust, heavier workflows, and collaboration—not a substitute for counsel.
Public tools require public support. Fund Public Access →