How to use
- Drop a PDF on the page or click to choose one. Any PDF that carries a digital signature works: contracts, official letters, e-invoices. If you have no signed PDF at hand, the sample buttons show what a result looks like.
- Every signature in the file is found and gets its own card. The sentence at the top of a card is the conclusion for that signature.
- Use the table in the card to read document integrity, signature value, changes after signing, signing time and signer certificate details.
- If there are several signatures they are numbered in the order they are stored in the file, and the card says whether a later signature covers an earlier one.
Files over 100 MB are not checked.
What this result means and what it does not
The tool checks exactly two things: whether the document changed after it was signed and whether the signature value is mathematically correct. A “match” does not mean the signer is a trustworthy person or organization.
Anyone can create a certificate and sign with it. A self-signed certificate that carries someone else’s name still produces a perfectly matching signature. For that reason the tool does not check:
- whether the authority that issued the signer certificate can be trusted (certificate chain, trust lists)
- whether the certificate has been revoked (OCSP, CRL)
- whether a timestamp authority’s time is genuine
- whether a national certificate scheme’s policy, such as Korean 공동인증서, was followed
- whether content added after signing is a change the document allows (form filling and so on)
To learn who signed and whether it has legal effect, use the trust check of a PDF viewer, the issuing authority’s verification service, or a professional. The result is for reference and does not judge legal effect.
What is checked
| Item | How |
|---|---|
| Document integrity | Hash the bytes named by the ByteRange and compare with the messageDigest recorded in the signature |
| Signature value | Verify the signature over the signed attributes with the public key of the signer certificate (RSA PKCS#1 v1.5, RSA-PSS, ECDSA P-256, P-384, P-521) |
| Changed after signing | Whether the ByteRange reaches the end of the file. If bytes follow, the added size is shown, and whether a later signature covers them |
| Signing time | The signingTime attribute and the /M entry of the signature dictionary. Both are written by the signer, so neither is a verified time |
| Signer certificate | Subject, issuer, validity, serial number, key type, SHA-256 fingerprint |
SHA-1, SHA-256, SHA-384 and SHA-512 are supported. For MD5 only the hash comparison runs and the signature value cannot be verified. Signatures that use SHA-1 or MD5 get a warning.
How a signature covers the file
A PDF signature signs a hash of the whole file, leaving out the spot where the signature value itself is stored. The /ByteRange entry names the covered parts as four numbers: start, length, start, length.
The built-in sample records [0, 747, 4749, 182]. The tool hashes 747 bytes from offset 0 followed by 182 bytes from offset 4749, and skips the 4002 bytes in between (4000 hex digits for the signature plus two angle brackets). The two parts add up to the file size of 4931 bytes, so the signature covers the file to its end.
When a PDF is saved again after signing, the new content is usually appended to the end as an incremental update, which leaves bytes after the signed range. The signed range is untouched, so the hash still matches, but the result reads “Changed after signing: Yes”. A document signed by several people in turn also has bytes after the first signature, and the card says so when a later signature covers the earlier range.
Reading the result sentences
| Result | Meaning |
|---|---|
| The signature value matches and nothing changed after signing | Hash and signature value are correct and the signature reaches the end of the file |
| The signed part is unchanged, but content was added after signing | The signed range is correct but an incremental save or another signature follows |
| The signed part was changed after signing | The computed hash differs from the hash in the signature |
| The signature value does not match the signer public key | The hash is right but the signature value fails verification |
| Some items could not be checked | The certificate is missing from the signature or the algorithm is unsupported |
| The signature structure is invalid | The signature value is empty or the ByteRange looks wrong |
If the part left out of the ByteRange is not where the signature value sits, the signature is reported as having a bad structure. A normal PDF never looks like that, and it can be a sign that a signature was swapped onto different content.
Example: change a single character
The two sample buttons on the page show it. The samples are fake documents signed with a throwaway test certificate made for this tool (subject C=KR, O=Toolulah Test, CN=Hong Gildong Test, RSA 2048 bits).
| Sample | Hash in the signature | Computed hash | Result |
|---|---|---|---|
| Signed sample | b8a2…2818 | b8a2…2818 | Match |
| Sample with the amount changed from 1 to 9 | b8a2…2818 | 496f…bbab | Signed part changed |
Changing one character gives a completely different hash. In the second sample the signature value row still says “Match”: the hash recorded in the signature does belong to the signer. The fact that the document no longer equals that hash shows up in the document integrity row.
Supported formats and limits
- Formats: adbe.pkcs7.detached, ETSI.CAdES.detached (PAdES), adbe.pkcs7.sha1 and document timestamps (ETSI.RFC3161). The old adbe.x509.rsa_sha1 format cannot be read.
- In an encrypted PDF the signature data itself is not encrypted, so a check is attempted. Text entries such as the reason or name may look garbled, and a copy saved after removing the password has a broken signature, so upload the original.
- A signature field with an empty signature value is reported as never signed.
- A PDF that only carries a handwritten picture or an image stamp has no signature to find. A visible signature picture is not a digital signature.
- If the file is cut off or damaged so that the signature trace cannot be read, the tool says so.
- Ed25519 signatures and a few rare algorithms are not supported.
Frequently asked questions
If the signature matches, can I trust the document?
No. A match means the document did not change after signing and the signature value is correct. Who actually signed is a separate question. A self-signed certificate gets a warning, but even for a certificate from an outside authority this tool does not verify that authority. For anything important, check the signer with a PDF viewer’s trust check or the issuing authority’s verification service.
It says content was added after signing. Is the file forged?
Not necessarily. Filling in a form, adding a comment and saving, or another person signing afterwards all leave bytes after the signed range. The signed range is untouched so the hash matches. The tool cannot tell what was added. If it matters whether the content differs, compare with the original using Compare PDFs.
Acrobat says the signature validity is unknown. Why does this tool say match?
On top of the math, Acrobat checks whether the authority behind the certificate is on its own trust list. If it is not, you get “unknown” even for a perfectly intact document. This tool does not look at trust lists and only shows mathematical agreement, so the two can differ.
Does it work for PDFs signed with a Korean 공동인증서?
If the signature data is PKCS#7 (CMS) using RSA or ECDSA, the hash and the signature value are checked. The certificate policy, chain and revocation status are not, so the tool never declares a “valid 공동인증서 signature”.
Can I trust the signing time?
The time in the signed attributes and the /M entry come from the signer’s device clock and can be set to anything. A trustworthy time comes from a timestamp token issued by a timestamp authority. This tool only reports that a token exists and does not verify the authority.
Is my file uploaded?
No. Hashing and signature verification both run in your browser and the file never leaves your device.
Related tools
To add a signature, use Sign PDF. To read document properties, use PDF Metadata Editor. To inspect a file whose signature is broken, try Repair PDF. To read a certificate in PEM form, use SSL Certificate Viewer. To compute a hash yourself, use Hash Generator. To compare content before and after signing, use Compare PDFs.
The file you choose is processed only in your browser and is never sent to a server.