apex SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

Wildcard certificate *.example.com doesn't cover example.com (the bare domain)

A wildcard covers subdomains one level deep, but not the apex domain itself, so https://example.com shows a name mismatch.

Exact message you may see wildcard certificate does not cover the apex domain*.example.com does not match example.comNET::ERR_CERT_COMMON_NAME_INVALID bare domain wildcardwildcard SSL doesn't include root domaincertificate only valid for *.example.com
Seen on: SSL Chrome

Meaning

Add both names to the certificate: example.com and *.example.com in the SAN list (most CAs issue the wildcard with the apex included on request). Reissue and redeploy.

Common causes

  • Certificate issued only for *.example.com
  • Apex requested separately by mistake
  • CA/plan limiting SANs
  • Redirect from apex to www skipping HTTPS
  • Old certificate still deployed

⚡ Quick fix

  1. Reissue with example.com and *.example.com
  2. Verify SANs: openssl x509 -noout -ext subjectAltName
  3. Update the load balancer/server

Detailed fix by platform

Shell

  1. sudo certbot certonly --dns-cloudflare -d example.com -d "*.example.com"

How to diagnose

  1. SANs — Include apex?
  2. Wildcard — Level?
  3. Cert — Redeployed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

CNAME — CloudFront: CNAMEAlreadyExists / alternate domain name not covered by the certificate (InvalidViewerCertificate) (SSL / TLS)CNAMEDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)Djangoerror 62 — openssl verify error:num=62:Hostname mismatch / Verify return code: 62 (SSL / TLS)error 62hostname — Java: SSLPeerUnverifiedException — Certificate for <host> doesn't match any of the subject alternative names (SSL / TLS)hostnamelegacy CN — Go: x509: certificate relies on legacy Common Name field, use SANs instead (SSL / TLS)legacy CNSAN — Self-signed/CSR certificate rejected: no Subject Alternative Name (openssl req needs -addext) (SSL / TLS)SANSAN limit — Certificate request failed: too many domain names in one certificate (SAN limit exceeded) (SSL / TLS)SAN limitSSL_ERROR_BAD_CERT_DOMAIN — Firefox: Websites prove their identity via certificates — the certificate is only valid for other names. Error code: SSL_ERROR_BAD_CERT_DOMAIN (SSL / TLS)SSL_ERROR_BAD_CERT_DO…apex

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.