Adding SANs to Wildcard SSL Certificates
Wildcard certificates help server administrators save hundreds or even thousands of dollars on SSL Certificates by installing the same certificate to multiple websites or servers at no additional cost.
However, by using our wildcard certificates in conjunction with Subject Alternate Names (SANs), you can save even more money and expand certificate functionality.
In our wildcard certificates we automatically include your domain name without any subdomain as a SAN (for example, domain.com). We also allow you to define your own SANs at no extra cost, as long as the SAN is a subdomain of your existing domain.
How Does This Help Me?
In general, wildcard certificates can only be used to secure first-level sub-domains of the domain that they are issued to. For example, a standard wildcard certificate is issued to *.domain.com. Once that certificate is installed on the server/servers, users can connect securely to www.domain.com, mail.domain.com, autodiscover.domain.com, etc.
However, because the name on your certificate must exactly match the name that a user is connecting to, a standard wildcard will not allow your users to connect to your domain with no subdomain (domain.com), or with multiple levels of subdomains, (multiple.sublevels.domain.com).
Additionally, this allows some devices that are not normally compatible with wildcard certificates (see the list here) to work.
How Do I Use SANs with My Wildcard Certificate?
In our wildcard certificates we automatically include your domain name without any subdomain as a SAN (for example, domain.com). You can add additional subdomains during the order process (example.domain.com, sub1.example.domain.com, etc).
Free duplicate certificates can also be generated for your wildcard SSL Certificates, as shown in the image below. Simply enter the subdomains that you want to secure into the form. You can do this at any time while your certificate is valid at no extra cost.