ERR_CERT_COMMON_NAME_INVALID means Chrome received a certificate that does not cover the website name it requested. Check the exact address first. If that address fails on updated devices and independent trusted networks, report it to the website owner rather than bypassing the warning.
Do not continue through the privacy warning to sign in, pay, or enter personal information. The error may be a website mistake, but it can also appear when a portal, filter, proxy, or unsafe network sends the wrong certificate.
What the error says about the website name
A website certificate identifies the hostnames it is allowed to protect. DigiCert’s current browser name-mismatch explanation ties ERR_CERT_COMMON_NAME_INVALID to a difference between the certificate name and the name shown in the browser address bar.
The certificate may cover example.com but not a different subdomain, or the server may present a certificate for another site. Chrome cannot safely assume that the mismatch is harmless. The browser stops before treating the connection as private.
Check the address before changing any settings
- Check the full hostname, spelling and unexpected subdomains.
- Open the official home page in a separate tab using an address you already trust.
- Keep any transaction or sign-in link intact; do not strip its parameters or resubmit a payment.
- Note whether the official main site works but an account or support subdomain fails.
- Do not follow a lookalike address suggested by an email or warning page.
A typo is not repaired by clearing the browser cache. If you reached the page through a message, search result, QR code, or shortened link, find the company’s official address through a source you already trust.
Compare one website with several websites
Open two familiar HTTPS websites in new tabs. If they work and only one domain shows the certificate-name error, the affected site or its subdomain deserves attention. Try the failing address in another current browser and on another updated device.
If one site also fails on an independent trusted network, that points toward the site’s certificate or routing setup. It is a useful clue, not proof of the cause. Avoid resetting a working router just because one site fails.
Pay attention to the exact subdomain
The main domain, www version, account portal, store, support center, and regional site can use separate hosting and certificates. One may work while another produces ERR_CERT_COMMON_NAME_INVALID.
Cloudflare’s current general SSL error guide tells site owners to check hostname proxying and certificate coverage, including deeper subdomains. A visitor cannot add the missing name to a certificate from Chrome.
Use another device on the same network
If another device opens the exact address on the same WiFi, focus on the original device. Install official browser and operating-system updates. Check its clock, especially if the displayed code is ERR_CERT_DATE_INVALID instead: an expiry/date warning is different from a hostname mismatch.
Compare a new Incognito window without signing into the affected site. It uses a separate session, and third-party cookies are blocked by default. Extensions allowed in Incognito can still run. A different result helps narrow the problem but does not prove an extension or cookie caused the certificate error. Keep security and privacy protections enabled.
Compare home WiFi with a phone hotspot
For an ordinary public page, compare home WiFi with your phone hotspot or another trusted connection. If the error disappears, investigate the original network’s portal or filtering path. Do not use a hotspot to bypass work or school policy, or test private internal services outside their approved network.
A hotspot result does not prove that the WiFi signal is bad. The wireless radio can work while a service farther along the connection redirects the hostname.
Finish a guest-network sign-in
Hotels, airports, cafes, apartments, and guest networks may intercept the first browser request until you accept their terms. Google’s current Chrome certificate-error guidance includes signing in to a WiFi portal before retrying the secure page.
Confirm the network name with the venue and use its official sign-in prompt. Never type a bank, email, or work password into a page that appears only after a certificate warning. If the portal will not load, forget the guest network and reconnect or ask staff for instructions.
Review VPN, proxy, antivirus, and parental controls
Some security products inspect HTTPS traffic by presenting a locally trusted certificate. A broken installation, expired inspection certificate, or incorrect rule can make the browser receive a name that does not match the requested site.
Keep antivirus, firewall, HTTPS inspection and managed protections enabled. Use the product’s official update or repair instructions, or ask its support team to check the certificate problem. On a school or work device, contact the administrator. Do not install a certificate, bypass policy or remove managed software yourself.
Treat errors on many familiar sites as urgent
If several well-known secure websites suddenly present certificates for an unrelated name, stop entering information. Disconnect from an unfamiliar network, close the affected pages, and try a trusted connection.
Check recently installed VPN, filtering, antivirus, parental-control, and workplace tools. If the problem follows one managed computer across networks, contact its administrator. If every home device sees the same unrelated certificate, contact the router-security service or internet provider.
A router or NAS login page is different
Local router, storage, printer, and camera pages may use a certificate created for a factory hostname while you open a numeric local address. That can produce a name warning even though ordinary internet routing still works.
Check the manufacturer’s supported hostname, app and current access instructions. If the warning persists, ask the manufacturer how to restore validated HTTPS access. Do not download a third-party certificate, add a browser exception, downgrade to HTTP or expose the administration page to the internet. A familiar local address does not by itself make a warning safe.
Why cache clearing and DNS changes are not first
A certificate-name mismatch is not the same as a stale image, failed page script, or slow DNS lookup. Clearing all cookies can sign you out without changing the certificate that the server presents. A random public DNS address can also obscure which service redirected the request.
Use a DNS-specific troubleshooting path only when the browser shows a name-resolution error or your comparisons point to one network’s resolver. Never edit the hosts file to force a sensitive website toward an address copied from a forum.
Do not bypass the privacy warning
- Do not continue to a login or payment page.
- Do not replace HTTPS with HTTP for a sensitive service.
- Do not install an unknown certificate.
- Do not disable certificate checks or browser protection.
- Do not use an old browser to avoid the warning.
- Do not press the router’s factory-reset button.
A bypass may hide a configuration mistake or an unsafe redirect. It does not make the certificate cover the requested hostname.
When the website owner must fix it
Contact the site when the correct address fails on updated browsers and independent trusted networks. Send the hostname, error code, time, time zone and comparison results. Do not send passwords, cookies or full sign-in URLs containing private tokens.
The operator should confirm that the requested hostname appears in the certificate, the correct certificate is served for that hostname, redirects point to covered names, and proxy or delivery settings route the request to the intended service. Visitors should not be asked to ignore the warning.
Match the next step to the pattern
| Pattern you observe | Safe next step |
|---|---|
| One correct site fails across independent trusted connections | Report the hostname and code to its owner. |
| Only one device fails | Check official updates and ask security-product support or your administrator. |
| Only one network fails | Verify its portal and ask the venue, filtering provider or ISP. |
| Several sites show unrelated certificate names | Stop entering information; investigate possible interception. |
| Only a local device page fails | Ask its manufacturer about supported secure access. |
If only one computer has trouble reaching otherwise working sites, use the one-device WiFi checklist. If every device loses normal access, use the WiFi or internet outage comparison. Keep the privacy warning in place until the address and certificate match.
