X.509 CSR Decoder
Paste a PEM certificate signing request and read its subject, public key type and size, signature algorithm, requested SANs and key usage, plus its SHA-256 fingerprint.
Use the tool
Why this tool exists
Before you send a CSR to a certificate authority, it pays to check what it actually asks for. A missing subject alternative name, a 1024-bit key or the wrong common name wastes a day when the certificate comes back unusable.
This decoder reads the PKCS#10 structure with a small built-in DER parser and lists the subject fields, the RSA bit length or EC curve, the signature algorithm and the requested extensions. It also computes a SHA-256 fingerprint of the request. The signature itself is not verified. The CSR contains only a public key and identity details, never the private key, but treat requests from unknown sources with care.
How to use it
- Paste the PEM text, from BEGIN CERTIFICATE REQUEST to END CERTIFICATE REQUEST.
- Read the subject, key, signature algorithm and extensions in the output.
- Fix the request in your tooling if anything is wrong, then submit it to the CA.
Frequently asked questions
Does the CSR contain my private key?
No. A CSR holds the public key, the requested names and a signature made with the private key. The private key stays where you generated it and must not be pasted anywhere.
Does it verify the signature?
No. The output says so at the end. It decodes the structure only, so a damaged or forged signature would not be detected.
Which key types can it describe?
RSA, with a bit length, and elliptic curve keys with the curve name when it is one of P-256, P-384 or P-521. Other algorithms are shown by their object identifier.
Where do I see the subject alternative names?
In a line labelled Subject Alt Names, if the CSR carries the extension. Names appear as DNS, email, URI or IP entries.