Security Tools

X.509 Certificate & CSR Decoder

Paste or upload a certificate, a full chain, a PKCS#7 bundle or a certificate signing request to see every field: subject and issuer, SANs, validity, key, fingerprints and all extensions, with chain-order and signature checks. To test a live server's certificate use the SSL Certificate Checker.

Private by design: anything you enter is processed in your browser only. It is never uploaded to or logged on our servers. Certificates, chains and CSRs are decoded locally with your browser's Web Crypto API. Private keys are not accepted: if you paste one by mistake it is removed before anything is decoded.

.pem .crt .cer .der .csr .p7b – up to 2 MB

Paste a certificate above, upload a file, or load the example chain (created in your browser) to see how the decoder works.

About X.509 certificates and CSRs

An X.509 certificate binds a public key to a name. The subject says who the key belongs to, the issuer names the certificate authority (CA) that signed it, and the validity period limits when it may be used. For TLS, browsers ignore the common name and only match host names against the Subject Alternative Name (SAN) extension, so every name the server answers to must be listed there.

Servers send a chain: their own (leaf) certificate first, then each intermediate CA certificate in turn. Each certificate must be followed by the one that issued it: its issuer name equals the next subject, its authority key identifier (AKI) equals the next subject key identifier (SKI), and its signature verifies with the next public key. This decoder checks all three for every link, verifies self-signed roots, and suggests the correct order when a bundle is shuffled. Root certificates come from the client's trust store, so sending them is optional.

A certificate signing request (CSR, PKCS#10) carries the subject, the public key and the extensions you ask the CA to include, signed with your private key. The decoder verifies that self-signature, lists the requested SANs and key usages, and reports whether a challenge password is present without showing it.

Files can be PEM text (the -----BEGIN CERTIFICATE----- format, often named .pem, .crt or .cer), binary DER (.der, .cer) or PKCS#7 bundles (.p7b) as exported by Windows and Java tools. Fingerprints are calculated over the DER bytes with your browser's Web Crypto API, so they match openssl x509 -fingerprint -sha256. Related tools: SSL Certificate Checker for a live server, JWT Encoder & Signer, which can verify tokens with a certificate's public key, SSH Key Generator and SAML Response Analyzer.

Frequently Asked Questions

No. Certificates, chains and CSRs are parsed in your browser with JavaScript and the Web Crypto API, and nothing is sent to our servers. The page also works offline once it has been loaded.

PEM blocks (BEGIN CERTIFICATE, CERTIFICATE REQUEST, NEW CERTIFICATE REQUEST, PKCS7), several blocks at once such as fullchain.pem or a CA bundle, base64 or hex DER without headers, and .pem, .crt, .cer, .der, .csr and .p7b files in PEM or binary DER form.

Private key blocks (PRIVATE KEY, RSA/EC PRIVATE KEY, ENCRYPTED PRIVATE KEY, OpenSSH and PuTTY keys) are removed from the input before anything is decoded, and a warning is shown. The key is never read. If it was a production key, treat it as exposed and replace it.

For every certificate followed by another, the decoder compares the issuer name with the next subject, the authority key identifier with the next subject key identifier, and verifies the signature with the next certificate's public key. Out-of-order chains get a suggested order. It does not check revocation or whether the root is in a browser trust store; use the SSL Certificate Checker for a live server.

Errors are things clients reject: an expired or not yet valid certificate, an RSA key under 2048 bits, a SHA-1 or MD5 signature on a non-root certificate, or a signature that does not verify. Warnings point at likely mistakes, such as a server certificate without Subject Alternative Names, an end-entity certificate with CA:TRUE, or a lifetime over 398 days.

The challengePassword attribute is stored unencrypted inside the CSR, so the decoder only reports that it is present. Most public CAs ignore it; leave it empty when generating a CSR unless your CA asks for it.