Last modified: October 13, 2020
SSL/TLS (Secure Sockets Layer/Transport Layer Security) encrypts information between a visitor’s browser and a server. These protocols protect against electronic eavesdroppers. This also protects sensitive communications (for example, credit card numbers and login information).
Both of these protocols initiate a handshake, during which your server and the user’s computer agree on specific conditions. These conditions include a set of public and private keys. Both computers use these keys to encrypt and decrypt messages transmitted during communication.
cPanel & WHM supports Transport Layer Security (TLS) protocol version 1.2 and Transport Layer Security (TLS) protocol version 1.3:
- cPanel & WHM only supports TLSv1.2 or newer. The system enables TLSv1.2 by default.
- Not all internet browsers or clients will support TLSv1.3, which requires OpenSSL 1.1.1 or higher.
You can set up SSL/TLS for your server and configure how SSL/TLS certificates run in cPanel’s SSL/TLS interface (cPanel >> Home >> Security >> SSL/TLS).
cPanel, L.L.C. does not offer free signed or self-signed hostname certificates for cPanel DNSOnly® servers.
An SSL certificate is an electronic document that digitally binds a public key to an identity. This helps secure the connection between a web browser and a website. An SSL certificate serves the following functions:
Encryption — Encodes data. This helps to ensure that if someone intercepts the transmission, they cannot understand it.
Identification verification — This ensures that you connect to the correct server.
- SSL certificates review domain names literally. For example, SSL interprets
example.comas two different domains.
- The Common Name (CN) entry of an SSL certificate is cosmetic and does not affect the security of a certificate.
- An SSL certificate’s CN does not need to be the main domain. The certificate covers all domains listed in the certificate’s Subject Alternative Name (SAN) field.
SSL key security
When you generate an SSL certificate, you can select the type of key that your SSL certificate uses. You can also select the type of key the system uses by default when generating SSL certificates:
- In WHM, use either WHM’s SSL/TLS Configuration interface (WHM >> Home >> SSL/TLS >> SSL/TLS Configuration) or the Default SSL/TLS Key Type setting in WHM’s Tweak Settings interface (WHM >> Home >> Server Configuration >> Tweak Settings).
This setting only applies to cPanel users who do not set a default key type.
- In cPanel, use the SSL/TLS interface (cPanel >> Home >> Security >> SSL/TLS).
When selecting a new default key type, the system performs an AutoSSL run. This updates all installed AutoSSL-issued certificates to use the new key type.
When you work with SSL, you may encounter the following types of SSL certificates:
Single-domain — This certificate type secures a single domain or subdomain.
Multi-domain — This certificate type secures many domains with one certificate. It is also called a Unified Communications/Subject Alternate Name (UC/SAN) certificate.Note:
You must reissue a multi-domain certificates each time you add a new hostname.
Self-signed — This certificate type does not verify the identity of the server and does not require a CA. These certificates are not secure. Visitors’ browsers will display a warning when they access the site. You can create a self-signed SSL certificate in WHM’s Generate an SSL Certificate and Signing Request interface (WHM >> Home >> SSL/TLS >> Generate an SSL Certificate and Signing Request).Important:
We strongly recommend using a valid signed certificate if your website handles sensitive data.
Shared SSL — This certificate type allows you to secure multiple domains with the same SSL certificate.Note:
As of cPanel & WHM version 76, we do not support this type of certificate.
Wildcard — Any type of certificate that contains a wildcard (
*) domain. You can secure a domain’s subdomains with a single certificate if they share an IP address. For example, you can use a wildcard for the
*.example.comdomain to also secure the
www.example.comsubdomains. However, this will not secure the to
You can apply a wildcard certificate to services in WHM’s Manage Service SSL Certificates interface (WHM >> Home >> Service Configuration >> Manage Service SSL Certificates).
rootuser may install a wildcard certificate on a collection of subdomains for a single
rootdomain on multiple IP addresses. If this configuration uses multiple IP addresses, a user on the server cannot own the
Server Name Indication (SNI) support allows you to host multiple SSL certificates for different domains on the same IP address. At the beginning of the handshake process, SNI indicates the hostname to which the client connects. Users on shared servers that support SNI can install their own certificates without a dedicated IP address.
cPanel & WHM servers do not support SNI for the FTP service.
Your Certificate Authority (CA) is the trusted third-party entity that issues your SSL certificates.
CA bundle files
Generally, when you purchase an SSL certificate, the CA will provide you a CA bundle file. Some providers will send you the bundle file as a
.zip file, others provide the files individually, and some will provide you a URL to download the bundle file.
A bundle file will contain the following details about the SSL certificate:
The CA that issued the certificate.
Any of the CA’s certificates, root or intermediate.
The chain of trust for the issuer.Note:
A CA can vouch for other CAs, which results in a chain of trust. For a CA to sell certificates, another CA must vouch for them.
Certificate Revocation Lists (CRLs).
The order of files in a bundle is important. If the CA sends individual files, we recommend that you ask them to pack them into a bundle file for you.
Bundle files for EV (Extended Validated) certificates may contain more files than certificates than OV (Organization Validated) and DV (Domain Validated) certificates.
Browsers include a list of trusted CAs, and they use the list to determine whether to trust a specific CA.
You can locate a domain’s CA bundle with either of the following UAPI functions:
You can install a CA bundle in either of the following interfaces:
cPanel’s Manage SSL Sites interface (cPanel >> Home >> Security >> SSL/TLS >> Manage SSL Sites).
WHM’s Install an SSL Certificate on a Domain interface (WHM >> Home >> SSL/TLS >> Install an SSL Certificate on a Domain).
You can also use the UAPI
SSL::install_ssl function to install a CA bundle.
A Certification Authority Authorization (CAA) record specifies which CAs may issue certificates for a domain. If no CAA records exist for a domain, all CAs can issue certificates for that domain. You can manage CAA records through WHM’s DNS Zone Manager interface (WHM >> Home >> DNS Functions >> DNS Zone Manager) or through cPanel’s Zone Editor interface (cPanel >> Home >> Domains >> Zone Editor).
If conflicting CAA records already exist, you must either remove the current CAA records or add one for the desired CAA. For example, a CAA record for Sectigo would resemble the following example, where
example.com represents the domain name:
example.com. 86400 IN CAA 0 issue "sectigo.com"
Similarly, a CAA record for Let’s Encrypt would resemble the following example, where
example.com represents the domain name:
example.com. 86400 IN CAA 0 issue "letsencrypt.com"
AutoSSL secures multiple domains with the assumption that all of the domains resolve to the same virtual host. A cPanel-issued AutoSSL certificate expires after 90 days. However, AutoSSL attempts to automatically replace that certificate before it expires.
You can use the cPanel (powered by Sectigo) provider to secure up to 1,000 domains per certificate.
AutoSSL does not issue certificates for websites on suspended accounts. You must first activate the account in order for AutoSSL to issue a certificate.
In cPanel & WHM version 64 and later, AutoSSL adds service subdomains to the SSL certificate using a sort algorithm. For more information about service subdomains, read our Service and Proxy Subdomains documentation.
AutoSSL uses a sort algorithm to establish which domains to add to the certificate first. This sort order ensures that the system adds the domains that customers will most likely visit to the certificate first. For example, customers most likely intend to navigate to
The default sort algorithm prioritizes domains in the following order:
Any fully-qualified domain names (FQDNs) that the virtual host’s current SSL certificate secures.
The primary domain on the cPanel account and its
Each addon domain and its
mail.subdomains. For example, the
examplecPanel user (whose primary domain is
example.com), creates the
foo.comaddon domain. This addon domain, like all cPanel addon domains, exists on a separate virtual host with a subdomain. In this case, the system prioritizes
Domains with fewer dots. For example, AutoSSL would prioritize
AutoSSL only adds the
whmservice subdomain to the SSL certificate for reseller accounts.
The cPanel (powered by Sectigo) provider
By default, cPanel & WHM uses the cPanel (powered by Sectigo) provider. It is free and comes with your cPanel & WHM license.
The Let’s Encrypt plugin
The Let’s Encrypt provider has the following limitations:
A rate limit of 300 certificate orders every three hours.
A weekly limit of 50 registered domains.
A maximum of 100 subdomains per certificate.
Limits the certificates it issues to a specific set of domains to five certificates per week. After this, Let’s Encrypt blocks any further certificates for that set of domains.Note:
To work around this rate limit, create an alias to a domain in the virtual host list (website). Let’s Encrypt will interpret the virtual host as a new set of domains.
For more information about Let’s Encrypt’s rate limits, read their rate limit documentation.
Domain and rate limits
The AutoSSL feature includes the following limitations and conditions:
A domain’s DNS zone contains CAA records. These CAA records restrict which CAs may issue certificates for that domain. If a CAA record for another provider already exists, you can remove that CAA record or add one for the desired CA. If no CAA records exist for a domain, all CAs can issue certificates for that domain.
- Your server’s DNS zone can have more than one CAA record to receive certificates from more than one CA.
Each AutoSSL provider may use a specific domain rate limit:
- Certificates that cPanel, L.L.C. provides through AutoSSL can secure a maximum of 1,000 domains per certificate (Apache virtual host). The following table demonstrates these limitations for the cPanel AutoSSL provider:
Virtual Host 1 Virtual Host 2 Result 1,000 domains AutoSSL generates one certificate for the account, which secures all 1,000 domains. 1,002 domains AutoSSL generates one certificate for the account, which secures the 1,000 first domains from the sort algorithm. 500 domains 500 domains AutoSSL generates a certificate for each virtual host that secures all of the domains on that virtual host. 500 domains 502 domains AutoSSL generates two certificates:
- Virtual Host 1 — Secures all of the virtual host’s domains.
- Virtual Host 2 — Secures the 1000 first domains from the sort algorithm.
Certificates that Let’s Encrypt provides can secure a maximum of 100 domains every three hours.
Aliases count three times towards each certificate’s domains limit. When you create an alias domain, the system adds the following aliases to the original virtual host (where
aliasdomain.comrepresents the alias domain):
AutoSSL only includes domains and subdomains that pass a domain control validation (DCV) test. This DCV proves ownership of the domain.
AutoSSL includes corresponding
www.domains for each domain and subdomain in the certificate, and those
www.domains count towards any domain or rate limits. For example, for the
example.comdomain, AutoSSL automatically includes
www.example.comin the certificate. If the corresponding
www.domain does not pass a DCV test, AutoSSL will not attempt to secure that
- This method affects Let’s Encrypt’s limit of 50 certificates per week that may contain a domain or its subdomains.
The default cPanel AutoSSL provider does not secure wildcard domains. However, the Let’s Encrypt provider will secure wildcard domains.
Each AutoSSL provider may wait for a specific amount of time to replace an AutoSSL-provided certificate before it expires. For example:
AutoSSL attempts to renew certificates that cPanel, L.L.C. provides when they expire within 15 days.
AutoSSL attempts to renew certificates that Let’s Encrypt provides when they expire within 29 days.
Due to rate limits, AutoSSL prioritizes new certificates over the renewal of existing certificates.
AutoSSL will not attempt to replace certificates that it did not issue. You can override this behavior if you enable the Allow AutoSSL to replace invalid or expiring non-AutoSSL certificates setting in WHM’s Manage AutoSSL interface (WHM >> Home >> SSL/TLS >> Manage AutoSSL).
AutoSSL replaces certificates with overly-weak security settings. For example, an RSA modulus of 2048-bit or less.
A virtual host may contain more than the provider’s limit of domain names per certificate. AutoSSL uses a sort algorithm to determine the priority of domains to secure. For more information, read the AutoSSL sorting section above.