Support Start > Web Hosting Technical Information > SSL Pages > SSL "Common Name" mismatch

This page is showing a generic answer.
To see a more detailed answer customized for you, type your domain name here:

Technically advanced users who view the details of their Let’s Encrypt SSL certificate sometimes ask why the “common name” of the certificate doesn’t match the domain name of their website.

For example, if your domain name is example.com, you might be surprised to examine the certificate in the Chrome browser and see that the “common name” of the certificate is “customers.tigertech.net” or another domain name, like this:

This is normal with modern certificates that are valid for multiple domain names. The “common name” is meaningless with modern SSL certificates, and it is simply the first of many domain names that a certificate is valid for; you should instead scroll down and look at the “Subject Alternative Names” of the certificate, which will include example.com (probably among others):

This difference is purely cosmetic with modern browsers — it does not affect how they work, and doesn’t indicate a problem. Many browsers are removing the display of the “common name” completely.

If the cosmetic difference bothers you, you can get a non-shared SSL certificate (where the common name always matches your domain name and the certificate does not include any other domain names) by ordering a dedicated IP address for your site.