site-plan-A1.pdf (1 pages)
No signature is present. The findings below are metadata observations only.
This file's records are consistent with a single-export original from CAD plotting software. No signature is present, so nothing is cryptographically proven.
Verified checks
These checks are cryptographic. They can be proven or disproven.
Digital signatureInformational
This document has no digital signature. There is nothing cryptographic to verify.
Why it matters: Unsigned PDFs can still be useful, but the file cannot prove that its bytes were sealed by a signer.
Next step: Use the metadata and timeline observations below, and request a signed original when the document depends on signer proof.
Technical detail
No signature dictionary was found in the PDF. Without a signature, no part of the file is cryptographically sealed.
File fingerprintInformational
This is the file's unique fingerprint. Any change to the file, even one byte, produces a different fingerprint.
Why it matters: The fingerprint lets another person prove they are looking at the exact same file later.
Next step: Keep this hash with the file, email, or case note so later copies can be matched byte for byte.
Technical detail
SHA-256: 6f1a09c4e2b35d7a8190f4c3a2e6b5d4c3b2a1908f7e6d5c4b3a29181706f5e4
Observations
These are signals from the file's records. They suggest, but never prove, how the file was made and handled.
Generated once, never re-savedConsistent
No incremental updates: this file was generated once and never re-saved. Edits with most PDF tools leave save layers, and this file has none.
Why it matters: Save layers are the file's own record of how many times it changed after the first export.
Next step: Match the layer count against the file's story: a single export should have one, a signed document gains one per signature.
Technical detail
PDFs save changes by appending a new generation to the file, so every re-save leaves a layer. This file contains exactly one generation: the byte structure of a single export. A careful rebuild can also produce one generation, so this supports, but does not prove, an unedited file.
Creating softwareInformational
This file reports it was made with AutoCAD 2025 - DWG To PDF.pc3, AutoCAD.
Why it matters: The software trail often shows whether a file came from a source system, an editor, a converter, or a print step.
Next step: Compare the software named here with the document's claimed source and ask for an original export if they do not fit.
Technical detail
Producer and creator fields are written by the software that created the PDF. They are informational and can be edited.
Document datesConsistent
The file reports it was created and last modified at the same time, on May 18, 2026. This is consistent with the stated dates.
Why it matters: Creation and modification dates are editable, but their order often exposes rebuilt or re-saved files.
Next step: Check whether these dates fit the document's story, email timestamps, and any source-system records.
Technical detail
PDF /CreationDate equals /ModDate, which is typical for a file that was exported once and not edited afterward.
What this means and what to do next
Nothing in this file's records contradicts its story, and nothing proves it either, because unsigned files cannot prove themselves. If the document matters, keep the original file as received and compare any later copy against the fingerprint above. For a decision that depends on the document, request the original directly from the source system.
Keep this report. It records this file's fingerprint as verified on June 10, 2026.
DocVerdict reports document evidence and classifications. It does not determine fraud, authenticity, or legal validity. Decisions belong to qualified professionals.