ERR_CERT_COMMON_NAME_INVALID — How to Fix [2026]

Enterno.io Editorial Team

ERR_CERT_COMMON_NAME_INVALID: Domain Mismatch

By Anatoly Oshmanovsky · Updated Apr 17, 2026

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.

Try it now — free →

What ERR_CERT_COMMON_NAME_INVALID means

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)

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

Check SSL now →

Related SSL errors

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

Enter domain

TLS chain verified

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.

Learn more

How-to

Glossary

Research

TLS Cipher Suites 2026: Distribution Report

Errors

Alternatives

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.