How to Fix ‘This Connection Is Not Private’ in Safari on Mac

Navigating to websites in Safari on macOS only to be stopped by the full-page security warning: ‘This Connection Is Not Private. Safari warns you when a website has an untrusted or invalid certificate’ prevents access to web resources. Safari strictly enforces Transport Layer Security (TLS) and Certificate Authority (CA) validation standards. While this alert legitimately warns against malicious phishing portals or man-in-the-middle attacks, it frequently appears as a false positive on legitimate websites due to system date and time desynchronisation, corrupted root certificates in macOS Keychain, or security software SSL inspection proxies.

What Causes ‘This Connection Is Not Private’ in Safari?

When Safari initiates an HTTPS connection, it validates the remote web server’s SSL certificate against trusted root certificates stored in macOS. Warnings are triggered by:

  • System Clock Time Skew: If your Mac’s internal clock is ahead or behind true atomic time, certificates that are currently valid appear expired or not yet valid.
  • Corrupted or Distrusted Keychain Certificates: Expired intermediate certificates or custom self-signed certificates marked as Never Trust in Keychain Access.
  • Antivirus and Firewall SSL Interception: Third-party security suites (such as Avast, Bitdefender, or Kaspersky) attempting to decrypt HTTPS traffic by installing custom local certificates that Safari rejects.
  • Public Wi-Fi Captive Portal Redirects: Hotel, airport, or cafe Wi-Fi networks intercepting DNS queries before you have completed browser login agreements.
  • Stale Safari Certificate Cache: Obsolete certificate cache files stored locally in macOS container caches.

Step 1: Check and Synchronise Mac Date and Time

A discrepancy of even a few minutes causes SSL certificate validity windows to fail mathematical verification.

  1. Click the Apple menu in the top left corner and open System Settings.
  2. Navigate to General > Date & Time.
  3. Ensure that Set time and date automatically is toggled On.
  4. Ensure that Set time zone automatically using your current location is toggled On.
  5. If the toggles were already on, toggle them Off, wait 10 seconds, and turn them back On to force synchronization with Apple’s time server (time.apple.com).
  6. Reload the webpage in Safari.

Step 2: Inspect and Remove Conflicting Certificates in Keychain Access

Expired intermediate certificates or broken root trust settings in the macOS Keychain cause persistent certificate rejections.

  1. Press Cmd + Space to open Spotlight, type Keychain Access, and press Enter.
  2. In Keychain Access, select System and System Roots from the sidebar.
  3. Select Certificates in the category filter.
  4. Look for certificates marked with a red X icon (indicating a distrusted certificate) or expired certificates belonging to the problematic domain.
  5. Double-click the suspicious certificate, expand the Trust section, and ensure that When using this certificate is set to Use System Defaults.
  6. If an obsolete intermediate certificate is corrupt, right-click and delete it.

Step 3: Resolve Public Wi-Fi Captive Portal Interception

Public Wi-Fi networks that require agreeing to terms of service intercept HTTPS traffic, triggering certificate warnings.

  1. In Safari, navigate to an unencrypted plain HTTP website (such as http://captive.apple.com or http://neverssl.com).
  2. This forces the network captive portal login page to appear without encryption errors.
  3. Accept the network terms and complete authentication.
  4. Return to your original website; secure HTTPS browsing will now proceed smoothly.

Step 4: Disable Third-Party Antivirus Web Shields

Antivirus web shields that perform deep packet inspection install local root certificates that frequently clash with modern Safari Apple security policies.

  1. Open your installed third-party security software (e.g. Avast, Norton, McAfee, Bitdefender).
  2. Navigate to Web Protection or Network Shield settings.
  3. Temporarily disable HTTPS Scanning, SSL Scanning, or Web Shield.
  4. Reload Safari. If the error disappears, add the target domain to the antivirus exclusion list or reinstall the antivirus certificate.

Step 5: Bypass Warning Safely (Advanced / Trusted Sites Only)

If you are accessing an internal development server or intranet device (such as a local router setup page) with a known self-signed certificate:

  1. On the Safari warning screen, click Show Details at the bottom.
  2. Review the specific certificate error details (e.g. self-signed root or hostname mismatch).
  3. If you completely trust the destination network, click visit this website at the bottom of the expanded text.
  4. Click Visit Website and confirm with your Mac administrator password or Touch ID to save a local certificate exception.

Synchronising system time, auditing certificates in Keychain Access, and bypassing captive portal intercepts eliminates ‘This connection is not private’ errors in Safari.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.