What it means
A certificate lists the exact host names it is valid for. The certificate your server sends for this name
doesn't include it; the detail shows the names it does cover. A frequent case is a certificate for
www.example.com served on example.com, or the reverse. Another is a wildcard such as *.example.com,
which covers www.example.com but never example.com itself.
Why it matters
Browsers show a security warning for any name the certificate doesn't cover, even when the certificate is otherwise valid. Visitors who type the name without www, or follow an old link, land on that warning.
How to fix it
- Decide which names should work. Usually that is the bare domain and www.
- Issue a certificate that lists all of them. Automatic issuers take several names at once; a wildcard certificate covers subdomains, but the bare domain must still be listed separately.
- Install the new certificate on every server and load balancer that answers for these names, then reload.
- If a name shouldn't serve a site, keep it covered anyway and redirect it to your main name: the redirect only happens after the secure connection is made.
Let's Encrypt with certbot
Request both names together: sudo certbot --nginx -d example.com -d www.example.com, or use --apache.
Cloudflare
Cloudflare's edge certificate covers the domain and one level of subdomains when the names are proxied. A mismatch usually means the name isn't proxied, so traffic goes straight to your server and its own certificate.
Check it worked
Run the SSL check again. Every card should list the host name among the names covered and say "Trusted".