Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
An SSL certificate CSR is a certificate signing request. It contains a public key and requested information; it is not the private key or the issued certificate. For freelance server work, keeping these artifacts distinct prevents insecure handovers and helps explain why a returned certificate must match the key used for the request.
Generate the request in the right environment
Use the hosting platform or supported tooling under the client’s approved process. Confirm required names and issuer fields before generation. The private key should be created and protected according to the deployment’s security policy. Do not send it with a CSR merely because both files appeared during setup or a provider asks for request material.
Review names and key handling separately
Inspect the CSR’s public information and ensure the intended names are represented under the platform’s supported workflow. A CSR is a request; the issuer validates and decides what it will issue. Keep private-key permissions and storage limited. Public request fields do not need the same secrecy as a private key, but may still contain organizational details worth handling thoughtfully.
Match the issued certificate and deployment
Install the returned certificate using the matching private key and the platform’s documented chain requirements. If the key was lost, do not assume renaming another key file will work. Follow the issuer’s reissue or replacement process. Document ownership and storage locations without copying private material into tickets, article examples or ordinary chat.
A practical checklist
- Confirm names and the issuer’s current request requirements.
- Generate the key and request through approved tooling.
- Keep the private key out of the CSR submission.
- Verify the issued certificate matches the intended deployment.
- Record ownership without exposing key contents.
Worked example
Illustrative example: a freelancer uses a managed server panel to generate a CSR. They send only the request through the issuer’s approved channel while the key stays protected on the platform. The returned certificate is installed through the matching pending request. A handover describes the process and responsible account, not the private key text.
Common questions
Is a CSR the certificate? No. Does the CSR contain the private key? It should contain the public key, not the private key. Can an unrelated private key be substituted? No; the certificate’s public key must correspond to the deployment’s private key.
What to do next
Treat request, key and issued certificate as separate artifacts with different handling needs. If any private material has been exposed, follow the client’s incident and replacement process.