We recently received a query from an SSL.com customer with an existing wildcard certificate:
*.mydomain.com. I need to use https://www.subdomain.mydomain.com or *.*.mydomain.com. Is there a way to do this? Do I have to purchase another wildcard?”A wildcard IS required, but we can extend this customer’s functionality as required (and save them money at the same time).
This customer actually asked two questions – can www.subdomain.mydomain.com be protected (yes) and could a wildcard be issued for *.*.mydomain.com (no).
There are no multi-level wildcard certificates, with two wildcard levels (like *.*.mydomain.com) since no browsers recognize this configuration. For that matter, a pattern like www.*.mydomain.com can’t be used for a wildcard certificate either, because the wildcard must be the leftmost element.
However, this customer can certainly cover www.subdomain.mydomain.com (and all other subdomains built over subdomain.mydomain.com) by upgrading to a UCC certificate with the following domains requested:
mydomain.com*.mydomain.com*.subdomain.mydomain.com
In this setup, the new wildcard certificate for *.subdomain.mydomain.com would protect www.subdomain.mydomain.com (and, as noted, any other subdomain built upon subdomain.mydomain.com).
You can add any number of wildcard certificates to the UCC SSL for $129 a year, and the price will be prorated for any wildcards added (so that you would pay half that price for any websites added in six months, etc). The total price for this particular customer’s new setup would be $435, but we would apply any existing payments for their wildcard SSL to the new UCC certificate.
(As recommended, this configuration will also give protection to mydomain.com, but you could choose an alternate domain to protect for the same price.)
We can accommodate any desired SSL configuration at SSL.com – just contact us at Support@SSL.com or via the chat link on this page and we will find the solution you need.
