b2KIT

CSR (Certificate Signing Request) Generator

Generate Certificate Signing Requests with subject fields, key type selection, and SAN (Subject Alternative Names).

Tested tool guide Tested browser tools Checked August 16, 2026

What CSR (Certificate Signing Request) Generator does and how it behaves

A CSR packages a selected public key, subject fields, and requested Subject Alternative Names into a signed certificate request. The generator creates the corresponding key pair in the browser and uses the private key to sign the request, allowing a certificate authority to verify possession of that key. The common mistake is assuming that a Common Name automatically covers the same hostname as a SAN. Enter every identity that the certificate must represent in the SAN list.

How the result is produced

1

Request contents

The subject fields describe the requested certificate holder. SAN entries request additional identities, such as DNS names or IP addresses, through the subjectAltName extension. The CSR also contains the generated public key. These values express what is being requested, but the certificate authority determines which subject information and extensions appear in the issued certificate.

2

Key and signature

Choosing a key type creates a matching public and private key. The public key is embedded in the PKCS #10 request, while the private key signs the request and is not part of the CSR. Generation occurs entirely in the browser, so the key material is not uploaded. The private key must be preserved for use with the resulting certificate.

Good uses

  • Prepare a CSR for a TLS certificate that must cover a primary hostname and several additional DNS names.
  • Generate a new key and request when rekeying or renewing a certificate through a public certificate authority.
  • Create a signed request for an internal PKI enrollment process that accepts PKCS #10 CSRs.

Limits and checks

  • A CSR is only a request. It is not an issued certificate and cannot be installed in place of one.
  • A certificate authority can reject, remove, or alter requested SAN and subject values according to its validation and issuance policy.
  • Verify the SAN list explicitly. Do not assume that entering a Common Name also adds that name as a SAN.

Common questions

Does the CSR contain the private key?

No. A PKCS #10 CSR contains the public key and a signature produced with the corresponding private key, but not the private key itself. Keep the generated private key secure and associated with this request. If it is lost, a certificate issued from the CSR cannot be used with that key pair.

Can I change the subject or SAN entries after generating the CSR?

No, not within the signed request. Changing the encoded subject, SAN list, or public key would make the existing signature invalid. Generate a new CSR with the corrected values instead. A certificate authority may also issue a certificate containing fewer or different values, so inspect the issued certificate separately.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools