When browsing on macOS, iPhone, or iPad, encountering the alert “Safari cannot verify the identity of the website ‘[domain]’. The certificate for this website is invalid. You might be connecting to a website that is pretending to be ‘[domain]’, which could put your confidential information at risk” blocks page navigation. Apple devices enforce stringent certificate validation policies through the macOS Keychain and iOS trust stores. If a domain presents a certificate with an expired timestamp, mismatched common name (CN/SAN), untrusted intermediate Certificate Authority (CA), or self-signed signature, Safari halts the TLS handshake to protect the user against man-in-the-middle (MITM) attacks. This troubleshooting guide covers how to identify whether the alert indicates a local client misconfiguration or a genuine server certificate failure, and how to resolve it safely.
What Triggers the Safari Certificate Verification Warning?
Safari’s certificate validation mechanism triggers when any link in the cryptographic chain of trust fails validation:
- System Date and Time Discrepancy: If your Mac or iPhone clock is set ahead or behind actual UTC time, valid certificates appear expired or not yet valid.
- Expired SSL/TLS Certificate: The website administrator failed to renew the TLS certificate before its expiration date.
- Missing Intermediate Certificates: The web server failed to bundle intermediate CA certificates, preventing Safari from tracing the certificate back to a known root authority.
- Untrusted Root Certificate Authority: For enterprise intranets, local development servers, or network firewalls, the root CA has not been marked as trusted in the macOS Keychain Access utility.
- Public Wi-Fi Captive Portal Interception: Hotel, airport, or cafe Wi-Fi networks intercepting HTTPS traffic to present a login splash screen.
Method 1: Verify and Synchronise System Date and Time
Cryptographic certificates are valid only within a specific temporal window. Even slight clock inaccuracies trigger certificate rejections.
- On macOS:
- Click the Apple menu > System Settings.
- Navigate to General > Date & Time.
- Enable Set time and date automatically. Ensure the time server is set to
time.apple.com. - Confirm that your Time Zone matches your geographic location.
- On iOS (iPhone/iPad):
- Open Settings > General > Date & Time.
- Toggle on Set Automatically.
- Quit and restart Safari, then attempt to load the domain again.
Method 2: Inspect Certificate Details and Trust Settings in Keychain (macOS)
If accessing an internal enterprise tool or development domain, checking certificate details reveals the specific point of failure.
- On the warning page in Safari, click Show Certificate.
- Review the certificate summary:
- Check the Validity dates.
- Ensure the Issued to name matches the exact domain in your URL bar.
- If the certificate was issued by an internal corporate CA that you trust, launch Keychain Access (via Spotlight: Cmd + Space > Keychain Access).
- Select System or login keychain and locate the root/intermediate certificate.
- Double-click the certificate, expand the Trust section, and change When using this certificate to Always Trust.
- Close the window, authenticate with your administrator password, and refresh Safari.
Method 3: Clear Safari Website Data and SSL Cache
Stale OCSP (Online Certificate Status Protocol) responses or corrupted cache entries can cause Safari to reject updated certificates.
- In Safari, click Safari in the top menu bar > Settings (or Preferences).
- Select the Privacy tab and click Manage Website Data.
- Type the name of the problematic domain in the search box.
- Select the entry and click Remove.
- Next, enable the Develop menu: navigate to Settings > Advanced > tick Show features for web developers.
- From the top menu bar, click Develop > Empty Caches.
- Restart Safari.
Method 4: Resolve Captive Portal Interception on Public Wi-Fi
Public Wi-Fi networks intercept secure connections to force users onto authentication splash pages.
- Disconnect and reconnect to the Wi-Fi network.
- In Safari, attempt to navigate to an unencrypted HTTP URL (such as
http://captive.apple.com). - This forces the network gateway to display its terms-of-service splash page without raising an SSL mismatch warning.
- Accept the Wi-Fi terms or complete guest sign-in. Once Internet access is granted, secure HTTPS browsing will function normally.
Safari Certificate Warning Diagnostic Matrix
| Certificate Error Detail | Underlying Cause | Appropriate Remediation |
|---|---|---|
| “Certificate has expired” | Server cert expired or local clock incorrect | Verify system date/time; notify website administrator |
| “Hostname mismatch” | URL domain does not match CN or SAN entry in certificate | Verify correct spelling of domain (e.g. www vs apex) |
| “Certificate signed by untrusted authority” | Private/internal CA or self-signed cert | Import root CA into Keychain Access and set to Always Trust |
| Warning appears only on public hotspot | Captive network proxying HTTPS | Navigate to captive.apple.com to complete Wi-Fi login |
Frequently Asked Questions
Should I click “Continue” or “Visit Website” to bypass the warning?
You should only bypass the warning if you are accessing a known internal system, private network device (such as a home router admin portal), or local development server. Never bypass this warning when accessing public banking, shopping, or email services, as doing so exposes your session credentials to interceptors.
Why does the website work in Google Chrome but fail in Safari?
Chrome uses its own internal Chrome Root Store and may handle missing intermediate certificate downloads (via AIA fetching) more aggressively than Safari. Safari relies strictly on macOS/iOS native security frameworks and Apple Root Certificate validation policies, rejecting any incomplete certificate chain.