
Every time you see the padlock in your browser, a protocol called TLS is doing the work. It scrambles what passes between a visitor and your website so nobody in between can read it or change it. Like most technology, it has had several versions, and the older ones are no longer considered safe.
We recently switched off the two oldest versions, TLS 1.0 and 1.1, on our own website. It took a couple of minutes once we had checked nothing depended on them, and the site now scores A+ on the free Qualys SSL Labs test. Plenty of UK business websites still accept them, usually because nobody has ever been asked to look.
The padlock tells you a connection is encrypted. It does not tell you how old the encryption is.
What TLS is, without the jargon
When someone visits your website or sends you a contact form, their browser and your web server agree how to encrypt the conversation before anything else happens. TLS is the set of rules for that agreement. The version they settle on decides how strong the protection is.
Your server offers the versions it supports and the browser picks the best one both sides understand. That is the catch: if your server still offers the old versions, an attacker who can sit in the middle of a connection, on public Wi-Fi for example, can try to push the conversation down to the weakest one.
Why TLS 1.0 and 1.1 have to go
TLS 1.0 dates from 1999 and TLS 1.1 from 2006. Both rely on cryptography that has known weaknesses, and they were formally retired by the body that writes internet standards in March 2021. The major browsers had already stopped using them in 2020.
How TLS got here
- 11999TLS 1.0 published
- 22006TLS 1.1 published
- 32008TLS 1.2, still the safe minimum today
- 42018TLS 1.3, faster and stronger
- 52021TLS 1.0 and 1.1 formally retired
If modern browsers no longer use them, you might wonder why it matters that your server still accepts them. There are three practical reasons:
- It invites downgrade attempts. Leaving an old door open gives an attacker something to aim for.
- It shows up on external scans. Insurers, larger customers and their security teams run exactly this kind of check during supplier reviews, and old TLS is one of the first things it flags.
- Card payments. If your website handles card details, the card industry's PCI DSS rules have not allowed early TLS since June 2018.
Old TLS left on or switched off
Still accepts 1.0 and 1.1
- Weaker encryption on offer Attackers can try to force a downgrade
- Flagged by external scans Questions from insurers and customers
- Grade capped SSL Labs marks it down
TLS 1.2 and 1.3 only
- Only modern encryption Nothing weaker to fall back to
- Passes supplier checks One less thing to explain
- A+ achievable With HSTS and a valid certificate
Will switching it off break anything?
For your website visitors, almost certainly not. Every browser released in the last several years supports TLS 1.2. The things that do occasionally trip up are older pieces of kit and software that talk to your systems in the background:
Check these before you switch old TLS off
- Older printers and scannersEspecially scan to email
- Legacy business softwareAnything that connects to your website or server
- Very old Windows versionsWindows 7 and Server 2008 era machines
- Payment and booking pluginsAsk the supplier which versions they use
- Integrations and APIsAnything that posts to your site automatically
In most small businesses none of these apply, and where they do, the fix is usually an update rather than a reason to leave the old versions on.
How to switch it off
Where you make the change depends on how your website is hosted, but it is normally a single setting:
Turning off TLS 1.0 and 1.1 safely
- 1Check where you areRun the free Qualys SSL Labs test on your site
- 2List what connects to itPlugins, printers, integrations and old software
- 3Set the minimum to TLS 1.2In Cloudflare, your hosting panel or your web server
- 4Test againConfirm 1.0 and 1.1 are refused and the site still works
- 5Add it to your checksRe-test after any hosting or certificate change
If you use Cloudflare in front of your site, it is one setting: Minimum TLS Version under SSL/TLS, Edge Certificates. Microsoft Azure and most good hosting companies have an equivalent. If your website sits on your own server, the change is made on the server itself and is worth testing out of hours.
It is a small change, but it is the sort of detail that tends to get missed because it is technical and nobody owns it. That is what we are here for: looking after the details and explaining them in plain English. If you would rather someone kept an eye on these details for you, that is what our cyber security services are for, and it is the kind of thing that comes up when we help businesses through Cyber Essentials.
How we can help
If you would like to know how your own website and email stand up, there are three easy ways to start:
- Run a free domain scan. It checks your website certificate and HTTPS settings alongside your email security, and explains the results in plain English.
- Book a free IT Health Check. A wider look at your setup, from accounts and devices to backups, with an engineer on Teams or on your own.
at a time that suits you, and we will check your website's settings and switch off anything out of date for you.
Want this handled for you? See Cyber security services.
Based in Brighton or Hove? We are too: see IT support in Brighton.
Free, no sales call needed
Two free checks. Know where you stand.
Domain email check
Can someone send email pretending to be you? Is your real email landing in junk? Type your domain and find out in under a minute.
IT Health Check
A short set of questions that scores your security and business risk, and tells you what to fix first. 15 to 20 minutes on your own.


