Back to Articles
Explainer2026-05-20•6 min read•CSR.plus Team

CSR vs Private Key: What Each One Is and Who May See It

CSR vs Private Key: What Each One Is and Who May See It

Two files, opposite risk profiles

Both are produced in the same second on the same machine, which is why they get confused. But they are not two halves of one secret — one is public by design, the other is the secret itself.

Certificate Signing Request (CSR)Private key
ContainsPublic key, requested names, signatureThe secret exponent / scalar
Signed byYour private keyNothing — it is the signer
Safe to shareYesNever
Who needs itThe CA or the issuing panelOnly your server
If lostRegenerate in secondsCertificate becomes unusable
If leakedNo impactAnyone can impersonate you until revocation

What a CSR actually proves

A CSR is a self-signed statement: "this public key belongs to this subject, and I hold the matching private key."

The CA verifies two separate things before issuing:

  1. Control of the names — through HTTP-01, DNS-01 or a manual review, depending on the CA and validation level.
  2. Possession of the key — implicitly, by checking the signature on the CSR against the public key inside it.

That second check is why you can submit a CSR generated on a machine that never touches the internet, as long as the private key never leaves it.

What the private key is for

Once the certificate is issued, the private key does all the work at runtime: it decrypts the TLS handshake (for RSA key exchange, now rare) and, more importantly, signs the handshake transcript so the client knows the server controls the key in the certificate.

Practical consequences:

  • File permissions matter. chmod 600, owned by root, no group read.
  • Backups matter. A lost key means a new certificate and a new deployment, usually during an outage.
  • Rotation matters. A certificate expires; a leaked key does not. Revocation only helps if clients actually check OCSP or CRLs, which many do not.

The mistake people actually make

Not misunderstanding the concepts — but attaching both files to the same email or ticket.

A CSR is fine to email. A private key is not. Since both are text files that start with -----BEGIN, they look similar in an attachment list, and panels often ask for "the CSR and key" in one form. Check what you are uploading:

  • -----BEGIN CERTIFICATE REQUEST----- → CSR, safe
  • -----BEGIN PRIVATE KEY----- → private key, never upload
  • -----BEGIN CERTIFICATE----- → the issued certificate, public

The PEM viewer identifies which one you have before you paste it anywhere.

Reuse, renewal and revocation

Renewal does not require a new key. You can regenerate a CSR from the existing key and get a fresh certificate, which is useful when:

  • the key is pinned in configuration management or a hardware module;
  • you rotate keys on a slower schedule than certificates;
  • the certificate was misissued and you need a replacement for the same key.

The safer default for most teams is a new key per renewal, with the old certificate kept until it expires. If you do reuse a key, at least verify the pair before deploying — a mismatched pair is the most common cause of a broken TLS rollout.

What to check when something breaks

  • Certificate installed but browsers complain → check the chain, then check that the certificate's public key matches the server key using key match.
  • Key works on one server but not another → the second server has a different key file than you think.
  • CSR rejected by the CA → the CSR is fine; the names or validation level are the problem.

Knowing which file you are looking at is most of the debugging.

FAQ

Is it safe to send a CSR by email?

Yes. A CSR contains only public material plus the signature. The risk is accidentally attaching privkey.pem with it — always check the attachment name before sending.

Can someone derive my private key from a CSR?

No. The CSR contains the public key and a signature made with the private key. Recovering the private key from either is equivalent to breaking RSA or ECDSA.

Does the CA keep my private key?

No. The CA signs your CSR with its own key and returns a certificate. If any service asks for your private key to "install" a certificate, that is a red flag.

Can I reuse my private key for a new certificate?

Yes. A CSR can be regenerated from the same key at any time. Many teams reuse keys when the key is pinned in config management, but rotating the key on renewal is safer.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles