KeyStore Studio

Opens Java keystores (JKS, JCEKS) and PKCS#12 (.p12 / .pfx) and lists each entry’s alias and type, the certificate chain’s subject, issuer and expiry (expired and within 30 days are highlighted), key type and size, signature algorithm, SHA-256 fingerprint and SANs. For private keys it shows only the type and size: the key itself is never displayed or exported. For a single PEM or .cer file use the Certificate, CSR & PEM Studio.

On-device・No uploadMobile friendlyWorks offline

Your files and input are processed only inside your browser on this device and are never uploaded to our servers.

Choose a keystore (.jks / .jceks / .p12 / .pfx)

The file is not sent anywhere. Up to 10 MB and 1,000 entries.Accepts: JKS / JCEKS / KEYSTORE / P12 / PFXUp to 10 MB per file

Used only for the integrity check and for decrypting encrypted parts. It is not stored or put in the URL. Certificates can often be listed without it.

How to use

  1. server.p12 / app.jks

    Open a keystore

  2. Certificates per alias

    Check aliases, expiry and keys

  3. cert.pem (no private key)

    Save certificates as PEM

Open a keystore, check each alias’s certificates and expiry, then save certificates as PEM
  1. Choose or drop a keystore file (.jks / .jceks / .p12 / .pfx), or press “PKCS#12 sample” or “JKS sample”.

  2. If you know the password, enter it and press “Analyze” (Ctrl/⌘+Enter also works). It is used for the integrity check and for decrypting encrypted parts.

  3. Under “Integrity check”, see whether the JKS SHA-1 digest or the PKCS#12 MAC matches. A mismatch means a wrong password or a file that was altered or damaged.

  4. For each entry, check the type (private key with chain, trusted certificate …), expiry, key type and size, SHA-256 and SANs. Expired and within-30-days certificates stand out.

  5. Copy or save any certificate as PEM. Private keys cannot be extracted.

What it does

JKS, JCEKS and PKCS#12 in one view

The format is detected from the first bytes (0xFEEDFEED for JKS, 0xCECECECE for JCEKS). Aliases, types, creation dates (JKS and JCEKS only) and certificate chains are shown the same way. The JKS layout follows the OpenJDK implementation (there is no official specification).

Expiry stands out

Each certificate shows its validity and days left; expired and within 30 days are marked with a warning colour and a badge. Days left use your device’s current time.

Integrity check

JKS and JCEKS are checked against the trailing SHA-1 digest, and PKCS#12 against its MAC (HMAC-SHA-1 / 256 / 384 / 512 with the RFC 7292 Appendix B key derivation), using the password you enter. A match shows the password is right and the file is unchanged since it was written.

Reads encrypted parts

Certificates and keys in PKCS#12 encrypted with PBES2 (PBKDF2 + AES-CBC, RFC 8018) are decrypted with the browser’s Web Crypto. Old RC2 and 3DES schemes cannot be read and the tool says so (no home-made cipher is used).

Private keys are never shown

For private keys only the type and size are shown. The key itself appears nowhere — not on screen, in copies, saves or logs — and decrypted bytes are wiped as soon as they are used. The password is not stored or put in the URL.

Use cases

  • Check the expiry of the certificates in a Java keystore or truststore without keytool
  • Check the chain and SANs inside a .p12 / .pfx without exposing the private key
  • Confirm the password is right and the file is not damaged, using the integrity value
  • Note down the CA certificates in a truststore with their SHA-256 fingerprints
  • Pull out just the certificates as PEM to open in another tool

Supported formats

Input

JKS (.jks / .keystore)JCEKS (.jceks)PKCS#12 (.p12 / .pfx)

Output

PEM (per certificate, per alias, or all)

Capability matrix

FeatureSupportNotes
List JKS, JCEKS and PKCS#12 entries (alias, type, creation date, certificates)Supported—
Show subject, issuer, expiry, key type and size, signature algorithm, SHA-256 and SANs; copy or save PEMSupported—
Integrity check (SHA-1 for JKS/JCEKS, MAC for PKCS#12)SupportedOnly when a password is entered. The PKCS#12 MAC supports SHA-1 / 256 / 384 / 512
Read encrypted parts of PKCS#12PartialPBES2 (PBKDF2 + AES-CBC) only. Old schemes such as RC2, 3DES and RC4 cannot be read
Read JCEKSPartialPrivate-key and trusted-certificate entries are read. A secret-key entry (keytool -genseckey) is stored as a serialized Java object and cannot be read past
Show the type and size of a private keyPartialPKCS#12: from the key when it can be decrypted, otherwise inferred from the matching certificate’s public key. JKS: inferred from the certificate
Extract or export private keysNot supportedThis tool never extracts private keys
Create or edit keystores, change passwordsNot supportedRead-only
Verify chain signatures, check trust stores or revocationNot supportedThe Certificate, CSR & PEM Studio checks chains. Neither tool checks revocation
BKS, UBER, public-key-signed PKCS#12, PBMAC1 MACsNot supportedNot supported

Limits & notes

  • Files up to 10 MB and 1,000 entries.
  • PKCS#12 MAC iteration counts up to 1,000,000, and PBKDF2 up to 5,000,000 per part and 20,000,000 per file. Files above that are not read.
  • With an empty password, PKCS#12 is tried with the empty password; if it does not match, the check is treated as not run.
  • JKS and JCEKS creation dates are shown as written in the file. PKCS#12 has no creation date.
  • Days left are computed from your device’s current time; a wrong clock gives wrong results.
  • An integrity match only shows the right password and an unchanged file; it does not mean a certificate is trustworthy.

Privacy & safety

Reading, checking and decrypting the file and password happens entirely in your browser. The file, its name, the password and the results are never sent to or stored on a server, and the password is kept out of the URL and localStorage. Private keys are never shown, copied or saved, and decrypted bytes are wiped after use.

FAQ

Can I see what is inside a JKS file without keytool?
Yes. Choose a .jks / .keystore file and each alias is listed with its type (private key with chain, trusted certificate), creation date, and the certificate’s subject, expiry and SHA-256. Certificates are not encrypted, so the list appears even without the password. Entering the password also checks the trailing SHA-1 digest.
How do I check what is in a .p12 / .pfx file?
Choose the file, enter the password and press “Analyze”. PKCS#12 files written by OpenSSL 3 with its defaults use PBES2 (AES), so certificates and the key’s type and size can be read. Older files encrypted with RC2 or 3DES can have their password checked through the MAC, but their contents are reported as unreadable.
Can I extract the private key?
No. The tool neither shows nor exports private keys; it only reports the type (RSA, EC …) and size. If you need the key, use openssl or keytool in your own environment.
Why does the integrity check say “does not match”?
Either the password is wrong or the file was changed or damaged after it was written. For JKS the SHA-1 digest, and for PKCS#12 the MAC value, differs from the computed one. Check the password’s case and full-width characters.
Is my password sent anywhere?
No. Checking and decrypting happen only in your browser. The password is not stored or put in the URL, and the field is masked (type=password).
Can it check the chain order and signatures?
This tool lists what is inside a keystore. Save the certificates as PEM and paste them into the Certificate, CSR & PEM Studio to check chain order, AKI/SKI matching and signatures.

Certificate, CSR & PEM Studio

Reads PEM, DER (.cer/.crt), CSR and PKCS#7 (.p7b) and lists the subject, expiry (days left), SANs, public key, signature algorithm and SHA-256 fingerprint. It also checks chain order and signatures and converts PEM and DER. Everything runs in your browser and private keys are never read.

No upload

ASN.1 / DER Viewer

Reads PEM, Base64, hex or a DER file and shows the ASN.1 TLV structure (tag, length, value) as a tree. Common OIDs get their names, and wrong lengths or non-DER encodings are flagged. Private-key values are hidden with a warning, and nothing is sent.

No upload

SSH Key Studio

Paste an ssh-ed25519, ssh-rsa or ecdsa-sha2-nistp256 public key, or lines from authorized_keys or known_hosts. The type, bits and fingerprints appear (SHA256 in the same form as ssh-keygen -lf, MD5 colon-separated). Private-key contents are never shown; you are warned to paste public keys only.

No upload

TOTP Studio (2FA Code Checker)

For developers testing two-factor authentication: compute TOTP and HOTP codes from a secret, and build or read otpauth:// URIs and QR codes. Everything runs with Web Crypto in your browser; the secret is never sent or stored.

No upload

Crypto Studio — Hash, HMAC, Encryption & Keys

Type text and see 12 hashes — SHA-256, SHA-3, BLAKE3 and more — at once. Verify webhook HMAC signatures, encrypt text with a password, generate key pairs and create or check bcrypt hashes, all on your own device with nothing uploaded.

No upload

Password Studio — Generator & Strength Checker

A strong 20-character password is ready when the page opens. Fine-tune symbols and excluded characters, switch to a memorable passphrase, or check a password you already use — all without sending anything off your device.

No upload

Last updated: