← Blog

How to Add NIC Root Certificate to Adobe Reader (And Why VerifySign.in is Easier)

The "Signature Validity Unknown" message on Indian government PDFs in Adobe Reader is caused by one thing: Adobe doesn't have the NIC (National Informatics Centre) root certificate in its trust store. The manual fix exists — but it involves several technical steps. This guide walks you through both: the full manual process and the one-click alternative using VerifySign.in.

Step 1: Download the CCA/NIC Root Certificate

Go to the India PKI website at cca.gov.in and navigate to the "Root Certifying Authority" section. Download the CCA India 2022 root certificate (or the most current version) in .cer format. You may also need to download intermediate certificates if your document's signing chain passes through NIC's sub-CAs. Save all certificate files to a known location on your desktop.

Step 2: Open Adobe Reader's Certificate Management

Open Adobe Acrobat Reader. Go to Edit → Preferences (or Acrobat → Preferences on macOS). In the left panel, select Signatures. Under the "Verification" section, click More. A new dialog opens — click Manage Trusted Identities. This is where you'll import the NIC certificate.

Step 3: Import the Root Certificate

In the Manage Trusted Identities dialog, click Add Contacts. Browse to the .cer file you downloaded in Step 1. Select the file and click Open. Adobe will display the certificate details — the issuer should read something like "CCA India 2022" or "NIC CA 2017." Click on the certificate, then click Trust.

Step 4: Set Trust Flags

In the Trust Settings for this certificate, check "Use this certificate as a trusted root". Also check "Certified documents" if you want Adobe to trust documents certified with this root. Click OK to save. If you downloaded intermediate certificates, repeat Steps 3 and 4 for each one — but do not mark intermediate certs as "trusted root," only the root CA certificate should have that flag.

Step 5: Restart and Re-verify

Close Adobe Reader completely and reopen it. Now open your government PDF. If you've imported the correct root and any required intermediates, the signature panel should now show a green "Signature Valid" status. If it still shows Unknown, you may be missing an intermediate certificate in the chain — check the signature's certificate path for hints.

The Problem with This Approach

Even after completing all five steps, this fix is per-machine and per-application. The recipient you share the PDF with will still see "Unknown" in their unmodified Adobe Reader. Mobile apps can't be fixed this way at all. And if a new government CA is introduced (which happens), you'll need to repeat the process. That's a lot of maintenance for a one-time document check.

VerifySign.in Does All of This Automatically

VerifySign.in performs the same cryptographic verification, but server-side and in seconds — no certificate downloads, no Adobe preference panels, no trust flag configuration. The result is embedded directly into your PDF as LTV data, making it universally valid across all readers. The fix travels with the PDF, not with your machine.