` reads). %> Why Your Wildcard Certificate Is a Bigger Problem Than You Think | TLS Radar Skip to main content
lifecycle 6 min read By TLS Radar Team

Why Your Wildcard Certificate Is a Bigger Problem Than You Think

A master key for an apartment building is wonderfully convenient. The building manager carries one key. They open the laundry room, the bin store, the mailbox cabinet, the maintenance closet, every unit's front door. One key, one keychain, no fumbling. It's lovely.

It's also the building's biggest single security risk.

If the master key is lost, every door in the building is potentially compromised. If a contractor copies it during a renovation, every tenant's privacy is at risk for as long as the lock cylinders are unchanged. If the building manager leaves under bad circumstances, the building has to consider rekeying every door - a logistical nightmare. The convenience of the master key is real, and so is the cost. Sensible buildings limit how many master keys exist, who holds them, and how often they get changed.

A wildcard TLS certificate is the master key of your domain.

It covers *.example.com - every subdomain, in one cert. One key for many doors. Convenient for ops. A blast radius the size of your whole subdomain space if it's ever compromised. Most teams treat wildcards as a free convenience. They are not free; they just hide the cost.

Here's why wildcards are riskier than they look, where the costs actually land, and when they're worth it anyway.

What wildcards are and why teams use them

A wildcard cert has a SAN entry like *.example.com. It validates against any single-level subdomain - api.example.com, www.example.com, staging.example.com. Most CAs offer them. Let's Encrypt supports them via DNS-01 validation.

Teams reach for wildcards because they solve a real problem: managing many subdomains without a separate cert per subdomain. A team that spins up new subdomains weekly doesn't want to manage hundreds of separate certs and their separate renewal cycles. A wildcard covers them all.

This is the convenience side. It's a genuine convenience.

The blast radius problem

The cost is what happens when something goes wrong.

A wildcard cert has a single private key. That key signs every TLS handshake on every subdomain it covers. If the key is compromised, every subdomain is compromised simultaneously. An attacker can impersonate any of them.

How keys get compromised: - A backup of a server containing the private key ends up on an attacker-accessible system. - A developer commits the private key to a public Git repository (this happens more than you'd think - CT logs sometimes find these, and so do GitHub's secret scanners). - A vendor with the key in their custody has a breach. - A long-lived key sits in a system that gets hacked through some other path.

For a single-subdomain cert, this is a one-subdomain problem. Re-issue the cert, rotate the key, move on. For a wildcard covering forty subdomains, the same incident affects forty subdomains. The remediation is larger and harder to coordinate.

The blast radius is a hidden cost of the wildcard. Most teams don't price it in because compromise feels unlikely. But "unlikely" multiplied by "very bad" is still a meaningful number.

The ownership confusion problem

Wildcards create a second, less obvious problem: who owns the cert?

A wildcard for *.example.com covers subdomains owned by multiple teams. Marketing's campaign.example.com. Engineering's api.example.com. Sales' app.example.com. Each team thinks of "their" subdomain as theirs. The cert that protects all of them is owned by... whom?

The usual answer: a central team owns the cert. The other teams use it. This works until something goes wrong:

  • The cert is up for renewal. The central team renews. They don't notice that Marketing has added six new subdomains since the last renewal, three of which need to be tested against the new cert. A subdomain needs a different SAN configuration. The teams disagree about whether to fork the wildcard into multiple certs. A compliance audit requires per-cert ownership documentation. The wildcard has many users, one owner. The auditor finds this unsatisfying.

The ownership confusion is harder to fix than the blast-radius issue because it's organisational, not technical. Single-subdomain certs naturally have a single team owning them. Wildcards have to be wedged into ownership models that don't fit them.

The depth problem (briefly)

Covered in detail in Hostname Mismatch and SAN Sprawl (an earlier piece). A quick recap: wildcards cover exactly one level of subdomain. *.example.com covers api.example.com, not v1.api.example.com. Teams forget this constantly. The recovery is painful.

When to use wildcards anyway

Wildcards aren't always wrong. Real situations where they make sense:

Short-lived ephemeral subdomains. A platform that creates user-specific subdomains (user1.app.example.com, user2.app.example.com) cannot pre-register each one. A wildcard is the only practical option.

Internal/staging environments where the blast radius is contained and the operational simplicity wins. The risk profile of an internal-only wildcard is different from a public-facing one.

High-churn subdomain spaces. Marketing landing pages, dev environments, A/B test domains. Managing per-subdomain certs is impractical.

When you'll never need different cert properties for different subdomains. If every subdomain genuinely needs the same SAN structure, key length, and renewal schedule, the wildcard simplifies things.

When not to use them:

  • Production-facing subdomains owned by different teams with different risk profiles. Any subdomain that handles sensitive data and would benefit from a smaller blast radius. Audit-heavy compliance environments (FedRAMP, certain financial regulations) where per-cert ownership matters.

The practical alternatives

Most situations that look like "we need a wildcard" actually look like "we need automation." If issuing per-subdomain certs were as cheap as renewing one wildcard, there'd be no reason for wildcards at all.

ACME automation, especially with DNS-01 validation, makes per-subdomain issuance basically free in operational terms. Some teams maintain hundreds of named certs with no manual work, because the automation does the registration.

Internal CAs (Vault PKI, step-ca) make this even easier for internal subdomains. Each service gets its own cert. The blast radius is one service. The ownership is clear.

For organisations that can move to per-subdomain certs, the wildcard isn't a convenience - it's a workaround for missing automation.

One small ask

Wildcards aren't bad. They're an explicit trade-off - operational simplicity for blast radius and ownership clarity. Teams that have made the trade deliberately tend to use them well. Teams that fell into using wildcards because they were the path of least resistance tend to discover the costs during a key compromise, an ownership dispute, or a compliance audit. TLS Radar monitors wildcards alongside everything else - including alerting when the wildcard's SAN coverage doesn't match the actual subdomains being served. The 30-day free trial covers three domains, which is enough to see where your current wildcards are doing more work than you realised.

Related reading

Get the next post in your inbox

TLS monitoring tips and product updates. No spam, unsubscribe anytime.

Keep reading

Comparing tools? See how TLS Radar stacks up against DigiCert and SSL.com.