Reading a DocVerdict report
Every DocVerdict report is split into two sections, and the split is the most important thing on the page. Verified checks are facts established with cryptography: they hold no matter who disagrees. Observations are signals read from the file's records: they're real evidence, but they need interpretation and they can be innocent. Keeping these separate is how professionals reason about documents, and the report enforces that discipline for you.
Verified checks
This section covers what can be proven: whether a digital signature is present, whether it verifies, who the signing certificate names, which pages the signature covers, whether anything was added to the file after signing, and the file's cryptographic fingerprint (its hash). If your report says the document was modified after it was signed, that finding comes from the file's own structure. It isn't an opinion, and no amount of explanation changes it. What can change is the meaning: a post-signing change might be a second signer or a filled form field, and the report says what kind of change it found.
The hash deserves a note. It uniquely identifies this exact version of the file. If you and a counterparty each check your copies and the hashes match, you're holding the same bytes. If they don't match, you aren't, and that settles the "we have the same document" question instantly.
Observations
This section reads the file's self-reported records: creation and modification dates, the software that produced the file, update history, and patterns in how the file was assembled. Each observation states what was found and what it typically means. A converter in the producer field typically means the file was rebuilt after leaving its source. A modification date before a creation date typically means a tool or a hand set the dates. Typically is the operative word, which is why these are observations and not verdicts.
How to act on what you find
A strong report with a clean signature and a coherent timeline means the file's evidence supports it. You can rely on the document with normal confidence. A report with contradictions, a converter where a bank should be, dates out of order, changes after signing, means the file can't vouch for itself. The move isn't to accuse anyone. It's to ask for the original from the source: the statement directly from the bank portal, the contract from the counterparty's system. An honest sender can always produce the original. The request itself resolves most situations.
DocVerdict reports document evidence and classifications. It does not determine fraud, authenticity, or legal validity. Decisions belong to qualified professionals. For matters headed to court or involving real money, bring the report and the file to counsel; the report is built to make that conversation fast.
FAQ
Why won't the report just say whether the document is fake?
Because the file's evidence can't carry that conclusion, and any tool claiming it can is overreaching. A rebuilt file might be laundering or might be an innocent compression. The report tells you exactly what the file shows, and what it shows is usually enough to know what to do next.
What's in the paid report that the free verdict doesn't show?
The free verdict gives the one-line conclusion and signature status. The full report adds every finding with its evidence: the complete metadata timeline, page-level signature coverage, update history, producer chain analysis, and a downloadable PDF you can file or forward.
Run a check
Drop a file on DocVerdict. Free verdict in seconds, no account, and files are analyzed in memory and never stored.