You sign a PDF, send it to a client, and they reply with a screenshot: a yellow bar in Adobe Acrobat that says "At least one signature has problems", and in the Signatures panel, "Signature validity is UNKNOWN". The document was not tampered with. In almost every case the problem is trust: the reader's copy of Acrobat cannot connect your certificate to a root it already trusts. This guide explains what Acrobat is checking, how to tell which check failed, and how to fix it on both the signer's side and the reader's side.
What Acrobat checks when it opens a signed PDF
For every signature, Acrobat answers three separate questions:
- Integrity: have the signed bytes changed since signing? If yes, you get a red X and "altered or corrupted". That is a different problem, covered in our post on documents altered after signing.
- Identity: does the signer's certificate chain up to a root certificate that this copy of Acrobat trusts?
- Validity at signing time: was the certificate valid (not expired, not revoked) at the moment of signing, and can Acrobat prove that moment?
"Validity UNKNOWN" means question 1 passed but question 2 or 3 could not be answered. Acrobat is not saying the signature is fake. It is saying "I cannot confirm who this is."
Step 1: read the Validity Summary
Open the PDF, click Signature Panel, expand the signature and click Signature Details > Certificate Details (or right-click the signature and choose Show Signature Properties). The summary at the top tells you which part failed. Typical wording and meaning:
| Message in Signature Properties | What it usually means |
|---|---|
| "The signer's identity is unknown because it has not been included in your list of trusted certificates and none of its parent certificates are trusted certificates" | The root CA is not in Acrobat's trust store. Most common cause. |
| "Signature validity is unknown" plus "Revocation checking was not performed" | Acrobat could not reach the CA's OCSP or CRL server and no revocation data was embedded. |
| "Signing time is from the clock on the signer's computer" | No trusted timestamp. Not an error on its own, but it weakens validation later. |
| "The signer's certificate has expired" or "is not yet valid" | Certificate dates do not cover the signing time, or there is no timestamp and the certificate has since expired. |
| "Invalid policy constraint" / "Error encountered while building certificate chain" | An intermediate certificate is missing or Acrobat's trust settings for that root exclude document signing. |
Cause 1: the certificate is not on a list Acrobat trusts
Acrobat does not use the Windows certificate store by default. It trusts certificates that chain to roots in the Adobe Approved Trust List (AATL) and, if enabled, the EU Trusted Lists (EUTL). Document-signing certificates from CAs such as GlobalSign, SSL.com, Sectigo and DigiCert are typically on the AATL. Certificates from a company's internal CA, self-signed certificates, many national CAs and all code-signing or TLS certificates are not.
Fix on the signer's side (the real fix)
- Sign with a document-signing certificate from an AATL member CA. Check the CA's product page: it should say "Adobe AATL" or "Adobe approved". These certificates are issued on a hardware token or HSM by CA policy.
- Do not reuse a code-signing or SSL certificate for PDFs. Even if it comes from a trusted CA, its key usage and policy are wrong for document signing and Acrobat will flag it.
- Make sure the signing software embeds the full chain (signer certificate plus intermediates). A chain with a missing intermediate is a common reason for "Error encountered while building certificate chain".
Fix on the reader's side
If the signer's certificate is from an AATL CA but the reader still sees UNKNOWN, their trust list is probably out of date or blocked:
- In Acrobat or Reader, open Menu > Preferences > Trust Manager in the current Acrobat interface on Windows, or Edit > Preferences > Trust Manager in the classic interface. On macOS, use Acrobat > Preferences (or Acrobat Reader > Preferences).
- Under Automatic Adobe Approved Trust List (AATL) updates, tick Load trusted certificates from an Adobe AATL server and click Update Now.
- Do the same under Automatic European Union Trusted Lists (EUTL) updates if the signer uses an EU qualified certificate.
- Close and reopen the PDF.
In managed environments, a proxy or firewall can stop Acrobat from downloading the lists or reaching OCSP and CRL servers. IT can allow the Adobe trust list URLs and the CA's revocation URLs, or push the trust settings through Acrobat's enterprise configuration.
Trusting an internal or national CA manually
For a certificate from your own corporate CA or a national CA not on the AATL, each reader can add the root once:
- Right-click the signature, choose Show Signature Properties > Show Signer's Certificate.
- In the left pane, select the top certificate in the chain (the root).
- Open the Trust tab and click Add to Trusted Certificates.
- Tick Use this certificate as a trusted root and Signed documents or data. Click OK and revalidate.
Only do this after confirming the certificate's fingerprint with its owner over a separate channel (a phone call, not a reply to the same email). Trusting the leaf certificate instead of the root works for that one signer only and has to be repeated when their certificate renews.
Cause 2: revocation status could not be checked
Acrobat wants to know whether the certificate was revoked. If the PDF does not carry the OCSP response or CRL, Acrobat tries to fetch it online. Offline readers, blocked networks or a CA that has retired an old OCSP endpoint all lead to "revocation checking was not performed".
The fix is on the signing side: embed the revocation data when you sign, which is what LTV (long-term validation) means. In Acrobat itself this is Menu > Preferences > Signatures > Creation & Appearance > More > Include signature's revocation status (classic interface: Edit > Preferences, same path after that). For an already signed PDF, a reader with network access can right-click the signature and choose Add Verification Information, then save. Acrobat only offers that option when the signature is valid and trusted through a certificate chain (not a self-signed or manually trusted certificate) and the verification time is not set to the current time. We cover LTV in detail in signature not LTV enabled.
Cause 3: no timestamp, and the certificate has since expired
Without a trusted RFC 3161 timestamp, the only proof of signing time is the clock of the signer's computer, which Acrobat does not trust. Once the certificate expires, many validators evaluate the signature at the current time and report it as invalid or unknown. Add a timestamp from your CA's timestamp server (TSA) when you sign. It cannot be added to an old signature after the certificate has expired, so this needs to be part of the signing setup from day one.
Cause 4: verification preferences on the reader's machine
Two Acrobat settings change the result for the same file:
- Menu > Preferences > Signatures > Verification > More > Verify signatures using (classic interface: Edit > Preferences; macOS: Acrobat > Preferences): "Time at which the signature was created", "Secure time (timestamp) embedded in the signature", or "Current time". If you compare screenshots between colleagues, make sure they use the same option.
- Require certificate revocation checking to succeed whenever possible during signature verification: when ticked and revocation data is unreachable, the result degrades to UNKNOWN.
Do not "fix" a real trust problem by loosening these settings on one machine. Your recipients will not have the same settings.
A quick checklist
- Certificate is a document-signing certificate from an AATL CA.
- Full chain embedded at signing.
- RFC 3161 timestamp from the CA's TSA.
- Revocation data embedded (LTV).
- PDF not modified after signing (signature is the last step).
- Reader's AATL list updated, network allows trust list and OCSP/CRL access.
When all six are true, Acrobat shows "Signed and all signatures are valid" with a green tick on any reader's machine, without anyone touching their trust settings.
How OneSigner handles it
OneSigner signs PDFs with the certificate on your own USB token or HSM, so the trust result depends on that certificate: use an AATL document-signing certificate for a green tick everywhere. Each PDF signing profile has a Timestamp URL and an LTV option; with both set, every document signed through the watched folder, REST API or portal carries a trusted signing time and embedded revocation data. Signing is incremental, so earlier signatures stay intact. See signing profiles for the settings, or choosing a USB token and CA if you are still picking a certificate.



