What it means
The certificate, or the request for one, lists no names in its Subject Alternative Name extension. Its only name is the common name in the subject. Long ago browsers read that field; today they read only the Subject Alternative Name list.
Why it matters
Chrome, Firefox, Safari and Edge reject a certificate without a Subject Alternative Name for every host, even when the common name matches exactly. Visitors see a name mismatch warning and most API clients refuse to connect. Public certificate authorities always add the list, so a certificate without one is usually self-signed or made by an internal tool with old defaults, and a request without one may be refused or turned into a certificate for the common name only.
How to fix it
- Make a new CSR that requests every name the certificate must cover, including the main name. The CSR generator always puts the common name in the list too.
- With OpenSSL, add
-addext "subjectAltName=DNS:example.com,DNS:www.example.com"toopenssl req, or asubjectAltNameline in the configuration file's request extensions. - For an internal certificate authority, check that its signing profile copies the requested names into the certificate.
- Order or issue the new certificate and install it in place of the old one.
Check it worked
Paste the new certificate or request into the certificate decoder: "Names covered" should list every host name. For a live site, the SSL checker shows the names the server's certificate covers.