Wildcard vs multi-domain SSL: choose by website names
Write down the exact names first. A wildcard pattern and a list of separate domain names solve different coverage needs.
One domain with several subdomains
A wildcard pattern such as *.example.com can match shop.example.com and mail.example.com. It does not by itself match example.com or a deeper name such as api.shop.example.com. Check whether the selected product includes the root domain separately and whether additional wildcard names are supported.
Several different domains
A multi-domain certificate can include a list such as example.com, example.net and portal.example.org in its Subject Alternative Name extension. Included name counts, additional SAN prices and allowed combinations vary. Some products support wildcard names alongside ordinary names; the label alone does not establish that entitlement.
Compare the full configuration
- List every name, including root and www versions when needed.
- Group subdomains by level and ownership.
- Choose the validation level required by your organisation or specification.
- Check included names, maximum names and additional SAN charges.
- Compare the same subscription term and the complete BDT total.
Consider operational responsibility
A single certificate spanning several services creates shared renewal and replacement work. Check who owns each system and whether their change windows align. Separate certificates may be easier for independently managed services. The best choice depends on the names, responsibilities and product terms, not only the cheapest headline amount.
See current options
Use the wildcard catalogue for subdomain products and the multi-domain catalogue for several names. Product pages provide the available terms and configuration. If the required combination is unclear, request a quotation with public names and the validation requirement. Do not send private keys or hosting passwords.
Before choosing a long plan, read subscription length versus certificate expiry.
Common questions
Does *.example.com automatically cover example.com?
The wildcard pattern itself does not match the root name. Check that example.com is separately included by the selected product and in the issued certificate.
Can a multi-domain certificate include wildcard names?
Some products support that combination. Confirm the exact product's capabilities, included names, validation level and extra SAN pricing.
Which option is cheaper?
Compare the complete set of required names and the same subscription length using current approved prices. A category starting price cannot establish the cost of your configuration.