When you need one TLS certificate to cover more than a single hostname, you choose between a wildcard certificate and a multi-domain SAN certificate. A wildcard covers every host at one level under a domain, such as anything-dot-example-dot-com, using a single asterisk entry. A SAN certificate, sometimes called a multi-domain or UCC certificate, lists each exact hostname it covers. They solve overlapping problems with different trade-offs in coverage, security, and operations. This guide explains what each one actually covers, the risk of sharing one wildcard key across many services, and how to pick, or combine, them for your own setup.
What SAN really means
Every modern certificate carries a Subject Alternative Name list, and browsers decide which hostnames a certificate is valid for by reading that list and nothing else; the old Common Name field is ignored. This matters because both certificate types rely on the same SAN mechanism. A so-called SAN or multi-domain certificate simply lists several explicit names, for example example.com, www.example.com, and shop.example.com. A wildcard certificate puts a wildcard entry such as *.example.com into that same SAN list. In other words, wildcard and multi-domain are two ways of filling one field. Understanding the SAN list is the foundation for both, as detailed in our guide on how to check an SSL certificate issuer, chain, expiry, and SAN.
What a wildcard covers, and what it does not
A wildcard entry matches exactly one label in exactly one position. The entry *.example.com covers www.example.com, shop.example.com, and api.example.com, but it does not cover the bare apex example.com, and it does not cover a deeper name like a.b.example.com. The apex gap trips people up constantly: a single *.example.com certificate will throw a name mismatch on example.com itself unless the apex is added as its own SAN entry, which is why many wildcard certificates list both *.example.com and example.com. If you run multiple subdomain levels, you need a separate wildcard for each level, because one asterisk never spans two labels.
What a SAN certificate covers
A multi-domain SAN certificate covers precisely the names you list, and those names can span different registrable domains entirely. One certificate can carry example.com, example.net, and brand.io together, which a wildcard can never do because a wildcard is bound to a single parent domain. The cost is that the set is fixed at issuance: adding a new hostname means reissuing the certificate with the expanded list. That is fine when your hostnames are stable and known, and awkward when you spin up new subdomains on demand.
The security trade-off of a shared wildcard key
The convenience of a wildcard has a real downside. One wildcard certificate means one private key, and that single key is installed on every server that serves a covered subdomain. If any one of those servers is compromised, the attacker holds a key valid for every host under the wildcard. A SAN certificate issued per service, or a set of narrower certificates, contains the blast radius: a breach of one box exposes only the names on that box's certificate. The more sensitive and the more numerous your subdomains, the more that containment matters. A wildcard also makes blanket issuance easy for anyone who controls your DNS, which is one more reason to protect your DNS and your ACME automation tightly.
Wildcard versus SAN at a glance
The table below summarizes the practical differences as of November 2026.
| Dimension | Wildcard certificate | Multi-domain SAN certificate |
|---|---|---|
| Covers | All hosts at one level under one domain | An explicit list of exact hostnames |
| Spans different domains | No, one parent domain only | Yes |
| New subdomains | Covered automatically, no reissue | Require reissue with the new name |
| Apex example.com | Not covered unless added explicitly | Covered if listed |
| Private key exposure | One key valid for every subdomain | Exposure limited to listed names |
| Issuance via free ACME | Requires a DNS-01 challenge | HTTP-01 works per name |
How to choose for your setup
- List the exact hostnames you serve today and whether they sit under one domain or several.
- If you frequently create new subdomains under one domain, lean wildcard so you avoid reissuing for each new host.
- If your names are stable, span multiple domains, or include high-value services, lean toward SAN certificates issued per service to limit key exposure.
- Remember to add the apex as its own entry whenever a wildcard needs to cover the bare domain too.
- For wildcards from a free CA, plan for the DNS-01 challenge, since wildcards cannot be validated with HTTP-01.
- Consider a hybrid: a wildcard for low-risk marketing subdomains plus dedicated certificates for sensitive services such as auth or payments.
Whatever you choose, confirm the issued certificate actually lists the names you expect by running it through the Valla DNS SSL checker, which shows the full SAN list the server presents.
Cost and operational notes
With free automated CAs the price difference between the two types has largely disappeared, so the decision now turns on coverage and risk rather than cost. Operationally, a wildcard means fewer renewals to track but a bigger consequence if that one key leaks, while per-service SAN certificates mean more renewals to automate but tighter containment. Automation flips the math: once renewal is scripted, issuing several narrow certificates is nearly as cheap to run as one broad one, which nudges security-conscious teams toward narrower certificates even when a wildcard would be simpler.
Frequently asked questions
Does a wildcard certificate cover my apex domain?
No. A wildcard such as *.example.com covers one level of subdomain but not the bare apex example.com and not deeper labels like a.b.example.com. Add the apex as its own SAN entry if you need it covered, which is why many wildcard certificates list both.
Can one wildcard cover sub.sub.example.com?
No. A single asterisk matches exactly one label, so *.example.com matches sub.example.com but not sub.sub.example.com. To cover a deeper level you need a wildcard scoped to that level, such as *.sub.example.com.
Can a SAN certificate cover completely different domains?
Yes. A multi-domain SAN certificate can list names across unrelated registrable domains, such as example.com and example.net, in one certificate. A wildcard cannot, because it is bound to a single parent domain.
Which is more secure, wildcard or SAN?
Per-service SAN certificates are generally safer because each private key is valid for fewer names, so a single compromised server exposes less. A wildcard concentrates risk in one key installed everywhere it is used. Choose based on how sensitive and how numerous your hosts are.
Do I need a wildcard to get a free certificate for many subdomains?
Not necessarily. You can issue separate certificates per subdomain with HTTP-01 validation, or request a SAN certificate listing several names. A wildcard only becomes worthwhile when subdomains appear often enough that reissuing for each one is a burden.
Wildcard and SAN certificates are both just ways of filling the SAN list, so the real choice is between broad convenience and tight containment. Decide based on how your hostnames grow and how much a leaked key would cost you, then confirm the result on the SSL checker.