igors@portfolio

The "connection is not private" warning: the customer leaves

Share

A customer clicks your link in Google, and instead of your site a grey page with an exclamation mark fills the screen: "Your connection is not private". They don't read the small print underneath. They close the tab, and the order that could have been yours never happens.

It's red-and-white tape across the door of a shop. Nobody goes up to ask what it means: repairs, an inspection, or someone forgot to take it down. They walk past.

The owner doesn't see this. He opens the site once a month, from his work computer, through a bookmark, and long ago clicked "proceed anyway". Meanwhile the certificate, the file that keeps "Not secure" away from your address, runs on its own calendar and one day stops being valid. The customer doesn't complain about the certificate. They have never heard the word.

One site in ten greets customers with a warning

A certificate proves to the browser that the site is who it says it is. If something is wrong with it, Chrome puts a full-screen warning in front of the site. If there is no https at all, it is gentler: since 2018 (Chrome 68) the address bar says "Not secure". There is no block, but the customer sees it.

In my check, the four causes together gave 2,721 sites out of 27,591 (9.9%).

What these mean. A certificate has a date after which the browser rejects it. A self-signed one was issued by the site itself, not by an outside authority, so nobody trusts it. "Issued for a different address" means it was made out for another address than the one the visitor arrived at: for example the version without www, while the customer came in with www. "No https" means the connection is not encrypted at all.

A lot depends on the platform. On Wix and Shopify the share is close to zero (0.7%), while on Joomla and on sites where no platform was detected it is around 14%. More in the article on platforms and their problems.

A certificate expires on its own calendar

The free Let's Encrypt certificates used by most sites in my check last 90 days, and a program on the server is supposed to renew them by itself, roughly every 60 days. While it works, nobody thinks about the certificate. When it breaks, Let's Encrypt itself will no longer warn you: it stopped sending expiry e-mails on 4 June 2025. A reminder, if there is one at all, comes from your host, and if nobody reads it, the tape stays across the door and nobody calls to tell you.

Usually the host handles this for you. But "everything is automatic" is exactly where a failure goes unnoticed.

What to do

  1. Open your site four ways. In a private window, type the address with https:// in front, then with http://, each with www and without. All four should land on the same page, with the icon left of the address and no "Not secure" next to it (in Chrome it is the site-settings icon; Safari and Firefox still show a padlock). A full-screen warning or "Not secure" on even one of them means some customers see the tape.
  2. See when the certificate runs out. In Chrome, click the icon to the left of the address: a summary of the connection opens. The path "Connection is secure → Certificate is valid" leads to the certificate, which shows a "valid until" date. Put it in your calendar two weeks before. One minute.
  3. If the site runs on WordPress, check two addresses. Settings → General: the "WordPress Address (URL)" and "Site Address (URL)" fields should start with https://. If they say http://, don't change them yourself: without a working certificate you will lock yourself out of the admin. That is a question for the host in the next step. To see whether WordPress detects the secure connection, go to Tools → Site Health → Info and look at the line "Is this site using HTTPS?".
  4. Send your host one line. "Is a Let's Encrypt certificate with automatic renewal enabled for the domain and for the www version?" If the answer is no, ask them to switch it on. For a specialist, renewing or replacing a certificate usually fits into an hour. Why you don't have to pay for a certificate is explained here.
  5. Find out whether anyone will warn you if renewal fails. Let's Encrypt no longer sends e-mails, so ask the host whether they send a reminder about certificate errors and to which address, and put a shared company inbox there. It is the only way to hear about the problem before a customer does.

A broader check of the site is in check your website in a minute.

What it buys you

Everyone who clicks your link lands on a site, not on a grey screen. On a site where everything is fine, a customer doesn't notice the icon left of the address. All they notice is the tape. I estimate taking it down at an hour of your host's work and two minutes of yours for the email, and after that the door of the shop is just a door again.

How I counted

September 2026, 27,591 Latvian company websites that responded, one check with no repeats. A certificate's state was recorded on the date of the check. If it was renewed the next day, it still counts as expired, so the "expired" figure may be too high. More: how I checked 27,591 websites.

Sources

If you would like me to open your site all four ways and tell you which one shows the tape, get in touch.

Share
← All articles