Expired SSL / "not secure" warning
The "Not secure" warning goes away and the little lock comes back.
Flat price
$99
One job, one price. No hourly billing.
What is actually going on
Every website needs a small security certificate so browsers know the connection is safe. They expire, usually once a year, and they are supposed to renew on their own. When that renewal quietly fails, Chrome stops showing the padlock and starts showing the words "Not secure" right next to your name in the address bar. On some setups it goes further and shows a full red warning page that the visitor has to click through.
Nothing about your business changed. Nobody was hacked. A certificate lapsed. But the customer cannot tell the difference between an expired certificate and a genuinely dangerous site, and neither can their browser.
What this costs you
A red warning screen is the fastest way to lose a customer on the internet. Most people will not click past it, and the ones who do arrive already wondering whether you are legitimate. It makes an honest business with twenty years of good work look like a scam.
How to tell if this is you
- Chrome says "Not secure" next to your web address.
- Visitors see a red warning page before they can reach your site.
- The padlock icon is missing or has a line through it.
- Your site works at one address but not the other, with or without the www.
What we do
- Install a fresh, valid certificate for your site.
- Point every version of your address — with www, without, http and https — at the secure one.
- Track down the mixed-content items, usually old images, that keep the padlock off even after the certificate is good.
- Set the certificate to renew automatically so this does not come back next year.
- Confirm the warning is gone in Chrome, Safari, and on mobile.
This is usually a one-day job and the cheapest thing on this list. If your site is showing a warning right now, it is the first thing to fix.
Not sure if this is your problem?
Check your site first. The free report tells you exactly what is wrong in about 60 seconds.