Problem × Security
Website shows "Not secure" in the browser
the browser is telling your visitors something
Why it happens
Certificate expired or mis-provisioned. TLS certificates last 90 days (Let’s Encrypt) to a year; auto-renewal breaks silently (DNS moved, hosting changed, CAA records). Expired = the whole site flagged.
Mixed content. The page is https but some asset (an image, a script, a font, an iframe) is hard-coded as http. Browsers downgrade the whole page’s badge for that. The usual source: old content pasted from a pre-SSL era, or a plugin/widget written before SSL was standard.
Subdomains outside the certificate. A certificate covering example.com and www but not shop.example.com or cdn.example.com: only those pages warn.
Triage
Open the failing page in Chrome, DevTools > Console: mixed content is listed line by line with the exact http URLs, or Security tab names the certificate problem explicitly. Expired/mismatched: check who issued the current cert (the padlock details) and whether renewal is supposed to be automatic (most hosts: yes, and it broke). Fix order: renew/reissue the certificate at the host, then hunt mixed content (the console list is your worklist; most fixes are URL rewrites in content or plugin settings).
When to bring us in
SSL breakage on a live site costs trust by the hour: renewals, reissues and mixed-content sweeps are same-day emergency work for us, and the permanent version - certificates that renew themselves, a site with zero http references - is a standard item in every care plan. The “Not secure” badge next to your brand is not a state of mind; it is a to-do list, and it is short.
Keep exploring