Certificate and CSR Decoder
Read PEM X.509 certificates, chains and PKCS#10 signing requests. Free, no login, entirely client-side.
Quick answer
Decode a PEM certificate, certificate chain or signing request in your browser. Inspect names, dates, public keys, extensions and a SHA-256 fingerprint without uploading the content. This free decoder flags selected weak signals and compares adjacent chain names. It does not verify signatures, browser trust, revocation or hostname ownership.
Sources and scope
Format: RFC 5280 sections 4.1 and 4.2, RFC 2986 section 4. TLS identity: RFC 9525 section 4.1.
CA/Browser Forum TLS BR 2.3.1, sections 6.1.5 and 6.3.2, verified November 16, 2026. Lifetime warnings use notBefore as an issuance estimate and apply conditionally to public TLS subscriber certificates. Other extensions and unsupported key types are labeled rather than fully decoded.
Frequently asked questions
Is my certificate or CSR uploaded?
No. Parsing and SHA-256 fingerprinting run locally in your browser. The tool does not save the pasted content or include it in usage analytics. Never paste a private key; private-key PEM blocks are refused and cleared.
What is the difference between a certificate and a CSR?
An X.509 certificate contains an issuer, subject, public key, serial number and validity dates. A PKCS#10 certificate signing request contains a subject, public key and optional requested extensions. A CSR has no certificate issuer, serial number or validity period. Requested extensions are not proof that a CA will issue them.
Does a matching chain prove the certificate is trusted?
No. The decoder compares the encoded issuer name of each certificate with the encoded subject name of the next certificate in the order pasted. This does not verify signatures, trust anchors, path constraints or revocation. Equivalent names with different encodings may show a mismatch. Paste the leaf first, then intermediates and optionally the root.
Which certificate weaknesses are flagged?
The tool flags SHA-1 signatures, RSA keys below 2048 bits, missing subject alternative names and hostnames present only in the common name. It also flags possible excessive public TLS subscriber validity. These are selected signals, not a complete certificate lint or security verdict.
What is the current public TLS certificate validity maximum?
CA/Browser Forum TLS Baseline Requirements 2.3.1 section 6.3.2 sets a 200-day maximum for subscriber certificates issued from March 15, 2026 before March 15, 2027, then 100 days until March 15, 2029 and 47 days thereafter. The prior maximum was 398 days. These limits do not apply to private PKI or CA certificates. The decoder uses notBefore as an issuance estimate because the exact issuance date is not encoded.
What does the SHA-256 fingerprint identify?
It is the SHA-256 digest of the complete DER certificate or CSR, formatted as hexadecimal byte pairs. Compare it with a fingerprint from a separately trusted source. A matching fingerprint identifies the same bytes; it does not establish trust by itself.