How to use
- Open the CSR file (
.csr) you generated before ordering an SSL certificate and copy everything from-----BEGIN CERTIFICATE REQUEST-----to-----END CERTIFICATE REQUEST-----. - Clear the sample and paste yours. Subject, requested SAN domains, key type and size and the signature algorithm appear.
- Check the banner at the top for the self-signature result. It is a good last look at domain spelling, the SAN list and key size before you submit the request to a certificate authority.
What is shown
| Field | Meaning |
|---|---|
| Subject | Request details. CN is the main domain, O the organization, C the country |
| Public key | Key type (RSA or EC) and size. 2048 bits is the usual minimum for RSA |
| Requested SANs | Domains and IPs you asked to be included. A CA may approve only some of them |
| Requested key usage | Extensions carried in the CSR’s extensionRequest attribute. A CA is free to ignore them |
| Signature algorithm | How the CSR itself was signed. SHA-256 or stronger is the norm |
| Self-signature check | Verifies the CSR’s signature with the public key inside it. Only RSA with SHA-1 or SHA-256 is verified; other types are displayed without verification |
What a CSR is
A CSR (Certificate Signing Request, PKCS#10) is the application you send to a certificate authority. It holds your public key and details such as domain and organization, and it is signed with the matching private key, which proves that whoever applied controls that key. The CA checks the details and issues a certificate. The private key is never part of a CSR, so a CSR is safe to send to a CA, while the private key must stay on your server.
Worth checking before you submit
- A typo in a domain is only noticed after issuance. Make sure the SAN list has both the
wwwand the bare name if you need both. - A CSR with no SAN is unlikely to produce a certificate usable in current browsers. Some CAs collect names in their order form instead of reading the CSR, so check how yours works.
- The certificate is issued for the CSR’s public key, so afterwards you can run the certificate and key matcher to confirm the issued certificate pairs with your private key.
- A
challengePasswordtriggers a warning. Some older enrollment flows used it and it sits in the CSR in plain text.
Private key caution
A CSR contains no private key, so pasting one is safe. Do not paste a private key (PRIVATE KEY) into any website. This tool does not read private keys and only warns if one is mixed in. Handling keys with openssl on the server is the safest route. For throwaway keys you can try the RSA key generator, but create production keys on the server. To inspect a certificate you already received, use the SSL certificate viewer.
FAQ
How do I create a CSR?
On the server, for example openssl req -new -newkey rsa:2048 -nodes -keyout server.key -out server.csr. Keep server.key (the private key) on the server and submit only server.csr to the CA.
Can I change the details in a CSR later?
A CSR is signed, so editing it breaks the signature. To change a domain or organization, generate a new CSR with the same private key. You do not need a new key to make a new CSR.
The self-signature check says “not supported”.
Only RSA signatures with SHA-1 or SHA-256 are verified here. For EC keys or SHA-384 and SHA-512 signatures the subject, key and SANs are still read, but no verification result is shown. For a full check use openssl req -in server.csr -verify -noout.
What is the difference between CN and SAN?
The CN is the subject’s main name; the SAN is the list of every name the certificate is valid for. Current browsers check only the SAN, so the main domain must also appear in it.
Can the private key be recovered from a CSR?
No. A CSR contains the public key only.
What you paste is processed only in your browser and never sent to a server.