Opening your e-Aadhaar PDF and seeing a message like "Signature Not Verified" or "At least one signature has problems" is confusing — but almost always harmless. This guide explains exactly what these messages mean, why UIDAI's signature isn't automatically trusted, and how to fix it in seconds using VerifySign.in.
These two phrases are often used interchangeably, but technically they mean slightly different things in PDF reader terminology:
"Signature Validity Unknown" (yellow question mark): The PDF reader could not determine whether the signature is valid because it doesn't recognise the signing certificate's root authority. The signature has not been verified — but it also hasn't failed verification. This is the most common status for Indian government PDFs.
"Signature Not Verified" or "At Least One Signature Has Problems": This can mean the same trust-store issue as above, OR it can indicate the PDF reader attempted verification and encountered a problem — such as a broken certificate chain or an unreachable OCSP server. Again, in most cases with Aadhaar, this is a trust configuration issue, not document fraud.
"Signature Invalid" (red X): This is the serious one. It means the mathematical signature check failed — the document has been altered since signing. This is rare for properly downloaded Aadhaar PDFs and should prompt re-downloading from the official UIDAI website.
UIDAI uses digital signing certificates issued under India's NIC (National Informatics Centre), which operates under the CCA (Controller of Certifying Authorities) — the apex body for digital certificates in India under the IT Act, 2000. This hierarchy is legitimate, government-backed, and legally recognised.
However, Adobe Acrobat and most PDF readers ship with the Adobe Approved Trust List (AATL), which includes commercial CAs from the US, Europe, and some other countries, but does not include India's CCA root. Since the PDF reader can't find the root in its trusted list, it doesn't automatically trust the UIDAI signature — resulting in "Validity Unknown" or "Not Verified."
The full certificate chain for an e-Aadhaar signature typically looks like this:
CCA India Root CA (Root) → NIC Sub-CA (Intermediate) → UIDAI Signing Certificate (Leaf)
For PDF readers to automatically trust this chain, the "CCA India Root CA" must be in the trust store. It isn't — hence the problem. VerifySign.in has India's full PKI hierarchy built into its verification engine.
Manual Certificate Installation (Hard Way): You can download the CCA India root certificate from india.gov.in/certificates, then import it into Adobe Acrobat via Edit → Preferences → Trust Manager → Import. This requires admin privileges on your machine, must be repeated on every device, and is version-dependent. It typically takes 15–30 minutes for a non-technical user.
VerifySign.in (Easy Way): Upload your Aadhaar PDF to verifysign.in. VerifySign.in validates the signature server-side against the complete NIC/UIDAI/CCA certificate chain and returns an LTV-enabled PDF that permanently shows a green tick — on any device, in any PDF reader, without any certificate installation. Total time: under 60 seconds.
VerifySign.in is dramatically faster for a one-off verification. Manual certificate installation is a one-time setup that helps all future Indian government PDFs on that specific machine. If you regularly work with many Indian government PDFs on a fixed personal computer, the manual method may be worth the setup time. For most users — especially those using multiple devices or verifying occasionally — VerifySign.in is the clear winner in speed and convenience.
Additionally, VerifySign.in's LTV-enabled output works permanently on any device — so even if you share the verified PDF with someone on a different machine, they'll see the green tick without any setup.
Instant digital signature verification for any government PDF — free, secure, no software needed.
Go to VerifySign.in →