Attempting to open an intranet portal, web application, or public website in Microsoft Edge only to have your navigation blocked by a red warning screen reading: “Your connection isn’t private. Attackers might be trying to steal your information from [domain]… NET::ERR_CERT_COMMON_NAME_INVALID” stops web browsing immediately. In modern TLS/SSL security architecture, web browsers verify that the domain name typed into the address bar matches the cryptographic Subject Alternative Name (SAN) or Common Name (CN) embedded within the host server’s digital certificate. When a server administrator configures a certificate that omits the www prefix, fails to include a wildcard domain, or binds a multi-tenant IP address to the wrong virtual host, Chromium’s cryptographic engine rejects the handshake. This guide explains why this certificate mismatch occurs and provides verified methods to fix it.
What Causes NET::ERR_CERT_COMMON_NAME_INVALID in Edge?
The TLS handshake terminates with this specific error due to several certificate and network mismatches:
- Domain Name vs Certificate SAN Mismatch: The certificate is valid for
example.com, but you accessedwww.example.com(or vice versa), and the administrator omitted the alternative SAN record. - Outdated or Incorrect Local System Clock: If your PC’s date and time are misaligned, Edge calculates certificate validity ranges incorrectly against active timestamp authorities.
- Third-Party Antivirus HTTPS / SSL Scanning: Security suites (such as Avast, Bitdefender, or Kaspersky) that inject local man-in-the-middle root certificates to inspect encrypted traffic generating mismatched common names.
- Stale Public DNS and Host Resolvers: Local DNS caches pointing to an old server IP address hosting a completely different website with a different certificate.
- Unconfigured Self-Signed Certificates on Intranets: Development servers (such as local staging nodes or router admin consoles) utilizing self-signed SSL certificates lacking proper localhost SAN attributes.
Method 1: Verify the URL Prefix (www vs non-www)
The most frequent trigger on public websites is an SSL certificate configured for only one domain variant.
- Look at the address bar in Microsoft Edge.
- If the current URL includes
www.(e.g.,https://www.example.com), click into the address bar, removewww., and press Enter to loadhttps://example.com. - Conversely, if the URL lacks
www., try prefixing it withwww.. - If the website loads securely upon changing the prefix, the webmaster failed to include both variants in their certificate Subject Alternative Name (SAN) list.
Method 2: Verify and Synchronize Windows System Date and Time
Cryptographic certificates carry strict Not Before and Not After validity timestamps. Clock drift causes Edge to miscalculate certificate status.
- Right-click the Date and Time display on your Windows taskbar (bottom-right corner) and select Adjust date and time.
- Ensure the switch for Set time automatically is toggled to On.
- Ensure Set time zone automatically is also toggled to On.
- Scroll down to the Additional settings section and click the Sync now button.
- Once the checkmark confirms successful time server synchronization, return to Microsoft Edge and refresh the page.
Method 3: Clear Microsoft Edge SSL State and Host Cache
Corrupted SSL session tickets cached in the Windows cryptographic subsystem can force Edge to reuse obsolete certificate handshakes.
- Press Win + R, type
inetcpl.cpl, and press Enter to open Internet Properties. - Switch to the Content tab.
- Click the Clear SSL state button. A prompt will confirm: “The SSL cache was successfully cleared.” Click OK.
- In Microsoft Edge, navigate to the internal DNS diagnostics page:
edge://net-internals/#dns - Click the Clear host cache button.
- Relaunch Microsoft Edge and test navigation to the target domain.
Method 4: Disable Third-Party Antivirus HTTPS Scanning
Security software attempting to filter encrypted web traffic intercepts SSL certificates and issues self-signed proxies that trigger common name mismatches.
- Open your installed third-party antivirus dashboard (e.g., Avast, AVG, Bitdefender, ESET).
- Navigate to Settings > Core Shields > Web Shield (or Network Protection).
- Look for an option named Enable HTTPS Scanning, Scan encrypted connections, or Check SSL/TLS protocols.
- Temporarily disable this setting.
- Restart Microsoft Edge. If the site loads without the warning, the antivirus proxy certificate was improperly signed or out of date.
Method 5: Bypass the Warning on Trusted Development / Intranet Sites
If you are accessing an internal office server, router management console, or development staging node where you know the certificate is safe despite the mismatch:
- On the red warning page in Microsoft Edge, click the Advanced button at the bottom.
- A detailed diagnostic paragraph will expand.
- Click the link reading: Continue to [domain] (unsafe).
- Edge will establish the connection and permit navigation for that browser session.
- Note: Never bypass this warning when accessing banking portals, ecommerce checkouts, or sites requiring personal login credentials over public networks.
Common Name Invalid Troubleshooting Matrix
| Issue Cause | Diagnostic Indicator | Primary Resolution |
|---|---|---|
| Missing SAN Record | Site loads without www | Adjust address bar URL to match certificate SAN |
| Windows Clock Drift | Certificate dates invalid | Sync time automatically in Windows Settings |
| Stale Certificate Cache | Error persists after fix | Clear SSL state via inetcpl.cpl |
| Antivirus Proxy Hook | Certificate issued by AV vendor | Disable HTTPS / SSL scanning in antivirus suite |
Checking URL prefixes and clearing Windows SSL session states permanently resolves common name validation errors and restores secure browsing in Microsoft Edge.