10/23/2026Digital Signing

'How to Verify a Digitally Signed PDF (and Fix "Validity Unknown")'

Gaurav Singhal

View LinkedIn

You receive a digitally signed invoice, open it in Adobe Acrobat Reader, and see a yellow warning that the signature validity is unknown. Someone in accounts asks whether the document is genuine. In most cases it is, and the fix takes a few minutes.

This guide explains what a PDF reader actually checks, what each status means, and what to do when a signature does not show as valid. It applies to any signed PDF you receive, whoever sent it.

Key takeaways

  • Verifying a signed PDF checks two things: that the document has not changed since it was signed, and that the signer's certificate chains to a root your computer trusts.
  • "Validity unknown" usually means your reader does not yet trust the root certificate, or could not finish a revocation check. It does not mean the signature is fake.
  • "Document has been modified" is the warning to take seriously. Ask the sender for a fresh copy.
  • Check the signer name and signing time yourself. A valid signature from an unexpected signer is still a problem.
  • Trust a root certificate only when you have got it from an official source.

What verifying a digital signature means

A PDF digital signature is a block of cryptographic data stored inside the file. When you open the document, your PDF reader does three things.

  1. Recalculates the document's fingerprint (a hash) and compares it with the one sealed into the signature. If they match, nothing in the signed content has changed since signing.
  2. Checks the certificate chain. It follows the signer's certificate up through the certifying authority that issued it to a root certificate, and checks whether that root is trusted on your computer.
  3. Checks validity and revocation. It confirms the certificate was within its validity period at signing time and, where it can reach the issuer online, that the certificate had not been revoked.

Step 1 proves integrity: the file is what the signer signed. Steps 2 and 3 prove identity: the signer is who the certificate says. A "validity unknown" message is almost always about steps 2 or 3, not step 1.

The signature statuses you will see

Most PDF readers show a banner at the top of the document and more detail in a signature panel. The exact wording varies by reader and version, but the meanings fall into four groups.

Valid (green tick)

The document is unchanged since signing, and the certificate chains to a root your reader trusts. This is what you want to see.

Validity unknown (yellow warning)

The document is usually unchanged, but the reader could not confirm the signer's identity. Common reasons:

  • The root certificate is not in your reader's trusted list.
  • Your computer was offline or behind a firewall, so the revocation check could not complete.
  • The reader is using its own trust list and not your operating system's certificate store.

This is the most common message, and it is usually fixable on your side.

Document modified (red or yellow, depending on the change)

The content changed after it was signed. Some changes are harmless, such as a form field filled in after signing when the signer allowed it. Others are not. If the signature panel says the document was altered after signing and you do not know why, do not rely on it. Ask the sender to send the original signed file again.

Invalid (red cross)

The signature is broken, the certificate was revoked, or it had expired at signing time. Treat the document as unverified and contact the sender.

How to fix "validity unknown"

Work through these in order. Most cases are solved by the first two.

1. Look at the signature details first

Open the signature panel and select the signature. Look at:

  • Signed by: the name on the certificate. Is it the organisation you expected?
  • Signing time: does it make sense for this document?
  • Issuer: which certifying authority issued the certificate.
  • Document integrity: the panel should say the document has not been modified since it was signed.

If the integrity check passes and the signer is who you expect, the remaining question is only whether your computer trusts the issuer.

2. Let your reader use your operating system's trust store

Many PDF readers keep their own list of trusted roots, separate from the one your operating system maintains. Your reader's preferences usually include a signature verification or trust setting that lets it also use the operating system's certificate store. If the root is already trusted by your system, turning this on is often enough. Close and reopen the PDF, then validate the signature again.

3. Trust the root certificate

If the root still is not trusted, you can add it yourself:

  1. In the signature details, open the certificate viewer and move up the chain to the top-most (root) certificate.
  2. Compare it with the root certificate published by the official authority for that certificate's country or issuer. Check details such as the name and fingerprint.
  3. If it matches, add it to your reader's trusted certificates and allow it to be used for validating signatures and certified documents.
  4. Validate the signature again.

Only trust a root you have obtained or checked against an official source. Do not trust a certificate just because a document asks you to.

4. Check your connection

If the root is trusted but the status is still unknown, the reader may not be able to reach the issuer to check revocation. Try again on a normal internet connection. In a corporate network, your IT team may need to allow access to the issuer's revocation servers.

5. Update your reader

Older versions can have outdated trust lists or weaker support for newer signature formats. Updating often clears odd results.

What verification does not tell you

A green tick confirms that a particular certificate signed this exact file and that nothing has changed since. It does not confirm:

  • That the content is correct. A signed invoice can still have the wrong amount.
  • That the signer had authority to approve that specific document inside their organisation.
  • What a document needs to be accepted for a particular purpose. Check with your advisor on what your documents require.

So treat verification as one check among your normal ones: right supplier, right amount, right reference, signed by the organisation you expect.

A simple checklist for accounts teams

If your team receives many signed PDFs, a short routine saves time:

  1. Open the PDF in a reader that shows signature details.
  2. Confirm the document has not been modified since signing.
  3. Confirm the signer name matches the supplier or sender.
  4. If it says validity unknown, check the trust store and root certificate once on that machine. Future documents from the same issuer will then usually show as valid.
  5. If a document shows as modified or invalid, ask for a fresh copy before processing it.

Fixing trust once per machine removes most of the repeat questions.

If you are the one sending signed PDFs

Recipients see a clean result when the signing certificate comes from a certifying authority their software already trusts, and when the document is not edited after signing. If you sign PDFs one at a time with a USB token, or want to sign at volume without one, read why digitally signing a PDF is still so hard and how to digitally sign PDFs in bulk.

Ambill Sign applies your organisation's own document signer certificate (.pfx) to PDFs. PumPumPum, Kazam and Workie already use it to sign their invoices in Ambill in batches, with no per-signature fees. Signing any PDF and a developer API are coming soon. To understand the certificate itself, see what a document signer certificate is.

Sign documents your customers can verify

If you send signed invoices or other PDFs and want a simpler way to sign them with your organisation's certificate, we can help.

Talk to us about Ambill Sign

Building your own product or workflow and want to sign PDFs from code? Request API early access

FAQ

Does "validity unknown" mean the signature is fake?

Usually not. It most often means your reader does not yet trust the issuer's root certificate, or could not complete a revocation check. Check the signature details: if the document is unmodified and the signer is who you expect, fixing trust on your computer normally turns the status valid.

Can I verify a signed PDF without Adobe Acrobat Reader?

Yes. Many PDF readers and some browsers show signature details, though support varies. Whichever tool you use, the same two checks matter: the document is unchanged since signing, and the certificate chains to a root you trust.

Why does the same PDF show as valid on one computer and unknown on another?

Trust is set per computer and per reader. One machine may already trust the root certificate, or use the operating system's trust store, while the other does not.

What should I do if the document shows as modified?

Do not rely on it. Ask the sender for the original signed file. If they confirm it was changed after signing, they should sign the final version again.

Does a valid signature mean the document meets every requirement?

No. It proves who signed the file and that it has not changed since. Check with your advisor on what your documents require.