UTILS.
100% in-browser
📜

X.509 Certificate Decoder

Decode a PEM or DER X.509 / TLS certificate in your browser: subject, issuer, validity, serial, public key, SANs, key usage, and SHA-1/256 fingerprints.

Paste a certificate above to decode it.

About this tool

The X.509 Certificate Decoder parses a TLS/SSL certificate and shows its contents in plain language. Paste a PEM block (the -----BEGIN CERTIFICATE----- armor) or base64/hex DER, and the tool strips the armor, base64-decodes to raw DER bytes, and walks the ASN.1 structure with a hand-written tag-length-value parser — no external library. It reads the TBSCertificate SEQUENCE to extract the version, serial number, signature algorithm (OID mapped to a name), the issuer and subject distinguished names (CN, O, OU, C, ST, L, emailAddress), and the notBefore / notAfter validity window from their UTCTime or GeneralizedTime fields.

All parsing happens locally in your browser and nothing is uploaded, so you can inspect private or internal certificates safely. From the subjectPublicKeyInfo the decoder reports the key algorithm and size — for RSA it measures the modulus bit length, for EC it names the curve. It decodes the common extensions too: Subject Alternative Name (DNS, IP, email, URI entries), Key Usage bits, and Basic Constraints (the CA flag). It also computes how many days remain until expiry and flags certificates that are expired or expiring within 30 days.

SHA-1 and SHA-256 fingerprints are computed with the browser's WebCrypto API over the exact DER bytes, matching the values openssl x509 -fingerprint prints. This tool decodes certificates specifically; for JSON Web Tokens use the dedicated JWT decoder instead. Copy the full decoded report with one click.

Frequently asked questions

What input formats are accepted?
PEM (the -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- block), raw base64 DER, or hex-encoded DER. The armor is stripped automatically and the base64 or hex is decoded to DER bytes before the ASN.1 parse.
Which fields does it show?
Version, serial number, signature algorithm, issuer and subject DN, validity dates with days-until-expiry, public-key algorithm and size, Subject Alternative Names, Key Usage, the Basic Constraints CA flag, whether it is self-signed, and SHA-1 / SHA-256 fingerprints.
How are the fingerprints calculated?
They are the SHA-1 and SHA-256 digests of the whole DER-encoded certificate, computed in-browser with WebCrypto. These are the same colon-separated hex fingerprints that openssl x509 -fingerprint -sha256 reports for the certificate.
Is the certificate uploaded anywhere?
No. Decoding, ASN.1 parsing, and fingerprinting all run in your browser with plain JavaScript and WebCrypto. The certificate never leaves your device, so internal PKI and client certs stay private.

More tools