A signed PDF can look untouched and still require verification. This checklist explains how to validate its cryptographic integrity, review the signer certificate, preserve useful evidence, and decide when a file should be checked again after export, storage, or workflow changes.
Overview
When someone asks whether a signed PDF is authentic and unchanged, there are two different questions to answer:
- Has the file changed since it was signed? This is an integrity question answered by validating the PDF’s digital signature and signed byte range.
- Who signed it, and can the signer be trusted? This is an identity and certificate question answered by reviewing the certificate, its trust chain, and the signature context.
A visual inspection is useful for spotting obvious problems, but it is not a substitute for cryptographic validation. Text, dates, logos, and visible signature marks can be copied or edited. A valid PDF digital signature uses certificate-based cryptography to detect changes to the signed content. It may also provide information about the signing time, certificate issuer, timestamp, and any permitted changes made after signing.
The exact labels and verification steps vary by PDF reader and digital signing platform. Treat the procedure below as a control checklist, then confirm the current terminology in the software used by your organization. For high-value contracts, regulated records, or disputed documents, preserve the original file and involve legal or compliance specialists before relying on an interpretation.
What to track
1. The original file and its fingerprint
Start with the file as received. Do not begin by printing it, scanning it again, editing it, or exporting it to another format. Record the original filename, file size, source, date received, and storage location. If your process supports cryptographic hashes, calculate and record a hash for the original file using an approved tool. The hash is not a replacement for PDF signature validation, but it helps demonstrate which exact file was examined and whether that file later changed in storage.
2. The PDF signature status
Open the file in a PDF application that supports digital-signature validation. Look for the signature panel, document status, or certificate details rather than relying only on a visible signature block on the page. Record whether the signature is reported as valid, invalid, unknown, or requiring attention.
Read the explanation behind the status. A warning may mean the document changed after signing, the certificate is not trusted by the application, certificate revocation information cannot be checked, or the signature uses a format the reader does not fully support. These conditions have different meanings and should not be collapsed into a simple “safe” or “unsafe” label.
3. Changes permitted after signing
Some signed PDFs can contain additional information after a signature is applied, such as another signature, a form completion event, or an annotation. A validation panel may distinguish between changes that are permitted by the document’s signing workflow and changes that invalidate the signature. Check the reader’s detailed message and the signature’s covered revision. If the file was saved, optimized, linearized, merged, or converted after signing, compare the current file with the original signed version and investigate any warning.
4. Certificate and signer details
Review the certificate associated with the signature. Capture the signer’s displayed name, certificate subject, issuer, validity period, and, where available, certificate fingerprint or serial number. Confirm that the signer identity matches the expected person or organization through an independent business record or established contact—not solely through the name displayed in the PDF.
Check whether the certificate was valid at the signing time and whether the application can establish a trusted certificate chain. Trust settings are local to an application or organization; a certificate being trusted on one device does not automatically prove that every reader will treat it the same way. A valid certificate also does not, by itself, prove that the signer had authority to bind an organization or that the underlying agreement is legally enforceable.
5. Time and revocation evidence
Note the signing time shown by the application and whether the signature includes a trusted timestamp. A device clock, a platform-recorded event time, and a trusted timestamp are not necessarily equivalent. Also note whether certificate revocation status—such as a current revocation check or embedded validation data—was available at verification time. If the reader cannot complete a check because the device is offline or the validation data is absent, record that limitation instead of treating the result as conclusive.
Visual checks versus cryptographic checks
| Check | What it can show | What it cannot prove |
|---|---|---|
| Read the visible signature block | The displayed signer name, date, and apparent document context | That the PDF has not been edited or that the mark is cryptographically linked to the file |
| Compare pages with a known copy | Obvious differences in text, layout, or attachments | Hidden changes, metadata changes, or certificate validity |
| Validate the PDF signature | Whether signed content passes the application’s integrity check and what revision was signed | That the signer intended the transaction or had organizational authority |
| Review certificate and trust details | Certificate identity, issuer, validity, and available trust information | That every business fact in the document is accurate |
Cadence and checkpoints
Verification should happen at the point of receipt, before approval or payment, and before a signed record is presented as evidence. For recurring workflows, add a monthly or quarterly review rather than waiting for a dispute.
At receipt
- Save the original attachment or download without renaming away useful identifying information.
- Open it in an approved PDF reader and inspect the signature status.
- Record warnings, signer details, timestamp information, and the file hash if used by your process.
- Move the file into controlled, encrypted document storage with restricted editing and deletion rights.
Before a business action
Recheck the file before releasing funds, changing a contract record, granting access, or completing an approval. Confirm that the verified file is the same version referenced by the workflow. An electronic signature audit trail can add useful context about invitations, authentication, completed actions, and downloads; it complements, but does not replace, the PDF’s own signature validation. See the electronic signature audit trail guide for a broader evidence review.
Monthly or quarterly control review
Sample completed files from each important signing workflow. Check whether readers report new warnings, whether certificates or trust settings have changed, and whether staff are accidentally editing or re-exporting signed files. Review reusable forms and signing configurations on a defined schedule using an eSignature template governance checklist. Keep verification procedures aligned with the current PDF reader, signing platform, certificate policy, and record-retention requirements that apply to your organization.
How to interpret changes
A green or positive status is useful, but read the detail. “Valid” generally indicates that the application’s cryptographic checks passed for the signed revision and that its trust rules accepted the certificate or signature. It does not settle questions of authority, identity outside the certificate, contract formation, or whether the document is appropriate for the transaction.
A warning that the document was modified after signing requires comparison with the signing workflow. If the change is an expected second signature or an allowed form action, the reader may identify it as permitted. If the change is an edited clause, replaced page, new attachment, or unexplained metadata update, stop the workflow and obtain the original signed version or a new signature.
An “unknown” or untrusted certificate result is not automatically proof of tampering. It may reflect an incomplete trust chain, an organization-managed certificate, an unavailable revocation service, or an unsupported signature format. Escalate the file to the sender or your certificate administrator, and document what could and could not be verified.
Use this evidence record for each material verification:
- Document title, original filename, and file hash, if available
- Source, date received, and person who performed the check
- PDF reader or validation service and version
- Signature status and exact warning or validation message
- Signer name, certificate issuer, validity period, and fingerprint or serial number when shown
- Signing time, trusted timestamp status, and revocation-check result
- Any post-signing changes, exports, or permitted revisions
- Decision, escalation owner, and links to related workflow records
When to revisit
Revisit this checklist whenever a signature warning appears, a signed PDF is re-exported or merged, a new PDF reader or signing platform is introduced, certificate trust settings change, or a record is prepared for an audit, legal review, or dispute. A quarterly review is a practical baseline for recurring business workflows; increase the frequency for high-value or heavily regulated records.
At each review, test one known-good signed file and one deliberately altered test copy in a controlled environment. Confirm that the reader distinguishes the original from the altered version, that staff can locate certificate details, and that evidence records are stored with appropriate access controls. Never use the altered test copy in a live transaction.
Finally, preserve the verified original in a controlled document repository, limit later editing, and retain the validation record alongside the file. If your organization also scans paper documents or uses OCR before signing, keep the pre-signing source and workflow history separate from the final signed PDF. That separation makes it easier to show which content was scanned, which version was approved, and which exact file received the digital signature.