Keep the evidence.
Skip the false verdict.
Forgeries preserves the exact file, checks the technical properties that can actually be verified, compares it with a reference you supply, and records the steps used. It produces an evidence report — not an automatic verdict.
No 0–100 authenticity score. Findings stay in defined evidence states.
🧊 Preserve the exact file
Raw bytes are hashed with SHA-256 before any parsing, and the original is kept separately.
🔬 Check what's verifiable
Identity, structure, embedded signatures, extracted fields and page differences — each cited.
🧑⚖️ Record the human step
The report shows how you contacted the issuer and what they said. The software does not call anyone.
From a suspicious file to a defensible record
Deliberate, documented, and honest about uncertainty.
Preserve & hash
Upload the document; its bytes are hashed before anything else happens.
Check & compare
Run defined checks and compare against a supplied reference, page by page.
Confirm & report
Record the issuer follow-up, then produce an evidence report you can share.
Never collapsed into a score
"No issue found" is not a pass. Each finding lands in exactly one state.
| State | What can be reported |
|---|---|
| Cryptographically verified | A supported signature or content credential validates against the trust policy and the covered bytes have not changed. |
| Matched to supplied reference | Byte hash matches, or reviewed fields match a separately uploaded reference whose provenance is recorded. |
| Inconsistency found | Defined fields, pages, signature state or versions conflict. Both originals and the specific rule are shown. |
| Unresolved | Missing reference, unsupported signature, scan-only file, ambiguous extraction, unknown trust chain or unavailable revocation check. |
Absence of a digital signature or C2PA credential is not proof of forgery. A valid credential proves only the properties it covers under the verifier's trust policy.
A workspace built for scrutiny
Every step is recorded so someone else can follow your reasoning.
Byte-exact hashing
SHA-256 of the original bytes, recorded before parsing.
Signature state
Supported signatures and credentials checked against a trust policy.
Page-by-page diffs
Reviewed fields compared with a reference, with the regions cited.
Comments & findings
Annotate findings and keep the discussion attached to the evidence.
Evidence reports
Generate a shareable report; exports are queued and downloadable.
Private handling
Originals are stored privately and served only as authorised attachments.
What this is not
Set expectations before you rely on any tool — including this one.
- Not a forensic expert and not a claim of court admissibility
- No automatic verdict, no 0–100 authenticity score, no fraud classifier
- No independent issuer identity from a logo, printed email, metadata or image classifier
- Deepfake detection, handwriting/ink analysis and device acquisition are outside scope
Check the basics first
Deterministic, account-free, nothing persisted.
Good to know
Will it tell me if a document is fake?
No. It reports what can be verified and where inconsistencies exist, in defined states — not a verdict.
Does it contact the issuer for me?
No. It records the follow-up you performed, from independently sourced contact details.
What about missing signatures?
An absent signature is recorded as a state, not treated as proof of forgery.
Can I export a report?
Yes — evidence exports are generated as a queue job and available to download.
Review the document. Keep the evidence.
Create an account and open your first case.