Skip to content

ERR_CERT_COMMON_NAME_INVALID: Domain Mismatch

TL;DR:

ERR_CERT_COMMON_NAME_INVALID (NET::ERR_CERT_COMMON_NAME_INVALID) means the requested domain is not listed in the certificate's SAN field. Example: cert issued for example.com but you open www.example.com. Fix: reissue the certificate with both domains in SAN, or use wildcard *.example.com.

This error is a frequent issue in SSL debugging. We cover the causes and step-by-step fix.

Check your site's SSL →

What ERR_CERT_COMMON_NAME_INVALID means

ERR_CERT_COMMON_NAME_INVALID (NET::ERR_CERT_COMMON_NAME_INVALID) means the requested domain is not listed in the certificate's SAN field. Example: cert issued for example.com but you open www.example.com. Fix: reissue the certificate with both domains in SAN, or use wildcard *.example.com.

The error can appear in Chrome, Edge, Opera, Brave (all Chromium-based), and partially in Firefox and Safari. Different browsers display the same code differently, but the underlying issue is the same.

How to fix (step-by-step)

  1. Check the SSL certificate online — the Enterno.io checker shows the grade, expiry, chain, and specific cause.
  2. If the issue is server-side — reissue the certificate via certbot or your chosen CA.
  3. Update nginx/apache config (enable TLS 1.2/1.3, fullchain, correct ciphers).
  4. Check kernel OpenSSL — an outdated openssl < 1.1 can break handshakes.
  5. After deploy: recheck via SSL checker + clear the browser SSL cache.

Check SSL now →

Related SSL errors

TL;DR: Fixing ERR_CERT_COMMON_NAME_INVALID

The ERR_CERT_COMMON_NAME_INVALID error occurs when the common name (CN) in the SSL certificate does not match the domain name in the URL. To resolve this, ensure that the SSL certificate is correctly configured for your domain. Check the certificate's CN and Subject Alternative Names (SAN) using tools like OpenSSL and update or reissue the certificate as necessary. For example, use the command openssl s_client -connect yourdomain.com:443 to inspect the certificate details.

Understanding the ERR_CERT_COMMON_NAME_INVALID Error

The ERR_CERT_COMMON_NAME_INVALID error is a common issue encountered when accessing websites secured with SSL/TLS. This error indicates a mismatch between the domain name requested by the user and the common name specified in the SSL certificate. The common name is a critical part of the SSL certificate, which helps establish trust between the user and the server.

When a user navigates to a website, the browser checks the SSL certificate to verify its authenticity. If the common name in the certificate does not match the domain name, the browser will display the ERR_CERT_COMMON_NAME_INVALID error. This can occur for several reasons:

  • The SSL certificate was issued for a different domain.
  • The certificate has expired or is not yet valid.
  • The server is misconfigured, serving the wrong certificate.
  • The user is accessing the site through a subdomain that is not covered by the certificate.

To prevent this error from occurring, it is essential to ensure that the SSL certificate is configured correctly and that it covers all necessary domain variations, including www and non-www versions, as well as any subdomains. Regular audits of SSL certificates can help identify potential issues before they affect users.

Practical Steps to Resolve ERR_CERT_COMMON_NAME_INVALID

To fix the ERR_CERT_COMMON_NAME_INVALID error, follow these practical steps:

  1. Check the SSL Certificate: Use the following OpenSSL command to verify the certificate details:
openssl s_client -connect yourdomain.com:443 -showcerts

This command will display the certificate chain. Look for the Subject field to identify the common name and ensure it matches your domain.

  1. Update the SSL Certificate: If the common name is incorrect, reissue the SSL certificate with the correct domain name. Ensure that the certificate includes all necessary Subject Alternative Names (SAN) to cover variations of your domain.
  2. Check Server Configuration: Ensure that your web server is configured to serve the correct SSL certificate. For example, in an Apache server, check the VirtualHost configuration:
<VirtualHost *:443>
    ServerName yourdomain.com
    ServerAlias www.yourdomain.com
    SSLEngine on
    SSLCertificateFile /path/to/your/certificate.crt
    SSLCertificateKeyFile /path/to/your/private.key
    SSLCertificateChainFile /path/to/your/chainfile.pem
</VirtualHost>
  1. Clear Browser Cache: After updating the certificate, clear your browser cache or try accessing the site in incognito mode to eliminate cached data that may still trigger the error.
  2. Test with Different Browsers: Sometimes, different browsers may handle SSL certificates differently. Test your site on multiple browsers to ensure the issue is resolved across the board.

By following these steps, you can effectively troubleshoot and resolve the ERR_CERT_COMMON_NAME_INVALID error, ensuring a secure and trustworthy experience for your website visitors.

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Sources

Frequently Asked Questions

Is it safe to ignore ERR_CERT_COMMON_NAME_INVALID?

No. This error indicates a real SSL certificate problem. Ignoring it (via chrome://flags or "thisisunsafe") makes the connection vulnerable to man-in-the-middle attacks. Fix it on the server side.

How can I catch this error early?

Use the <a href="/en/ssl">Enterno.io SSL/TLS checker</a>, or <a href="/en/monitors">set up monitoring</a> with 14-day expiry alerts. Receive an email/Telegram notification before your users see the error.

Does clearing cookies / cache help?

Sometimes, for transient cached SSL errors. Steps: chrome://net-internals/#sockets → Flush sockets, chrome://net-internals/#hsts → Delete domain security policies (carefully, for debugging only). But if the issue is server-side, cache clearing will not help.

Is Let's Encrypt free — and is the certificate trusted?

Yes, Let's Encrypt certificates are in every modern trust store (Chrome, Firefox, Safari, Edge). 90-day validity with automatic renewal via certbot. No reason to use a paid CA for a standard website.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.