SSL & Certificates

CSR Decoder

Check a certificate signing request before you send it — the names it asks for, the key behind it, and how it was signed.

PEM signing request
Output

Result appears here after you select

{ } How to use

  1. Paste the signing request, including its BEGIN and END lines.
  2. Select Process to read it.
  3. Check the names and key size match what you intended to order.

{ } How it works

CSR Decoder works on the text you provide. Select Process ▸ and it runs entirely in your browser — nothing is uploaded to a server — then shows the result in the Output panel.

Input

  • PEM signing request — paste or type your input in the left panel (use Sample for an example)

Output

TXT text — copy or download it from the Output panel.

{ } Common uses

  • Make sure a CSR has the right common name before paying for a certificate.
  • Confirm every additional domain made it into the request.
  • Check the key is large enough for the authority you are ordering from.

{ } Limitations

  • A signing request cannot tell you which private key it belongs to; keep them together yourself.
  • The self-signature on a request is not checked here.

{ } FAQ

Is my data uploaded to a server?

No. Everything runs locally in your browser — your files never leave your device.

Can I process more than one file at once?

This tool works on one input at a time.

Is this tool free?

Yes — it’s completely free and needs no sign-up.

Is my private key uploaded anywhere?

No. Every one of these tools runs entirely in your browser — the certificate and key are read, converted and shown without a byte being sent anywhere. That is what makes it safe to paste a private key, which you should never do on a site that converts it on a server.

Does this work with ECDSA certificates?

Yes. RSA, ECDSA and Ed25519 are all read the same way, because the structure is read directly rather than through a library that only understands RSA keys.