This is a certificate error on a site that has told browsers to use HTTPS only (HSTS). Because of that promise, the browser offers no way to click through: the only fix is to repair the certificate problem underneath, and only the site can do that.
Your connection is not private You cannot visit example.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
How one other client words the same error
Firefox
Did Not Connect: Potential Security Issue example.com has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.
| Error | You cannot visit … because the website uses HSTS |
| Usually fixed by | The website |
| Shown by | Chrome, Edge, Firefox |
| Can visitors click through? | No — by design |
| Rule behind it | RFC 6797: on a certificate error, no user recourse |
Check the certificate a site serves
Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.
What it means
A site that sends the Strict-Transport-Security header — or is on the browsers’ HSTS preload list — has asked browsers to refuse any connection whose certificate cannot be verified, without offering to proceed. The HSTS standard requires exactly that, so an attacker cannot talk a visitor past a forged certificate.
So this page is always a second message: something is wrong with the certificate — expired, wrong name, missing intermediate — and HSTS removes the “proceed anyway” link. The underlying error code, shown under the message or in the details, names the real problem.
Why it happens
- Any certificate error on a site that uses HSTS: expired, issued for another name, untrusted or with a missing intermediate.
- A Wi-Fi sign-in page intercepting the connection.
- Antivirus or a company network inspecting HTTPS with its own certificate.
- A device clock set far wrong.
How to fix it
- Run the check above and fix what it finds — renew the certificate, cover the right names, serve the full chain.
- Do not try to switch HSTS off to get round it: browsers only accept a new HSTS header over a working HTTPS connection, so removing it needs a valid certificate anyway — and a preloaded domain takes months to come off the list.
If you are visiting the site
- Wait and retry if you are on public Wi-Fi: open any plain http:// page to bring up the sign-in screen.
- Check the device’s date and time.
- If the error appears on every HTTPS site, antivirus or a company proxy is the likely cause.
Questions
Can I remove HSTS from my browser to get in?
Chrome lets you delete a site’s HSTS policy at chrome://net-internals/#hsts, for your browser only, and not for preloaded domains such as .app and .dev. It does not fix the certificate, and it removes a protection — only do it for a site you control.
Why is there no “Proceed” link?
Because the site asked for HTTPS only, and the HSTS standard says browsers must then refuse a connection with a certificate error without offering to continue.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 6797 — rfc-editor.org
- What does “Your connection is not secure” mean? — support.mozilla.org
- Strict-Transport-Security header — developer.mozilla.org
- Security interstitials strings.grdp — raw.githubusercontent.com