AuraDoc
Sign inSign up

Blog

How to verify a signed PDF

Check who signed a PDF, whether it changed after signing and when the timestamp was issued, without storing the file in your workspace.


A signed PDF arrives in your inbox. It looks finished, with a name and a date on the last page, but a picture of a signature proves very little. What matters is the cryptographic signature stored inside the file: who produced it, whether the document changed afterwards and when the signing happened. AuraDoc includes a verification tool that reads those details and explains them in plain language, so anyone on your team can check a document before it is filed, paid or acted on.

What the verification tool checks

Upload a PDF to the verification tool and AuraDoc looks for every digital signature it contains. For each one it reports whether the signed bytes are still intact, which certificate was used and who it was issued to, and whether a trusted timestamp is attached. If the file was edited after signing, the result says so clearly instead of hiding the problem behind a green tick. A document can carry more than one signature, and each is listed separately so you can see the full history.

The check is read-only. The file you upload is examined and then discarded; it is not saved in your workspace, added to search or shared with anyone. That makes the tool safe to use on documents that arrive from outside, such as a contract countersigned by a supplier or a certificate sent by a public office. The tool reads standard PDF signatures, so it is not limited to files signed in AuraDoc. When you do want to keep the file, upload it to a folder in the usual way after the check.

Signatures made with AuraDoc

Documents signed through electronic signatures with a one-time code carry a PAdES seal and when the timestamp service was available, a timestamp from a timestamp authority. A SHA-256 hash of the audit trail is embedded with the seal, so the record of who was invited, who confirmed the code and when each person signed is tied to the exact file.

Some teams already hold their own digital certificate, issued as a .p12 or .pfx file. The PDF tools can apply that certificate to a document directly, which is useful for invoices, reports and letters that your organization signs on its own behalf. The signed file can then be checked with the same verification tool, by you or by the person who receives it.

Building a habit of checking

Verification works best as a routine step rather than an emergency measure. A common pattern is to check every signed contract when it comes back, and only then move it into the folder where approved agreements live. Because the result is immediate, the check adds seconds to the process, and it catches the rare file that was altered, re-saved by a tool that broke the signature or signed with an expired certificate.

Before sharing a signed document further, it can also help to look at what else the file contains. The PDF tools can remove metadata and embedded JavaScript, and sanitize a file received from outside. Keep in mind that any change to a signed PDF invalidates its signature, so clean a copy or do the cleaning before signing, never after. The same applies to redaction before sharing: redact first, then sign.

Signing and verification belong to the same set of controls as roles, audit trails and encrypted connections (TLS). Together they let you answer the questions an auditor, a client or a court may ask: who approved this document, when, and has it changed since? If you are new to the platform, start with a document you signed yourself and run it through the tool to see what a healthy result looks like. More articles on the topic are collected under the e-signature tag.

Back to the blog