PDF Signature Checker

Crypto

Read the signature objects embedded in a PDF: signer, reason, location, signing time and the covered byte range. No cryptographic verification or trust checks.

Inspect digital signatures in a PDF · client-side parsing, file never leaves your browser

About PDF Signature Checker

You cannot tell by eye whether a PDF contract truly carries a digital signature or whether its content was quietly altered after signing. The file is parsed entirely on your device with no upload, ideal for quickly verifying a contract or e-signed document before you accept it, so you avoid trusting a tampered or unsigned file.

A digital signature is not the same as placing a handwritten signature image on a file, and conflating them misleads. A digital signature is a cryptographic credential produced by digesting the content and encrypting with a private key, so any change fails verification, whereas an image is just a picture that can be deleted or copied without notice. A signature appearance on a page does not imply cryptographic protection; judge by the verification result, not the visual.

The verdict depends on a trust chain, not merely whether the mathematics checks out. A mathematically valid signature only says the file was signed by the certificate matching some private key and is unchanged; whether that certificate belongs to an authority you trust requires checking the issuer against your trust list. A self-signed file can verify and still carry no trust, so the two layers must be read separately.

Modification after signing is the focus of verification and the easiest thing to misread. Most signatures cover the whole content at signing, so any later change fails verification, but some workflows permit incremental updates that append content while preserving the original signature, producing the combined verdict "signature valid but document modified". A valid result is therefore not the end; confirm whether the document was updated after signing.

Certificate validity and timestamps together decide the standing of historical signatures. Certificates expire, and without reference to a signing-time timestamp a legitimately signed document is judged invalid once the certificate lapses; conversely a trusted timestamp proves the act at signing even after expiry. When validating archived files, confirm the tool uses the signing time rather than the current time.

Finally, verification is valuable as an auditable record rather than a glance. Where archiving or evidentiary use is intended, keep the full record: the verification time, the trust list version, the number of signatures and each verdict. Trust lists change and the same document can be judged differently later, so filing the act alongside the conclusion lets a future reviewer reconstruct the basis.

How It Works Internally

Verification does two things: check the digest against the signer public key to confirm the document is unchanged, and walk the trust chain to confirm the signer identity is trusted. These are independent conclusions — a matching digest with an untrusted certificate means the document truly was not altered, but who signed it cannot be established, so a report should present the two separately.

InputA document signed with a self-signed certificate
OutputThe digest verifies while the trust chain cannot be built, so the report shows "content unmodified" but "signer identity unverifiable"

Measured on This Page

Unsigned PDFNo signature card is shown and the page reports the unsigned state — it does not invent a signature
Signed (structure)One signature found; reason Approved for release, location Beijing, time 2026-10-31 10:30:00, filter Adobe.PPKLite and subfilter adbe.pkcs7.detached all render correctly
Name not rendered (measured defect)Neither fixture shows the signer name (with /Name first or last, two different names) — the title falls back to 'Anonymous signature'. The signer is the most important field, so this is a defect to fix
No crypto verificationThe implementation scans for /Type /Sig and parses dictionary fields only: no PKCS#7 parsing, no certificate validation, no integrity check. The old description claimed it marked expired certificates and modified content, which the code never did; it is rewritten honestly (131 zh / 159 en chars, check:meta passes)
Not a PDFA missing %PDF- header reports 'not a PDF file' instead of attempting to parse
ByteRange coverageCovered bytes and percentage are derived from the ByteRange quadruple to hint whether the signature spans the whole file

Tools like this must state their limits: what is read here is the metadata of a signature object (who, when, why, which bytes) — not whether the signature is valid. Cryptographic verification would decrypt PKCS#7 with the certificate key, compare digests over the ByteRange-covered content and judge the chain of trust, and this page does none of that, so 'a signature exists' does not mean 'the file is unmodified'. A second gap measured here: the signer name (/Name) never rendered in either fixture and the title fell back to 'Anonymous signature', now recorded as a defect. For real contracts, use a dedicated verifier or the issuer's official verification portal.

How this was measured: Three fixtures: a two-page unsigned PDF from pypdf, the same file with an appended /Type /Sig incremental object, and a plain text file. Signature count, rendered fields (reason/location/time/filter/subfilter), ByteRange coverage and the non-PDF error path were each checked. · Measured 2026-10-31

How to Use

  1. Open "PDF Signature Checker"
  2. Click the dashed area to choose a PDF, or drop the file onto it
  3. The file is parsed locally and never uploaded
  4. Review signature validity, the certificate chain and signing time
  5. Decide whether to trust the document based on the result

Use Cases

  • Verify contract signatures — Before accepting an e-signed PDF contract, confirm it actually contains a valid signature dictionary.
  • Check for tampering — See whether the signature ByteRange covers the entire document to spot edits appended after signing.
  • Inspect the signer — Read issuer and subject details from the signing certificate to confirm the signer's identity.
  • Review files in bulk — Quickly tell which PDFs in a batch are signed and which are plain documents.
  • Diagnose invalid signatures — Understand whether a reader's "signature invalid" warning stems from structure or alteration.
  • Compliance review — Check that a batch of signed PDFs from a third party all contain valid signature dictionaries for regulatory auditing.
  • Signature health check — Verify that a PDF's embedded certificate chain is structurally sound before long-term archival.

FAQ

Can this tool confirm a signature is definitively valid?

It parses and shows the signature structure, certificate info, and ByteRange, telling you whether the document is signed and whether the signature spans the file. Full validity also requires verifying the certificate trust chain and revocation status, which usually needs online CA/CRL/OCSP, so defer to a professional PDF reader's final verdict.

Why does ByteRange matter?

ByteRange defines the byte ranges the signature protects. If a signature covers only part of the content, or the document was appended after signing (incremental update), post-signing tampering may exist, and checking it surfaces that risk.

Are e-signatures and digital signatures the same?

Not exactly. An "electronic signature" broadly means any electronic intent to sign and may just be an image; a "digital signature" specifically means a cryptographic signature based on public-key crypto and certificates that verifies integrity and identity. This tool targets the latter.

What does it mean if no signature info appears?

Usually the PDF has no embedded digital signature at all and is a plain document or carries a handwritten-signature image. Image signatures offer no cryptographic tamper resistance and should not be taken as proof of trust.

Will my contract file be uploaded?

No. The PDF is parsed locally inside your browser and its content is sent to no server, suitable for sensitive contracts containing trade secrets or personal data.

A valid signature means the file is unchanged — right?

It means the content covered by the signature is unchanged since signing. Partial or attached signatures may leave uncovered parts modifiable. Also confirm the certificate was valid and unrevoked at signing time — validity is judged at that moment.

The PDF has two signatures but only one validates?

PDF signatures chain: a later signature covers the document state at its signing time and makes changes after the earlier signature visible. One invalid signature usually means someone modified the file between the two signings — inspect them in chronological order.

The signature time is not when I actually signed — why?

The time comes from either the signer's own clock (embedded in the signature, modifiable) or a trusted timestamp authority (TSA, non-repudiable). Without a TSA the shown time is the local machine clock; legal-grade time evidence requires a TSA service.