Forgeries

← Tools

Evidence-state guide

A report uses exactly these states for findings. They are never collapsed into a 0–100 authenticity score, and “no issue found” is not a pass.

Cryptographically verified

A supported signature or content credential validated against the configured trust policy and the covered bytes have not changed. This proves only the properties the credential covers under that policy, not whether the document's claims are true.

Matched to supplied reference

Byte hashes matched, or reviewed fields matched a separately supplied reference. The reference's own provenance is recorded and is not assumed authentic.

Inconsistency found

Defined fields, pages, signature state or versions conflict. Both originals and the specific rule are shown. An inconsistency is an investigation trigger, not proof of forgery or theft.

Unresolved

A reference is missing, the signature is unsupported, the file is scan-only, extraction is ambiguous, the trust chain is unknown or revocation could not be checked.

Check-level markers

Observation A neutral technical fact recorded from the file, with no finding attached.

Not supported No tested validator is configured for the check. It is never shown as a successful check.