SSOGEN / Free tools / Java keystore viewer (JKS and PKCS12)

SSOGEN

Java keystore viewer (JKS and PKCS12)

This java keystore viewer opens a JKS or PKCS12 file in your browser and lists every alias with its type, subject, expiry date and fingerprint. The file never leaves your computer.

Open a JKS or PKCS12 file here

Drop a .jks, .p12 or .pfx file, or use the second tab to paste keytool -list -v output. Nothing is uploaded.

  • Load an Acme JKS. One key pair and one trusted certificate. Password changeit.
  • Load an Acme PKCS12. A key pair with a two-certificate chain. Password changeit.

A PKCS12 file needs its password. A JKS file lists without one; with a password it also checks the integrity digest. The password stays in this tab's memory.

Private by design. Nothing is uploaded, and the page makes no network request when you open a file. Private keys are not decrypted or shown: a key entry is listed as "private key, not opened". Certificates are public information.

To read an exported certificate field by field, use the certificate decoder.

Why it is safe to open here

  • What is read. The aliases, entry types, certificates and chain.
  • What is never read. Private keys. Key bags are not decrypted.
  • What you can check. Open the browser network tab and load a file: no request appears. The page works offline after it loads.

What each format reveals

A JKS file lists its certificates without a password; a PKCS12 file needs one. JKS keeps certificates in the clear and protects only private keys. PKCS12 encrypts the certificate bags too.

Format Starts with Password to list This page
JKS FEEDFEED No Lists every entry.
PKCS12 (.p12, .pfx), AES-256 ASN.1 sequence Yes Lists every entry. This is the format JDK 21 and OpenSSL 3 write.
PKCS12, 3DES and RC2-40 ASN.1 sequence Yes Names the cipher and gives the command to re-save it.
JCEKS, BKS, BCFKS CECECECE (JCEKS) Varies Not read here. Paste keytool -list -v output instead.

Convert and export

Export one certificate with the Copy PEM button. To convert a whole file, use keytool.

Before: a JKS file, acme.jks. The certificate you need is inside it.

After: a PEM file. Run keytool -exportcert -alias acme-web -keystore acme.jks -rfc -file acme.pem.

Before: a .pfx file from a Windows export, and an application that needs JKS.

After: a JKS file. Run keytool -importkeystore -srckeystore acme.pfx -srcstoretype pkcs12 -destkeystore acme.jks -deststoretype jks.

Before: a CA certificate in PEM form, acme-ca.pem, that Java must trust.

After: a JKS truststore. Run keytool -importcert -alias acme-ca -file acme-ca.pem -keystore acme.jks -storetype JKS.

The keytool command generator builds these commands for your file names and options.

When a file will not open

Message Cause Fix
Wrong password The PKCS12 integrity check failed. Re-enter the password. JKS needs none to list.
Legacy cipher (3DES, RC2-40) An older JDK, OpenSSL 1.x or a Windows export wrote the file. Run keytool -importkeystore -srckeystore old.p12 -srcstoretype pkcs12 -destkeystore new.p12 -deststoretype pkcs12, then open new.p12.
Format not read The file is JCEKS, BKS or BCFKS. Run keytool -list -v and paste the output on the second tab.

For a PKIX path building failed error, open the truststore here and look for the issuer; the error guide explains it.

Need to edit a keystore on your desktop? KeyStore Explorer is an open-source graphical tool for that. This page is read-only.

Questions people ask

Where are keystore files stored?

There is no fixed location. The application’s configuration names the file, so look in its settings or start-up options. The JDK’s own default truststore is the cacerts file under the JDK’s lib/security folder. The Java cacerts guide lists the exact path for each JDK version and operating system.

Is JKS obsolete?

JKS is a legacy format, not a broken one. JEP 229 made PKCS12 the default keystore type from JDK 9, and keytool now recommends migrating. Existing JKS files keep working, because Java detects the format before loading. New keystores should use PKCS12, which supports stronger algorithms.

How to create a keystore password?

Choose it when you create the keystore. Keytool prompts for a store password, or you pass -storepass. Use a long, random value and keep it in a secret manager. Never commit it to source control. The default changeit belongs only to the cacerts file.

Sources, all read 2026-11-17: JEP 229: Create PKCS12 Keystores by Default; OpenSSL 3.0 openssl-pkcs12 manual; the PKCS12 properties in the java.security file of JDK 21.0.12 and its keytool output; KeyStore Explorer.