What is SSL, and why does the padlock matter?
Find out what an SSL certificate does, why browsers warn visitors about sites without one, and what it means for your forms and payments.
SSL is the technology that scrambles information travelling between a visitor's browser and your website so nobody in between can read it. When it is working, your address starts with https and the browser shows a padlock or a similar "secure" indicator. When it is missing, the browser tells your visitor the site is "Not secure", which is about as welcoming as a "Beware of the dog" sign on a cafe door.
Strictly speaking, the modern version is called TLS. Almost everyone still says SSL, including the people who sell it, so we will too.
What it actually does
An SSL certificate does two jobs.
It encrypts the connection. Without it, anything typed into your site travels across the internet as readable text. On a shared wifi network at an airport or a shopping centre, that is a bit like sending a postcard. With SSL, the same information goes in a sealed envelope that only your website can open.
It confirms the site is the real one. The certificate is issued for your specific domain. When a browser connects, it checks that the certificate matches the address. This makes it much harder for someone to sit in the middle and pretend to be you.
That is all. It protects information in transit between the visitor and the site.
What it does not do
The padlock gets more credit than it deserves, so it helps to be clear about the limits.
- It does not mean the business behind the site is honest. Scam sites have padlocks too.
- It does not stop your site being hacked. A weak password is still a weak password.
- It does not protect information once it arrives. If a form emails a customer's details to an inbox with a poor password, SSL has done its bit and the weak link is elsewhere.
Think of it as an armoured van. It gets the cash from the shop to the bank safely. It has no opinion on whether the shop is reputable or whether the bank's vault is locked.
Why the browser warning matters so much
Browsers used to stay quiet about sites without SSL. Now they label them, and on some pages they put a full screen warning in front of the visitor before letting them continue.
Picture a new customer looking for a dog groomer. They tap your link and see "Not secure" beside your address. They do not know what SSL is. They just know their phone is telling them something is wrong, and there are four other groomers in the search results.
There are other knock on effects. Search engines prefer secure sites. Some browser features will not work on insecure pages. And if your form is on an insecure page, the browser may warn people again at the moment they start typing, which is the worst possible time.
Forms and payments
Any page where someone types something should be secure. That includes the obvious ones (credit cards, logins) and the ones people forget: contact forms, booking requests, quote forms, newsletter signups. A name, a phone number and a description of someone's sore back is personal information, and it deserves the sealed envelope.
For payments, most small businesses use a provider such as Stripe, PayPal or Shopify's checkout. In those setups the card details are entered on the payment provider's secure system and never touch your own server, which is exactly how you want it. Your site still needs its own certificate, because customers reach the payment step through your pages and need to trust the whole path.
If you ever find yourself being asked to collect card numbers through an ordinary web form or by email, stop. That is not something a small business site should be doing.
Certificates expire
An SSL certificate is valid for a limited time and must be renewed. These days most hosts issue certificates at no extra cost and renew them automatically, so you never think about it.
Until the automatic renewal fails. This is a classic cause of a site that worked fine yesterday and today shows a frightening red warning page. The usual culprits are a change to the domain's settings that broke the renewal check, or a move between hosts where nobody set up the certificate at the new end.
The other common glitch is "mixed content". The page itself is secure, but an old image or script is still being loaded from an insecure address, so the browser drops the padlock. It is a quick fix for whoever looks after the site.
How to check your own site
This takes two minutes.
- Type your address into a browser starting with https and look for the padlock or secure indicator. Tap it. It should say the connection is secure.
- Now type the address starting with http, without the s. You should be sent to the https version automatically. If the insecure version loads and stays, a redirect is missing.
- Try the address with and without www. Both should end up at the same secure page.
- Visit your contact page and any booking or payment page and check the padlock is still there.
- Ask your host two questions: is the certificate renewed automatically, and will someone be alerted if the renewal fails?
If all five check out, you can stop thinking about SSL. If any of them fail, pass this list to whoever manages your site. None of it is hard to fix, and all of it is worth fixing today.