Actually, wildcards only work on the first level of a subdomain in most browsers. So a wildcard certificate for *.example.com wouldn't work on mail.test1.example.com.
Web browsers also don't know what to do with a certificate for somthing.*.example.com either. You best option is to get a SAN certificate that you can include the specific hostnames in no matter what level they are on.
Actually, wildcards only work on the first level of a subdomain in most browsers. So a wildcard certificate for *.example.com wouldn't work on mail.test1.example.com.
Web browsers also don't know what to do with a certificate for somthing.*.example.com either. You best option is to get a SAN certificate that you can include the specific hostnames in no matter what level they are on.
In case it helps anyone, double wildcard certs don't actually work.
(from firefox)
www.test.example.com
uses an invalid security certificate.The certificate is only valid for
*.*.example.com
(Error code: ssl_error_bad_cert_domain)
As ceejayoz says - a standard wildcard certificate will do exactly what you desire.
I assume you're looking for that style of certificate because you want something cheaper? If so, then no can do, you have to purchase a wildcard.
As wildcard SSL certificate is used to secure unlimited number of sub-domains(first level).
Example 1: To secure *.domainname.com, you need to buy Wildcard SSL certificate for Doaminname.com,
Here in this case, domainname.com will be your first level domain.
Example 2: To secure something.*.domainname.com, you need to buy wildcard for *.domainname.com,
Here in this case, *.domainname.com will be your second level domain.