A customer emails to say your website shows a "Not secure" warning, or your web person mentions that your certificate expires next week. You know HTTPS matters, but not what it actually does, what can go wrong, or what you should check. This guide explains it without the jargon.
When someone visits your site, their browser and your server exchange data across many networks: the cafe Wi-Fi, their internet provider and several companies in between. Over plain HTTP, that data travels as readable text. Anyone positioned along the way could read it or quietly change it.
HTTPS wraps that conversation in encryption. It gives your visitors three things:
SSL is the original name of the technology. The modern version is called TLS, but most people, and most hosting dashboards, still say SSL. For practical purposes they mean the same thing.
To prove it is the real server for your domain, your site presents a certificate. Think of it as an ID card issued by a certificate authority, an organization that browsers are built to trust. Before issuing one, the authority checks that whoever asked for it controls the domain.
There are three common levels:
The encryption is equally strong at every level. The difference is only how much identity checking happened before the certificate was issued.
The padlock, or a similar icon, beside the address means the connection is encrypted. It does not mean the business behind the site is honest. Scammers can get domain-validated certificates for look-alike domains just as easily as you can. It is worth telling your staff this, because "it has the padlock" is not a safety check for a link in a suspicious email.
On the other side, browsers such as Chrome label plain HTTP pages "Not secure." That warning makes visitors hesitate, especially on pages with contact forms or a checkout. Google has also said it uses HTTPS as a ranking signal, though a light one. The bigger cost of skipping it is lost trust.
Every certificate has an expiry date, and lifetimes keep getting shorter across the industry. Some last only a few months. When one lapses, visitors see a full-page warning that most of them won't click past. The answer is automatic renewal, which most modern hosts and platforms handle for you. If yours is renewed by hand, put the date in two people's calendars.
If an HTTPS page loads an image, script or font over plain HTTP, browsers may block that piece or show a weaker security indicator. This often happens after a site move, when old links in your pages still start with http. Updating those links to https usually solves it.
A certificate lists the exact names it protects. If it covers yourshop.com but not www.yourshop.com, or a subdomain like book.yourshop.com, visitors to the missing name get an error. Check every address you share publicly.
Your site should send anyone who arrives on the http version to the https version automatically. Otherwise old links and bookmarks still land on the unencrypted page.
If all five pass, HTTPS is doing its job, and you can leave it alone until you change domains, add a subdomain or switch providers. At that point, run the same five checks again.