A wildcard certificate covers only one left-most label, not every subdomain
A certificate issued for *.example.com may look like a broad solution for a large service estate, but its coverage is narrower than many teams expect. Under RFC 9525, a wildcard is valid only as the complete left-most label, and the identity must be carried in subjectAltName rather than the common name. As a result, it does not automatically cover the bare domain or names with multiple extra labels. The article also stresses that a valid certificate alone does not confirm tenant ownership, application intent, or whether an endpoint should be reached, since those depend on configuration, DNS, and authorization. It recommends inventorying every SAN and securing the wildcard's private key, which can impersonate any matching single-label hostname, along with testing how each client library validates identities.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in