In short. This error means your website's security certificate (its proof of identity, which makes the secure connection possible) was issued for a different address than the one the visitor typed, for example with "www" but not without, or a forgotten subdomain. Those visitors see a warning and may leave without entering your site. It is up to you, or to your hosting provider or web provider, to get a certificate issued that covers every address of your site. Usually allow a few minutes of configuration.
NET::ERR_CERT_COMMON_NAME_INVALID means the certificate served by the site was issued for a different name than the address visited. Typical cases: the certificate covers your-domain.com but not www.your-domain.com (or the reverse), it does not cover a subdomain, or the host serves another site's certificate. The fix: issue a certificate that contains every name in use.
Last verified: November 18, 2026, in the Chromium and Firefox source code.
What your visitors see
Chrome shows "Your connection is not private", with the code NET::ERR_CERT_COMMON_NAME_INVALID. Under Advanced, it names the two domains involved (Chromium text):
This server could not prove that it is www.your-domain.com; its security certificate is from your-domain.com. […]
Firefox shows "Warning: Potential Security Risk Ahead", with the code SSL_ERROR_BAD_CERT_DOMAIN, and lists the names the certificate is valid for.
This message is the most useful of the three: it says exactly which name is missing.
Step 1: list the names covered
Run our free SSL certificate check on the address in error, or open the certificate details in the browser. The names covered appear in the "Subject Alternative Name" field. That is the field browsers read, not only the "common name" that gave the error its name.
Compare with the address visited:
wwwmissing or extra: the most frequent case. The certificate was issued for only one of the two forms.- Subdomain missing:
shop.your-domain.comis not covered by a certificate issued foryour-domain.com. - Wildcard certificate (
*.your-domain.com): it covers a single level.shop.your-domain.comyes,www.shop.your-domain.comno, and the bare domainyour-domain.comno either. - Name unrelated to your site: the host serves a default certificate or another customer's. Often, the domain points to a server that does not know it (DNS set wrongly after a change of host).
Step 2: issue a certificate with all the names
- Shared hosting: in the customer area, add the missing form (
wwwor the subdomain) to the domain, then restart the certificate issuance. Most hosts then cover both forms. - Server you manage: request a certificate that lists all the names, for example with certbot:
-d your-domain.com -d www.your-domain.com. - Wrong server: first fix the DNS so the domain points to the right hosting, then issue the certificate.
Step 3: redirect to a single address
Once both forms are covered, redirect one to the other with a 301 redirect (for example your-domain.com to www.your-domain.com). Be careful: the redirect does not replace the certificate. The browser checks the certificate before following the redirect: the redirected form must be covered too.
Step 4: check
Run the free tool again on every address: with www, without www, and every public subdomain.
Check your certificate for free. AttackScout reads the certificate of every address of your domain and flags the ones it does not cover. Check my domain
Frequently asked questions
The site works with www but not without. Is that serious?
Yes. Some visitors type the address without www, and shared links often use it. They see a warning instead of your site.
I have a wildcard certificate. Why is the bare domain in error?
*.your-domain.com does not cover your-domain.com. You need to add that name to the certificate.
The error appeared after a change of host.
The domain may still point to the old server, or the new one has not yet issued a certificate for it. Check the DNS, then the certificate issuance at the new host.
Sources
Accessed on 11/18/2026.
- Chromium,
IDS_CERT_ERROR_COMMON_NAME_INVALID_DETAILS(components/ssl_errors_strings.grdp) and its translations (components/strings/components_strings_<language>.xtb): https://github.com/chromium/chromium/tree/main/components - Firefox,
cert-error-domain-mismatch(certError.ftl) andSSL_ERROR_BAD_CERT_DOMAIN(nsserrors.properties): https://github.com/mozilla-firefox/firefox - IETF, RFC 9525 (certificate name verification, wildcard limited to the first level; replaces RFC 6125): https://www.rfc-editor.org/rfc/rfc9525
- Certbot, documentation (
-dfor each name): https://eff-certbot.readthedocs.io/en/stable/using.html