Choosing an SSL certificate for the names your website uses

A TLS certificate, often sold as an SSL certificate, helps browsers establish an encrypted connection to a named service. Choose it by the hostnames you need to protect, the validation required and the renewal process you can maintain. The certificate does not prove that every page or business offer is trustworthy.

01 List the required names first

Write down the exact public names, such as example.com, www.example.com and shop.example.com. Include only names you control. Check any existing hosting-provided certificate before buying another product, and confirm whether a CDN terminates the public connection.

  • Single-name or bundled coverage: inspect the product's actual names. Some certificates include an additional www or root name, but this should not be assumed.
  • Wildcard coverage: a name such as *.example.com covers one subdomain level. It does not by itself cover example.com or a.b.example.com.
  • Multiple names: a suitable multi-domain product can include several approved names in its subject alternative name list, subject to its allowance.

02 Understand validation

Domain validation checks control of a name. Organisation and extended validation products involve additional checks defined by the certificate authority. They do not offer a magic stronger encryption mode simply because their validation takes longer, and modern browsers do not generally display the old prominent green company-name bar.

03 Prepare for issue and installation

  1. Confirm the correct product, names and supported server before ordering.
  2. Choose the supported certificate request or managed issuance method. Keep private keys private.
  3. Complete the authority's current validation instructions using the authorised domain or organisation contacts.
  4. Install the issued certificate and required chain at the service presenting HTTPS, then test each covered name.
  5. Set up renewal ownership and expiry monitoring from the first installation.

Common question: is a long subscription one long certificate?

No. The purchased service period can include multiple certificate issuances. Public TLS validity limits are shorter than many billing terms, so check the actual installed certificate's expiry and the product's replacement process.

  • 0 Users Found This Useful
  • security-ssl
Was this answer helpful?

Related Articles

Redirecting HTTP to HTTPS safely with an Apache .htaccess rule

Use an HTTPS redirect after the website has a valid certificate and works correctly over HTTPS....

Understanding a certificate issuance failure caused by CAA

A CAA failure can mean that your DNS policy does not authorise the requested certificate...

Managing separate edge and origin certificates for a CDN

Track edge and origin certificates separately when a CDN or security proxy handles HTTPS. The...

Fixing an incomplete certificate chain

An incomplete certificate chain means a client cannot build the required trust path from the...

Creating a certificate signing request in Plesk

For a certificate ordered outside an automated Plesk workflow, generate a CSR in the domain's...