How to Fix This Site is Not Secure Error in Edge Browser

Encountering the dreaded "This Site is Not Secure" warning in Microsoft Edge? 😩 It blocks access to sites, sparks security fears, and ruins your browsing flow. Don't worry—this common issue stems from outdated certificates, cache glitches, or system mismatches. Our guide delivers quick, reliable fixes to get you back online safely. Follow these steps, and you'll banish the error for good! 🚀

"This Site is Not Secure" error screenshot in Microsoft Edge browser

Why Does the "This Site is Not Secure" Error Happen in Edge?

Edge flags sites as insecure due to:

  • ❌ Expired or invalid SSL certificates on the website.
  • ❌ Mixed content (HTTP resources on HTTPS pages).
  • ❌ Corrupted browser cache/cookies.
  • ❌ Wrong system date/time.
  • ❌ Interference from VPNs, proxies, or extensions.

Good news? Most fixes take under 5 minutes. Let's dive in! 👇

1️⃣ Method 1: Sync Your System Date and Time (Quickest Fix)

The #1 culprit? Time desync breaks certificate validation. Here's how to fix it:

  1. Open Settings (Windows key + I).
  2. Go to Time & Language > Date & Time.
  3. Toggle Set time automatically ON.
  4. Click Sync now.
  5. Restart Edge and refresh the page. ✅

Pro Tip: On laptops, disable "Automatically change time zone" if traveling. Works 80% of the time!

2️⃣ Method 2: Clear Edge Cache and Cookies

Stale data fools Edge into thinking sites are unsafe. Wipe it clean:

  1. Launch Edge, click the three dots > Settings.
  2. Navigate to Privacy, search, and services.
  3. Under Clear browsing data, click Choose what to clear.
  4. Select All time, check Cookies, Cached images/files.
  5. Hit Clear now. Reload the site! ✨
Step-by-step guide to clearing cache in Microsoft Edge for "This Site is Not Secure" fix

3️⃣ Method 3: Update Microsoft Edge to the Latest Version

Outdated Edge misses security patches. Update now:

  1. In Edge, three dots > Help and feedback > About Microsoft Edge.
  2. It auto-checks and installs updates.
  3. Restart browser. Boom—fixed! 🚀

Edge's 2026 builds include enhanced SSL/TLS 1.3 support for fewer errors.

4️⃣ Method 4: Disable Interfering Extensions and VPNs

Extensions like ad-blockers or VPNs can tamper with certificates.

🛡️ ActionSteps
Disable Extensionsedge://extensions/ > Toggle OFF suspects > Reload page.
Turn Off VPN/ProxySettings > Network > VPN > Disconnect. Or use Microsoft's proxy guide.

5️⃣ Method 5: Reset Edge Settings (Nuclear Option)

If nothing works, reset without losing data:

  1. Three dots > Settings > Reset settings > Restore settings to their default values.
  2. Confirm. Edge restarts fresh! 💥

Warning: Customizes may reset, but bookmarks/passwords stay safe.

Advanced Fixes for Stubborn Errors

Still stuck? Try these:

  • ⭐ Check Antivirus: Temporarily disable real-time scanning (e.g., Windows Defender).
  • ⭐ Site-Specific Bypass: Click the lock icon > Site settings > Allow insecure content (use cautiously!).
  • ⭐ Command-Line Reset: Run edge://settings/reset in address bar.

Prevention Tips: Stay Secure Forever

Lock down future errors:

  1. ✅ Enable auto-updates in Edge.
  2. ✅ Use only HTTPS sites (Edge blocks HTTP by default).
  3. ✅ Install latest Edge from Microsoft.
  4. ✅ Scan for malware with Windows Security.

By now, your Edge browser should be error-free. If issues persist, it's likely the website's fault—contact them! You've got this. 🎉 Share your success in comments below.

Ready for more? Bookmark this for quick reference and explore our guides on Chrome/Chrome errors next! 👀

Leave a Comment

Enable FIPS Mode on SLES 15 and Verify the Boot State

Enable FIPS Mode on SLES 15 and Verify the Boot State

Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.

Set Up a LUKS-Encrypted Data Volume on SLES

Set Up a LUKS-Encrypted Data Volume on SLES

Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.

Build a Custom AppArmor Profile on SUSE Linux

Build a Custom AppArmor Profile on SUSE Linux

Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.

Build a Local SUSE Update Server with RMT on SLES 15

Build a Local SUSE Update Server with RMT on SLES 15

Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.

Join SLES 15 to Active Directory with SSSD in YaST

Join SLES 15 to Active Directory with SSSD in YaST

Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.

Enable SLES Live Patching and Verify a Kernel Fix

Enable SLES Live Patching and Verify a Kernel Fix

Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.

Apply the SLES 15 STIG Safely with OpenSCAP

Apply the SLES 15 STIG Safely with OpenSCAP

Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.

Restore Cockpit Access to SUSE Linux Enterprise Server

Restore Cockpit Access to SUSE Linux Enterprise Server

Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.