ToolConvoyToolConvoyv2.6
DEV

SSL Certificate Decoder — Decode PEM SSL Certificates in Your Browser

Decode PEM-encoded SSL/TLS certificates. View issuer, subject, validity period, SANs, public key details, and fingerprints — no upload, no server.

● LOCAL · GENERATED IN YOUR TAB0 network requests from tools since page load

SSL Certificate Decoder

Decode PEM SSL certificates — view issuer, subject, validity. No uploads — your certificates never leave your device. Works entirely in your browser.

X.509 certificates are the identity layer of the internet. Every HTTPS connection begins with a TLS handshake in which the server presents a certificate that proves its identity, and every browser, every API client, and every mobile app verifies that certificate against a trusted root store before sending a single byte of application data. The certificate itself is a binary ASN.1 structure, but the format that developers encounter is PEM — a Base64-encoded block delimited by header and footer lines — because PEM is the format that web servers, load balancers, and certificate authorities exchange. Decoding the PEM back to its structured fields is the first step in debugging any TLS issue: an expired certificate, a mismatched hostname, a missing intermediate in the chain, or a public key that is too short for current security requirements.

The SSL Certificate Decoder parses the PEM, unwraps the DER-encoded ASN.1 structure, and extracts every field that the X.509 standard defines: subject and issuer distinguished names, validity period with human-readable dates, the serial number, the public key algorithm and bit length, the signature algorithm, and the Subject Alternative Names that browsers check against the URL’s hostname. The fingerprints are computed locally from the raw DER bytes and match the values that browsers display in their certificate viewers. An expired certificate is highlighted red in the validity section, so the most common debugging question — “why is this site showing a certificate error?” — is answered immediately.

The decoder does not verify the issuer’s signature and does not check revocation status — those operations require network access to the issuing CA and the OCSP responder, which a client-side tool cannot do without leaking the certificate. For full verification, the companion openssl verify command is documented in the platform notes. For inspecting a certificate you already have — from an email, from a configuration file, from a clipboard paste — the decoder gives you the structured view without opening a terminal.

Advertisement

How to use

  1. Paste the PEM certificate

    Paste the Base64 block between `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`. The decoder parses ASN.1 DER structure and extracts every standard X.509 field.

  2. Review the certificate details

    The decoded view shows the Subject, Issuer, validity dates (Not Before / Not After), serial number, public key algorithm and size, signature algorithm, and every Subject Alternative Name (SAN) in a flat list.

  3. Check fingerprints

    SHA-256 and SHA-1 fingerprints are computed locally from the DER bytes. The SHA-256 fingerprint is the value browsers display in the certificate viewer — paste it to verify a certificate you received matches what the issuer published.

Frequently asked

Does this tool verify the certificate chain?

No. Decoding reads the certificate's contents but does not validate the signature or check the issuer chain. Verification requires the issuer's public key and root CA trust store, which are not available in a client-side tool. Use `openssl verify` for chain validation.

What information can I see about the public key?

The algorithm (RSA, EC, Ed25519), the key size in bits (2048, 4096 for RSA; 256, 384 for EC), the curve name for EC keys (P-256, P-384), and the raw public key bytes in hex. Private key material is never present in a certificate.

Can it decode the full certificate chain from a PEM bundle?

Yes — paste a PEM file with multiple `-----BEGIN CERTIFICATE-----` blocks, and each certificate is decoded separately. The bundle view shows the chain order and highlights which certificate is the end-entity (leaf) vs intermediate.

Does it support DER-encoded certificates?

The tool accepts PEM only. To decode a DER certificate, convert it to PEM first with `openssl x509 -inform der -in cert.der -out cert.pem`, or use the companion Base64-encode tool to wrap the DER bytes in PEM headers.

Limitations

  • No signature verificationDecoding reads the certificate fields but does not cryptographically verify the issuer's signature. For verification, use `openssl verify -CAfile ca.pem cert.pem` on the command line.
  • No revocation checkingCRL and OCSP status are not checked. A decoded certificate that appears valid may have been revoked. Check revocation status with `openssl ocsp` or your browser's certificate viewer.
  • Extension parsing is limitedStandard X.509v3 extensions (SAN, Basic Constraints, Key Usage, Extended Key Usage) are fully decoded. Custom or obscure extensions are shown as hex dumps with the OID label.

Platform notes

macOS
The macOS Keychain Access app shows certificate details in a GUI. Use this tool when you need the raw ASN.1 field values for scripting, or when you only have the PEM text without importing it into the keychain.
Linux
The equivalent CLI command is `openssl x509 -in cert.pem -text -noout`. The browser tool is the right pick when you are on a machine without OpenSSL installed, or when you want a formatted view without scrolling through terminal output.
Web
Runs entirely client-side using ASN.1 parsing in JavaScript. Certificates never leave your browser — useful for inspecting sensitive internal certificates.
Advertisement
Advertisement