What is a CSR?

A certificate signing request (CSR) is the file you send to a certificate authority to get an SSL/TLS certificate for your website or server. It holds your domain names, optional details about your organization and the public half of a new key pair, signed with the private half to prove you own it. The certificate authority checks it and sends back a certificate for that key.

The private key never goes into the request. You keep it on your server, where it works together with the certificate.

How to generate a CSR

  1. Enter the domain name the certificate is for, such as shop.example.com, or a wildcard like *.example.com.
  2. Add any other names the certificate should cover under More domain names, one per line, such as www.shop.example.com. IP addresses work too.
  3. Fill in your organization, city, state and country if your certificate authority asks for them. Domain-validated certificates usually ignore these fields.
  4. Pick a key type and click Generate CSR.
  5. Download or copy the CSR and send it to your certificate authority. Save the private key right away: it can't be made again, and the certificate is useless without it.

Which key type should I pick?

  • RSA 2048 works with every certificate authority, server and client, and is what most people use.
  • RSA 3072 and RSA 4096 are bigger RSA keys. They're slower to use and rarely needed.
  • ECDSA P-256 gives smaller keys and faster connections with security comparable to RSA 3072. All current browsers and servers support it.
  • ECDSA P-384 is a larger elliptic curve key for policies that ask for one.

What goes into the request

  • The domain name becomes the common name (CN) and is always repeated as a subject alternative name (SAN), since browsers only read the SANs.
  • Domain names are written in lower case. International names like bücher.example are converted to their xn-- form.
  • Organization, city, state or province and country are added only when you fill them in. Public certificate authorities no longer put organizational units or email addresses in TLS certificates, so the tool leaves those fields out.
  • RSA requests are signed with SHA-256, ECDSA P-256 requests with SHA-256 and P-384 requests with SHA-384.

The private key is saved in the standard PKCS#8 format (-----BEGIN PRIVATE KEY-----), which web servers like nginx, Apache and Caddy read directly.

How it works

The key pair is generated by your browser's built-in Web Crypto API, and the request is built and signed with the PKI.js library. Everything happens on your device: neither the key nor the request is uploaded anywhere.

Features

  • RSA 2048, 3072 and 4096 and ECDSA P-256 and P-384 keys
  • Several domain names, wildcards and IP addresses in one request
  • International domain names converted for you
  • Optional organization, city, state and country
  • Download the CSR and the private key as files
  • Runs in your browser