Why your site shows a “Not secure” warning, and how to fix it
“Not secure” usually labels an HTTP connection, while “Your connection is not private” indicates an HTTPS certificate or connection validation problem. The warning varies by browser, and the time to resolve it depends on the cause.
Four common causes
- The certificate has expired: SSL certificates are valid for a limited period. If automatic renewal is off or broken, the browser warns once the date passes.
- The certificate belongs to another domain: on shared hosting a site can be served with the host’s generic certificate. Because it does not cover your domain, the browser does not trust the connection.
- The certificate is self-signed: browsers warn about self-signed certificates unless the browser or device has been explicitly configured to trust them.
- The site only runs over HTTP: if HTTPS was never set up, browsers may mark pages, especially ones with forms, as “Not secure”.
How to check it yourself
- Type your site address starting with https:// and open it.
- Click the icon in the address bar and open the certificate details; check the validity dates and which domain it was issued for.
- Repeat with and without www; the two can behave differently.
- Open the http:// address and see whether it redirects to https:// automatically.
How to fix it
Most hosts offer free Let’s Encrypt certificates with automatic renewal. Make sure the certificate covers both your domain and its www version, that renewal is on, and that all HTTP requests redirect to HTTPS.
Check the certificate, domain and server configuration first. Consider moving hosts if the current service cannot support HTTPS; a certificate problem alone does not require rebuilding the site.
Why it matters
The warning is not only about security; it shapes the first impression. On a page with a booking, appointment or quote form, a warning can stop visitors from filling it in.