Skip to content
AdminKit

CSR (Certificate Signing Request)

What is CSR (Certificate Signing Request)?

A CSR (Certificate Signing Request) is the file a server operator sends a certificate authority to request a TLS certificate, structured under RFC 2986's PKCS #10 format and signed with the matching private key. AdminKit's SSL check tool shows the certificate a CSR eventually becomes, as a live server presents it.

By AdminKit team, Netbase JSC · Updated

A CSR (Certificate Signing Request) is the file a server operator generates and sends to a certificate authority to request a TLS certificate, structured according to RFC 2986’s PKCS #10 format, whose document record is tracked at the IETF Datatracker. It bundles the public key the certificate will cover, the requested subject details (commonly the domain name), and a signature made with the matching private key, which proves the requester actually holds that private key without ever sending it anywhere. The CA uses the CSR’s public key and subject information to build the issued certificate, then separately verifies the requester actually controls the domain — often automatically, via the ACME protocol, under rules the CA/Browser Forum Baseline Requirements set for every publicly trusted CA — before issuing it; the CSR itself only proves key possession, not domain ownership. Generating a new CSR also generates a new key pair, which is why rotating a certificate’s private key means creating and submitting a fresh CSR rather than reusing an old one. The openssl req command is a common way to do this; OpenSSL documents it as primarily creating and processing certificate requests (CSRs) in PKCS#10 format. A CSR is typically generated and submitted in PEM format, the same base64 text container the issued certificate itself is usually distributed in.

What a CSR does and doesn’t prove:

  • Proves the requester holds the private key matching the public key in the request.
  • Does not prove domain ownership — the CA verifies that separately, often via ACME.
  • A fresh CSR means a fresh key pair, which is why key rotation always starts with a new CSR.

AdminKit groups cSR (Certificate Signing Request) under its machine protocols cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does a CSR's signature actually prove?

That the requester holds the private key matching the public key in the request -- it does not prove the requester owns the domain being requested.

How does a CA verify domain ownership if the CSR doesn't prove it?

Separately, often automatically via the ACME protocol, under rules the CA/Browser Forum Baseline Requirements set for every publicly trusted CA.

Why does rotating a certificate's private key always start with a new CSR?

Because generating a new CSR also generates a new key pair, so reusing an old CSR would mean reusing the old, rotated-away key.

What format is a CSR structured under?

RFC 2986's PKCS #10 format, typically generated and submitted in PEM, the same base64 text container the issued certificate is usually distributed in.