A ctlplne studio product
22 October 2026 · 3 min read

The wildcard six teams share

Every estate has one. The wildcard for *.example.com was requested years ago by someone who has left, and six teams copied its private key into six places. Nobody owns it, everyone depends on it, and from March 2029 it has to be replaced everywhere at least every 47 days.

Discovery and inventoryKey protectionAudit and ownershipThe 47-day schedule

What a wildcard actually is

A wildcard certificate names *.example.com: one certificate and one private key that any host directly under that domain can present.1 The convenience is obvious. The cost is that the private key, the one thing a certificate exists to keep in one place, is now in every place. Whoever holds it can impersonate every service under the name, and the authorities know it: the Baseline Requirements rule out the HTTP and TLS-ALPN challenges for wildcards, because those prove control of a single host, and Let's Encrypt requires the DNS challenge for every wildcard it issues.1,2

One wildcard private key copied to six services, with one renewal that has to reach all of them at once *.example.com one private key api.example.com, platform teamwww.example.com, marketing agencyvpn.example.com, ITgrafana.example.com, SREold-portal.example.com, nobodystaging-*.example.com, developer laptops
Six deployments, six renewal paths, one key. A leak on any line is a leak of every line.

What short lifetimes do to it

  • Every copy has to change at once. A renewal is not done until all six places serve the new certificate, and each place has its own deployment path, or none. At twelve renewals a year the odds that one of them is missed each cycle are not small.
  • The blast radius does not shrink. Short lifetimes limit how long a stolen key is useful. They do nothing about how many services one stolen key covers.
  • The logs tell on you. Every issuance of the wildcard is in the transparency logs.3 What they cannot tell you is where the key went afterward.
  • Nobody owns it. Six teams depend on it, so each assumes another one manages it. "Owner: unknown" is a common attribute of a wildcard.4

When a wildcard is still right

When the names are genuinely dynamic and short-lived, such as per-tenant or per-preview subdomains that appear and disappear faster than issuance could follow, a wildcard on a single, well-guarded edge is the right tool. The rule that keeps it safe is one key, one place: the wildcard terminates on one system, the key never leaves it, and the services behind it get their own certificates from a private authority.

How to unwind the other kind

  1. Find every copy. Scan for the wildcard's fingerprint across your address ranges; each hit is a deployment, and each deployment is a team to talk to.
  2. Give it one owner now, even if that owner's first job is to retire it.
  3. Issue per-service certificates through ACME for everything that has a stable name. Most of the six lines above are stable names.
  4. Rotate the wildcard's key once the copies are gone and revoke the old certificate, so the key that was everywhere stops being trusted.

trstctl's discovery joins certificates on fingerprint, so a wildcard shows up as one certificate, with a discovery finding for each place a scan sees it, and ownership attribution keeps it marked orphaned until someone owns it.4

Sources

  1. CA/Browser Forum, TLS Baseline Requirements, version 2.3.1: the definition of Wildcard Domain Name, and the section 3.2.2.4 table that rules out the HTTP and TLS-ALPN methods for wildcards.
  2. Let's Encrypt, FAQ: "Wildcard issuance must use the DNS-01 challenge."
  3. Google Chrome, Certificate Transparency Policy.
  4. trstctl documentation, Discovery and inventory: ownership attribution and the unified inventory.