In short
HTTPS encrypts the connection between a visitor's browser and your website, so nobody in between can read or change what is sent. It does not prove a business is honest or that the site is free of malware. Free Let's Encrypt certificates are fine for most sites, as long as renewal is automatic and monitored.
Most business owners know their website needs “the padlock”. Fewer know what it actually does, what it does not do, or why a site that worked fine yesterday suddenly shows a full-page security warning today.
This guide explains HTTPS and SSL certificates in plain terms, with the practical details that matter when you run a site: free certificates, renewals, mixed content warnings, HSTS and how browsers now treat sites without HTTPS.
What does HTTPS actually do?
HTTPS encrypts the connection between a visitor’s browser and your website. Anyone sitting in between, on a café Wi-Fi network or along the route the data travels, cannot read or quietly change what is being sent.
It provides three things:
- Privacy: form entries, passwords and page contents are encrypted in transit.
- Integrity: nobody in the middle can inject adverts, malware or altered content into your pages.
- Identity of the domain: the browser checks that the certificate was issued for the domain being visited, so the visitor is talking to the real server for that address.
The certificate is the file that makes this possible. It is issued by a certificate authority after checking that you control the domain, and your server presents it to every visitor.
What does HTTPS not do?
This is where most misunderstandings come from. HTTPS protects the connection, not the website or the business behind it.
| HTTPS does | HTTPS does not |
|---|---|
| Encrypt data between browser and server | Stop your site being hacked |
| Prevent tampering in transit | Remove malware already on the site |
| Confirm the certificate matches the domain | Prove the business is legitimate or honest |
| Protect logins and form entries on the way | Protect data once it is stored on your server |
Phishing sites use HTTPS too, because certificates are free and quick to get. So the padlock tells a visitor “this connection is private”, not “this site is safe”. Securing the site itself is a separate job: updates, strong logins, backups and monitoring. Our WordPress security checklist covers that side.
Are free certificates good enough?
For most business websites, yes. Let’s Encrypt is a nonprofit certificate authority that issues certificates free of charge. It issues domain-validated certificates only, which confirm you control the domain. It does not offer organisation or extended validation certificates, because those checks cannot be automated.
The encryption is the same as a paid domain-validated certificate. Paid certificates can make sense when:
- A contract, insurer or partner specifically requires an organisation-validated certificate
- You need a certificate type or support arrangement your host does not provide
- Internal policy requires a particular certificate authority
Most managed hosts, and Cloudflare, issue and renew certificates automatically, so you may never see the certificate at all.
Tip: If you use Cloudflare, there are two connections to secure: visitor to Cloudflare, and Cloudflare to your server. Both should use valid certificates, with SSL mode set to Full (strict), so traffic is encrypted all the way.
How do certificate renewals work, and why do they fail?
Certificates expire on purpose. Short lifetimes limit the damage if a certificate’s private key is ever stolen. Let’s Encrypt certificates currently last 90 days by default, and the FAQ recommends renewing every 60 days.
Lifetimes are getting shorter across the whole industry. Let’s Encrypt has announced it will move to 64-day certificates in February 2027 and 45-day certificates in February 2028, following changes to the rules all certificate authorities work under. It warns that manual renewal is not recommended. In practice, renewal has to be automatic.
Renewals usually fail for boring reasons:
- DNS was moved and the validation check can no longer reach the server
- A firewall or security plugin blocks the validation request
- A domain or subdomain was added to the site but not to the certificate
- The host’s renewal job stopped and nobody was watching
An expired certificate produces a full-page browser warning that most visitors will not click past. Uptime monitoring that also checks certificate expiry dates catches this days before visitors do.
What is mixed content?
Mixed content happens when a page loads over HTTPS but some of its images, scripts or stylesheets are still requested over plain http://. It is common on older WordPress sites that moved to HTTPS without updating links stored in the database.
According to MDN’s guide to mixed content, modern browsers try to upgrade images, audio and video to HTTPS automatically, but block scripts, stylesheets, iframes and web fonts loaded over HTTP. The result can be a page that looks broken, a form that stops working or a missing font, with no obvious error for the visitor.
The fix is to replace http:// with https:// in content, settings, theme files and any hard-coded links, using a proper search and replace tool that handles WordPress data safely.
What is HSTS and should you turn it on?
HSTS (HTTP Strict Transport Security) is an instruction your site sends to browsers: “only ever connect to me over HTTPS”. After a browser has seen it once, it will refuse to load the site over plain HTTP for the time you specify, even if someone types http:// or clicks an old link.
MDN’s HSTS reference explains the options:
- max-age: how long browsers remember the rule, in seconds. A year is common.
- includeSubDomains: applies the rule to every subdomain as well.
- preload: asks for your domain to be built into browsers’ HTTPS-only lists.
Watch out: HSTS is hard to undo. If you enable includeSubDomains or preload while some subdomain (an old intranet, a mail web interface, a staging site) still lacks a valid certificate, that subdomain becomes unreachable in browsers that have seen the rule. Start with a short max-age, check everything works, then increase it.
What does the padlock mean in Chrome now?
Browsers have shifted from rewarding HTTPS to expecting it. Chrome now treats plain HTTP as the exception that needs a warning.
Google announced that Chrome would turn on “Always Use Secure Connections” by default for everyone with Chrome 154 in October 2026, after enabling it in April 2026 for people using Enhanced Safe Browsing. With it on, Chrome asks for permission before loading a public site that does not support HTTPS, and explains that attackers could see or change information on that connection.
For a business, the takeaway is simple: every page, subdomain and old campaign URL should work over HTTPS and redirect from HTTP. A forgotten subdomain on an old landing page tool is exactly where visitors will now meet a warning.
If you would rather not track certificates and renewals yourself, this is routine work that good managed hosting and a care plan with uptime monitoring should take off your plate.
The short version
- HTTPS keeps the connection private and untampered; it does not make the site or the business trustworthy.
- Free Let’s Encrypt certificates are fine for most sites, but renewal must be automatic and monitored.
- Certificate lifetimes are shrinking, to 45 days at Let’s Encrypt by 2028.
- Fix mixed content by updating every http:// link, and add HSTS carefully, starting with a short max-age.
- Chrome now warns before loading public HTTP sites, so check every subdomain and old URL.
Questions people ask
Is a free SSL certificate as secure as a paid one?
For encryption, yes. A free domain-validated certificate from Let's Encrypt uses the same encryption as a paid domain-validated certificate. Paid certificates can include organisation checks, warranties or support, but browsers no longer show visitors much difference.
Why does my site say 'Not secure' even though I have a certificate?
Usually the certificate has expired, does not cover the exact address being visited (for example the www version), or the site is still being reached over http:// without a redirect. Older pages loading images or scripts over http:// can also cause warnings.
Does HTTPS affect SEO?
Google has used HTTPS as a lightweight ranking signal for years, but the bigger effect is on trust: browsers warn visitors about sites without it. Moving from HTTP to HTTPS needs proper redirects so search engines follow the change.
What is the difference between SSL and TLS?
TLS is the modern protocol; SSL is its retired predecessor. People still say 'SSL certificate' out of habit, but every current certificate is used with TLS. The terms mean the same thing in everyday conversation.