The scary red screen — "Your connection is not private", NET::ERR_CERT_DATE_INVALID, SEC_ERROR_EXPIRED_CERTIFICATE — always means one thing: your browser doesn't trust the website's SSL certificate. Here's how to tell whether the problem is on your side or the site's side.
Why browsers show this warning
Every HTTPS site presents a certificate that proves its identity. Browsers reject it when it's expired, issued for a different domain, signed by an untrusted authority, or when your device's clock makes a valid certificate look invalid.
First: check your device's clock
A wrong date or time is the most common local cause. If your laptop thinks it's 2024, every modern certificate looks "not yet valid" or "expired". Fix the clock, reload, done.
Second: is the certificate really broken?
Run the domain through our free SSL certificate checker. It shows the certificate's issue date, expiry date and issuer in seconds. If the certificate is expired or mismatched, the site is broken for everyone — nothing you can do except wait, and our down checker will show the same TLS problem.
Local fixes when the certificate is actually fine
- Correct your system date & time.
- Flush your DNS cache — here's how — a stale or hijacked DNS entry can send you to the wrong server with the wrong certificate.
- Temporarily disable HTTPS-scanning antivirus or corporate proxies.
- Try a different browser or device to isolate the problem.
- On public Wi-Fi, log in to the captive portal first — unauthenticated hotspots trigger this error.
Should you click "Proceed anyway"?
Only for sites you fully trust (e.g. your own router's admin page). On banking or shopping sites, never bypass the warning — an invalid certificate on a site that used to work can indicate DNS hijacking. When in doubt, check the site's live status first.