Before approving, forwarding, or storing a signed file, use this practical checklist to verify the digital signature, confirm who signed it, detect changes made after signing, and document any warnings that need follow-up.
Overview
A digital signature is designed to connect a document to a signing certificate and to reveal whether the signed content has changed. Digital signature verification is therefore more than checking for a visible signature image. A proper review considers four separate questions:
- Integrity: Does the cryptographic signature still match the file?
- Signer identity: Who does the signing certificate identify, and is that identity appropriate?
- Trust: Can the certificate chain be linked to a trusted certificate authority or organizational trust source?
- Timing and status: When was the signature created, and was the certificate valid or revoked at the relevant time?
These checks are related but not interchangeable. A file can have an intact signature while the signer certificate is unknown to your device. A certificate can be expired today while still having been valid when the document was signed, particularly when a reliable trusted timestamp is present. Conversely, a document may display a name or scanned signature while containing no cryptographic signature at all.
Use the original file whenever possible. Save it without renaming or editing it, and verify it in a reputable PDF reader or validation tool rather than relying only on a browser preview. For broader background on signed-document checks, see our guide to verifying a digitally signed document.
Checklist by scenario
When reviewing a signed PDF
- Obtain the original attachment. Ask the sender to resend the file if it was converted, printed and scanned, compressed, or passed through a system that may have removed signature data.
- Open it in a signature-aware PDF application. Look for the signature panel, document message, or validation controls. A visible signature block on the page is not sufficient evidence by itself.
- Check the document status. The application should indicate whether the document has been modified after signing. Review the list of permitted changes, if the application provides one.
- Inspect the signer certificate. Record the subject name, organization or email attributes where available, issuing authority, validity period, and certificate purpose. Confirm that these details match the expected signer through a separate trusted channel.
- Review the certificate chain. Determine whether the signer certificate chains to a trusted root and whether any intermediate certificate is missing or untrusted. Trust-store problems can produce warnings even when the file itself has not changed; see this certificate trust-store troubleshooting guide.
- Check the timestamp. A trusted timestamp can help establish when the signature was created. Distinguish a timestamp issued by a trusted timestamp service from a time displayed by the local computer or application.
- Check revocation information. If available, review whether the certificate was checked through an OCSP response, certificate revocation list, or another status mechanism. A current validation result and a historical signing-time result may not be the same.
When a signature shows as invalid
Do not immediately conclude that the document is fraudulent. First save a copy of the file and capture the exact warning. Then determine whether the problem concerns document integrity, certificate trust, missing validation data, or certificate status. Reopen the original in another current, signature-aware application if your process permits, but do not edit or resave it during troubleshooting.
- Document changed after signing: Compare the signed version with the sender’s original and ask what changes were made and when.
- Signer identity cannot be verified: Obtain the certificate details and validate the signer through an independent contact or organizational record.
- Certificate chain is incomplete: Check whether the required intermediate certificates are available and whether your organization’s trust store is current.
- Certificate is expired: Check the signing timestamp and any embedded validation data before treating expiration as proof that the signature was invalid when created.
- Certificate is revoked: Pause approval and ask the issuer or signer to explain the status. Revocation is a serious warning, but its meaning can depend on the time of signing and the validation evidence retained.
When reviewing another signed format
PDF is common, but signatures may also be embedded in XML, office documents, containers such as ASiC, or other application-specific formats. Use a validator that understands the format and preserve the complete signed package. Do not extract one file from a signed container and assume that the extracted copy carries the same verification context. For technical investigations, record the file hash, signature format, certificate chain, validation time, and tool version.
What to double-check
Identity is not the same as a name on screen
Read the certificate details rather than relying on the name printed beside the signature. A certificate may identify an individual, an organization, a mailbox, or a device, depending on how it was issued. Match the identity to the transaction and verify unusual requests through a known contact method. A successful cryptographic check does not independently prove that the person was authorized to sign the particular contract.
Integrity is not the same as business approval
A valid signature generally indicates that the signed bytes still correspond to the signature calculation. It does not decide whether the terms are acceptable, whether all required parties signed, or whether an attachment referenced by the document was included. Confirm page count, appendices, exhibits, signature order, and any approval workflow separately.
Timestamp and certificate status need context
Record both the displayed signing time and the source of that time. Then review the certificate’s validity and revocation evidence in relation to that point. If the application cannot establish a reliable signing time, describe the result conservatively: the certificate may be valid now, but the available evidence may not prove its status when the document was signed.
Keep an audit record
For procurement, legal, compliance, or security reviews, retain the original file, verification report or screenshots, validation date, application name and version, warning text, and any correspondence resolving the warning. If you calculate a hash, label the algorithm and exact file used. A later hash comparison is useful only when it is made against a known, unchanged reference.
Common mistakes
| Mistake | Why it causes problems | Better practice |
|---|---|---|
| Trusting a scanned signature image | An image can be copied and does not provide cryptographic integrity. | Look for an actual embedded digital signature and certificate details. |
| Editing the file before verification | Resaving or converting it can remove, invalidate, or alter signature data. | Keep the received original untouched and work on a copy. |
| Equating an unknown certificate with fraud | The verifier may lack the issuing root or intermediate certificate. | Investigate the chain and trusted source before reaching a conclusion. |
| Equating an expired certificate with an invalid historical signature | Expiration today does not by itself establish the certificate’s status at signing time. | Review timestamp and embedded validation evidence. |
| Ignoring post-signing changes marked as allowed | Some workflows permit limited actions, but not every change is acceptable for your transaction. | Read the application’s change summary and compare it with the expected workflow. |
| Using an online upload tool for confidential files | Uploading a contract may expose sensitive information or conflict with internal controls. | Prefer approved local tools or an organizational validation service. |
When to revisit
Return to this checklist whenever a signed document is replaced, forwarded in a new format, or accompanied by a new validation warning. Recheck the file before a seasonal procurement or approval cycle, after changing PDF or document-management software, and when your organization updates its trusted certificate stores or signing policy.
Teams that receive many signed documents should maintain a short runbook. Define the approved validation applications, trusted roots, escalation contact, evidence to retain, and conditions that require approval to pause. Review the runbook when certificate authorities, signature formats, timestamp services, operating systems, or application interfaces change. Also revisit it after an incident involving an altered attachment, a revoked certificate, or a disputed signer identity.
For a final action-oriented review, use this sequence: preserve the original, validate the signature, inspect the signer certificate, check the chain and status, confirm the timestamp, compare the document contents with expectations, record the result, and escalate unresolved warnings. If the file is intended to support a credential or public verification workflow, keep the verification record aligned with the organization’s issuance and revocation process; related guidance is available in this certificate verification portal guide.