Opening Google Chrome to browse everyday search results, check banking portals, or read online news only to find that every single website triggers an ominous “Not Secure” badge in the address bar—or blocks navigation completely with a full-screen interstitial warning reading: “Your connection is not private (NET::ERR_CERT_AUTHORITY_INVALID or NET::ERR_CERT_DATE_INVALID)”—is an alarming experience. While users immediately assume their network has been compromised or that every site has been hacked, an across-the-board security warning across all legitimate domains is virtually always a client-side certificate validation failure on your local device. In modern web architecture, Google Chrome verifies cryptographic SSL/TLS certificates issued by certified Certificate Authorities (CAs) against your local operating system’s root certificate store and Chrome’s built-in Root Store. When your local system clock falls out of synchronisation, when third-party antivirus software injects corrupted SSL inspection certificates, or when Windows root certificates expire, Chrome loses trust in all encrypted traffic. This guide outlines how to diagnose and fix universal ‘Not Secure’ errors in Chrome.
What Causes the ‘Not Secure’ Warning Across All Websites in Chrome?
Because universal certificate failures occur at the root validation level, common causes include:
- Desynchronised System Date and Time: SSL/TLS certificates are strictly valid only between defined issuance and expiration timestamps. If your computer’s clock drifts by even a few hours, valid certificates fail cryptographic validity windows.
- Third-Party Antivirus HTTPS / SSL Scanning: Security suites (Kaspersky, Avast, ESET, Bitdefender) intercept encrypted HTTPS traffic by installing a local proxy certificate. If this root certificate corrupts, Chrome rejects all web connections.
- Outdated Windows Trusted Root Certification Authorities: Missing Windows root certificate updates leaving your operating system unable to verify modern cryptographic signatures (such as modern Let’s Encrypt or DigiCert chains).
- Misconfigured Chrome Security Flags: Experimental security flags (such as strict HTTPS-First mode or invalid certificate allowance overrides) misconfigured in
chrome://flags. - Corrupted Local SSL State and Browser Cache: Fragmented SSL session tokens stored in the Windows Cryptographic Services cache rejecting handshake renewals.
Method 1: Correct and Synchronise Windows Date and Time
An inaccurate system clock is the number one cause of sudden, system-wide SSL certificate rejections.
- Press Win + I to open Windows Settings.
- Click on Time & language in the left sidebar, then select Date & time.
- Ensure the toggle for Set time automatically is switched On.
- Ensure the toggle for Set time zone automatically is switched On.
- Under the Additional settings section, locate Sync your clock and click the Sync now button.
- Verify that the date, month, year, and time match your exact current local time.
- Restart Google Chrome and test navigating to previously blocked websites; certificate errors will instantly vanish.
Method 2: Disable HTTPS / SSL Scanning in Third-Party Antivirus
Third-party security suites act as “man-in-the-middle” proxies to inspect web traffic; disabling this inspection restores native browser encryption.
- Open your installed third-party antivirus interface (e.g. Avast, AVG, ESET, Bitdefender, or Kaspersky).
- Navigate to Settings > Core Shields or Web Protection.
- Locate the setting named Enable HTTPS scanning (or Scan encrypted connections / SSL/TLS scanning).
- Toggle this feature Off or uncheck the box.
- Save changes and restart your computer. (Your web browsing remains 100% protected by native HTTPS encryption and Google Safe Browsing).
Method 3: Clear the Windows SSL State
Flushing the operating system’s cryptographic cache removes stale SSL session tokens and corrupt certificates.
- Press Win + R, type
inetcpl.cpl, and press Enter to launch Internet Properties. - In the Internet Properties window, click on the Content tab at the top.
- Under the Certificates section, click the Clear SSL state button.
- Windows will display a prompt: “The SSL certificate cache was successfully cleared.”
- Click OK, then click OK to close Internet Properties.
- Relaunch Chrome.
Method 4: Update Windows Trusted Root Certificates
Installing recent Windows quality updates ensures your PC recognizes newly minted international certificate authorities.
- Open Windows Settings (Win + I).
- Click on Windows Update in the left pane.
- Click Check for updates and allow Windows to download and install all pending Cumulative and Security updates.
- Alternatively, force a root certificate update via Command Prompt: open Command Prompt as Administrator and run:
certutil -generateSSTFromWU roots.sst
certutil -addstore -f root roots.sst - Restart your PC to commit the updated root certificate authority catalogue.
Method 5: Reset Google Chrome Settings to Default
Purging broken browser security flags and conflicting proxy configurations restores clean Chromium defaults.
- In Chrome, click the three vertical dots at the top right and select Settings.
- Click on Reset settings in the left navigation sidebar.
- Click on Restore settings to their original defaults.
- In the confirmation dialogue, click the blue Reset settings button.
- This resets search engines, disables extensions, and clears temporary site data without deleting saved bookmarks or passwords.
Chrome ‘Not Secure’ Warning Diagnostic Matrix
| Observed Error Message | Primary Root Cause | Recommended Solution |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID across all sites | System clock, date, or year out of sync | Settings > Time & Language > Click ‘Sync now’ |
| NET::ERR_CERT_AUTHORITY_INVALID everywhere | Antivirus HTTPS proxy certificate failure | Disable HTTPS / SSL Scanning in antivirus settings |
| Red ‘Not Secure’ on HTTP intranet pages | Chrome standard behavior flagging unencrypted sites | Normal browser policy; access via HTTPS or domain SSL |
| Intermittent certificate handshake timeouts | Corrupted Windows SSL state cache | Run inetcpl.cpl > Content tab > Click ‘Clear SSL state’ |
Synchronising system time, disabling conflicting third-party antivirus SSL proxies, and clearing the Windows SSL state permanently resolves universal ‘Not Secure’ warnings and restores trusted browsing in Google Chrome.