SSL certificates explained: types, costs and renewal
An SSL certificate proves a site is yours and encrypts the connection. Most sites need only a free one that renews itself. Types, lifetimes and costs.
By Sohail Hussain18 November 20266 min read
An SSL certificate is a small file, issued by a certificate authority, that proves to a browser that it is talking to your domain and lets the two encrypt everything sent between them. Without one, browsers label your pages "Not secure", and as of October 2026 Chrome is moving to ask visitors before it loads public sites over plain HTTP. Most company websites need only a free domain-validated certificate from Let's Encrypt or their host, set to renew automatically. Paying for a certificate rarely buys anything a visitor can see.
The technology is now called TLS, not SSL, but "SSL certificate" is still the name everyone uses, including the companies that sell them. This guide uses it too.
What does a certificate actually do?
Two things.
It proves identity. Before issuing a certificate, the authority checks that the person asking controls the domain, usually by asking them to place a file on the website or a record in DNS. When a browser later connects, the certificate shows that this server is the one the authority checked.
It enables encryption. The certificate carries a public key that the browser uses to agree a secret with the server. After that, everything sent, including form entries and login details, is unreadable to anyone in between, such as a shared Wi-Fi network.
What it does not do: it says nothing about whether the business behind the site is honest. Phishing sites have valid certificates too. Chrome replaced the padlock icon in 2023 partly because visitors read it as "this site is safe", which it never meant.
On sites under our website care and maintenance, the certificate is one of the things we monitor rather than assume, because a failed renewal takes the whole site down for every visitor.
Which type of certificate do you need?
Certificates differ in how much the authority checks before issuing them, and in which addresses they cover.
| Type | What is checked | Typical cost as of October 2026 | Worth it for |
|---|---|---|---|
| Domain validated (DV) | Control of the domain only | Free from Let's Encrypt and most hosts and CDNs; paid versions from a few dollars a year | Almost every website |
| Organisation validated (OV) | Domain, plus that the company exists | Tens to a few hundred dollars a year | Contracts or procurement rules that demand it |
| Extended validation (EV) | Domain, company, and further legal and address checks | Higher than OV, often several hundred dollars a year | Very few sites |
| Wildcard | Covers every subdomain, such as *.example.com | Free through Let's Encrypt with a DNS check; paid versions cost more | Many subdomains that change often |
| Multi-domain | Several named domains in one certificate | Varies | Hosting several related domains together |
The OV and EV rows are the ones to question. Browsers stopped showing the company name for EV certificates in the address bar in 2019, so the extra checks are invisible to visitors. If a quote includes a paid certificate for a normal company site, ask what it does that a free one does not.
How long does a certificate last now?
Not long, and getting shorter. The CA/Browser Forum, the body of certificate authorities and browser makers that sets the rules, agreed a schedule in ballot SC-081 that cuts the maximum lifetime in steps:
| Certificates issued | Maximum lifetime |
|---|---|
| Before 15 March 2026 | 398 days |
| From 15 March 2026 | 200 days |
| From 15 March 2027 | 100 days |
| From 15 March 2029 | 47 days |
So as of October 2026, no publicly trusted certificate can be issued for more than 200 days. Let's Encrypt certificates have lasted 90 days since 2015, and Let's Encrypt plans to bring its default down to 45 days by February 2028.
The consequence is simple. Manual renewal is no longer realistic. A paid "one-year" certificate now means reissuing and installing it at least twice in the year, and by 2029 about eight times. Renewal has to be automated, and someone has to notice when the automation fails.
How does automatic renewal work, and how does it fail?
Most hosts, CDNs and platforms renew certificates for you using a standard protocol called ACME. Vercel, Netlify, Cloudflare, Shopify, Wix and most managed WordPress hosts handle it without any setup. On your own server, a client such as Certbot does the same job on a schedule.
Automation fails in a handful of predictable ways:
- DNS moved and the check broke. The authority checks domain control on each renewal. If the domain now points somewhere the renewal client cannot answer from, renewal fails.
- A firewall or redirect blocks the check. Security rules sometimes block the path the authority requests during validation.
- A CAA record names the wrong authority. A CAA record in DNS lists which authorities may issue for your domain. If your host switches to a different authority, a stale CAA record blocks it.
- The new certificate was issued but not loaded. The server keeps serving the old one until it restarts.
- Nobody is told. Let's Encrypt stopped sending expiry reminder emails in June 2025. If your setup relied on those, it now relies on luck.
The fix for the last one is an expiry check on an uptime monitor, set to warn two weeks ahead. Uptime monitoring shows how to add one in a few minutes.
What else does HTTPS need to be set up correctly?
A valid certificate is the start. A correct setup also has:
- Every address covered. The certificate must cover both
example.comandwww.example.com, and any subdomain in use. A missing name shows visitors a full-page warning. - One redirect to HTTPS.
http://should go tohttps://in a single 301 redirect, ideally combined with thewwwchoice so there is no chain. 301 vs 302 redirects explains why the code matters. - No mixed content. Pages loaded over HTTPS should load every image, script and font over HTTPS too, or browsers block them or downgrade the page.
- HSTS, with care. The HSTS header tells browsers to use HTTPS only for your domain. It is good practice, but a long HSTS setting on a domain with an HTTP-only subdomain locks visitors out of that subdomain, so add it once every subdomain has a certificate.
Google's announcement of HTTPS by default in Chrome explains the browser side of this: sites still on plain HTTP will increasingly meet a warning before the visitor sees the page.
What does SSL cost you in practice?
For most sites, nothing beyond the hosting you already pay for. The mainstream hosts, CDNs and site builders include free certificates as of October 2026. The hosting cost calculator estimates the hosting figure, and a standard certificate should not add anything to it. If a host charges extra for a basic certificate, that is a reason to look at other hosts.
The real cost is attention: making sure renewal is automated, monitored and covers every address. That is a few minutes a year when it works and a lost day of enquiries when it does not. It belongs in the routine described in the website maintenance guide, next to the domain renewal it so often fails alongside.
Was this guide useful?