Certificate Signing Request (CSR) Overview


Before you can generate your SSL Certificate, the certificate requester must create a Certificate Signing Request (CSR) for a domain name or hostname on your web server. The CSR is a standardized way to send the issuing Certificate Authority (CA) your public key, which is paired with a secret private key on the server, and provides relevant information about the requester as indicated below:

  • Common Name (CN):
    This is the Fully Qualified Domain Name (FQDN) of your server (i.e. www.example.net). This must match exactly what you type in your web browser or you may receive a security error.
  • Organization Name (O):
    The legal name of your company/organization. Do not abbreviate your company name and it should include the corporate identifier such as Inc., Corp, or LLC (if applicable). For DV orders, you can use your personal name.
  • Organization Unit (OU):
    The unit or division of the company/organization managing the certificate (i.e. IT Department).
  • Locality (L):
    The city that you are located in (i.e. Tripoli).
  • State or Province Name (ST):
    The state or province in which you are located in (i.e. Tripoli)
  • Country (C):
    The country in which you are located in (i.e. LY)
  • Email Address:
    An email address associated with the company (i.e. [email protected])
  • Root Length:
    The bit-length of the key pair determines the strength of the key and how easily it can be cracked using brute force methods. 2048-bit key size is the new industry standard and is used to ensure security well into the foreseeable future.
  • Signature Algorithm:
    Hashing algorithm are used by issuing Certificate Authorities to actually sign certificates and CRLs (Certificate Revocation List) to generate unique hash values from files. It is highly recommended that your certificate be signed with SHA-2 as this is the strongest signature algorithm adopted by the industry.

As mentioned above, in addition to creating a CSR, the web server will also export another file called a private key.

The private key is a unique cryptographic key related to the corresponding CSR and should never be shared with anyone outside your secured server environment. The private key is mathematically used to decrypt whatever sensitive data that’s transmitted and encrypted with its corresponding public key and vice versa.

If the private key is lost or compromised, malicious users could potentially read your encrypted communications and put your organization’s reputation at risk, which defeats the entire methodology behind the Public Key Infrastructure (PKI). If the private key is lost or compromised, we highly recommend creating a new key pair and replacing or reissuing your SSL Certificate.

Example CSR

Most CSRs are created in the Base-64 encoded PEM format and include the “—–BEGIN CERTIFICATE REQUEST—–“and “—–END CERTIFICATE REQUEST—–“ lines as the header and footer tags of the CSR. A standard PEM format CSR will look like the following example:


When making your CSR and private key, please reference our easy-to-read CSR Generation Instructions:

If you are unsure what server you’re using or need assistance during any step within the process, please Submit a ticket or visit our support center.

Share this:
FacebookTwitterWhatsAppViberCopy LinkTelegramLinkedIn
Updated on January 25, 2022
Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for?
Contact Support