SSL Certificate Decoder

Decode an SSL/TLS certificate and see everything in it. Paste PEM text or drop .pem, .crt, .cer, .der or .csr files and get the subject, issuer, validity dates, the domain names it covers, the key type and size, the signature algorithm and the SHA-256 fingerprint — with warnings when it's expired, nearly expired or signed with an outdated algorithm. Whole chains, CSRs and public keys work too. It's free, runs in your browser, and certificates never leave your device.

PEM block types

BEGIN lineContains
CERTIFICATEAn X.509 certificate
CERTIFICATE REQUESTA CSR (PKCS#10)
PUBLIC KEYA public key (SPKI)
PRIVATE KEYA private key (PKCS#8) — keep secret
RSA PRIVATE KEYAn RSA private key (PKCS#1) — keep secret

When to use it

  1. Check when a certificate expires before renewing it.
  2. Confirm a certificate covers every domain it's meant to (SANs).
  3. Inspect a CSR before sending it to a certificate authority.
  4. Match a certificate's fingerprint against one a server presents.

How to Use

  1. Paste PEM text or drop certificate files.
  2. Read the subject, issuer, dates and names.
  3. Check any expiry or algorithm warnings.
  4. Compare the SHA-256 fingerprint if needed.

Features

  1. X.509 certificates, chains, CSRs and public keys
  2. PEM and binary DER
  3. SANs, key usage and basic constraints
  4. SHA-256 fingerprint
  5. Expiry and weak-signature warnings
  6. Private keys: type only
  7. 100% client-side

FAQs

How do I read a .crt or .pem file?

Open it in a text editor and paste it here, or drop the file. Binary .cer and .der files can be dropped too.

What are SANs?

Subject Alternative Names — the domain names and IPs the certificate is valid for. Browsers check these, not the Common Name.

Does the fingerprint match OpenSSL?

Yes. It's the SHA-256 hash of the certificate's DER bytes, the same value openssl x509 -fingerprint -sha256 prints.

Should I paste a private key?

Avoid it. This tool only shows a private key's type and size and never sends it anywhere, but private keys shouldn't be pasted into websites.

Is my certificate uploaded?

No. It's decoded in your browser.

Technical Details

A PEM file is Base64-encoded DER — the binary ASN.1 encoding of an X.509 certificate — between BEGIN and END lines. The decoder reads that structure directly in the browser with a small DER parser: tag, length and value for each element, walking into the to-be-signed certificate to extract the version, serial number, issuer and subject distinguished names, the validity window (both UTCTime and GeneralizedTime), the public key algorithm and size — modulus length for RSA, named curve for EC, or Ed25519 — and the signature algorithm. Extensions are decoded for Subject Alternative Names (DNS names, IP addresses, emails, URIs), Basic Constraints and Extended Key Usage. The SHA-256 fingerprint is computed with the Web Crypto API over the original DER, so it matches what openssl x509 -fingerprint -sha256 reports. Chains with several certificates, CSRs, public keys and binary .cer/.der files are supported. Expired, not-yet-valid and soon-to-expire certificates and SHA-1 or MD5 signatures are flagged. For private keys only the type and size are shown, never the key material.

Developer Tools

Developer Tools

  • HAR File Viewer
  • OpenAPI & Swagger Viewer
  • Log Analyzer
  • .env File Validator
  • HTTP Headers Parser
  • Cookie Parser
  • Dockerfile Generator
  • Nginx Config Generator