The padlock in your browser's address bar represents one of the most important pieces of web infrastructure: an encrypted, verified connection between your visitor and your site. This article explains what SSL/TLS actually does, why every site needs it, and how it is provided on your hosting.
What the certificate really does
An SSL/TLS certificate does two jobs at once:
- Encryption. It scrambles the data travelling between the browser and the server so that anyone in between — on public Wi-Fi, along the network path — sees only unreadable noise instead of passwords, form entries or card details.
- Identity. It proves the visitor is really connected to your domain and not an impostor sitting in the middle. That is the difference between
http://and the padlockedhttps://.
("SSL" is the historical name; modern connections actually use its successor, TLS, but the term SSL stuck and everyone still uses it.)
Why every site needs one — not just shops
It is tempting to think encryption only matters for checkout pages, but that is no longer true:
- Browsers mark plain
http://sites as "Not secure", which erodes trust instantly. - Search engines prefer secure sites, so HTTPS has an SEO benefit.
- Any form at all — a login, a contact form, a newsletter box — sends data you do not want exposed.
- Modern browser features and many APIs simply refuse to work over plain HTTP.
The types of certificate
Certificates differ mainly in how much identity they verify:
- Domain Validation (DV) confirms you control the domain. It is issued quickly and is perfect for the vast majority of sites. The free AutoSSL certificates included with your hosting are DV.
- Organization Validation (OV) additionally verifies your business details.
- Extended Validation (EV) involves the most thorough vetting of your organisation.
All of them provide the same strong encryption — the difference is the level of identity assurance, not how secure the padlock is.
What you get on Xponzy hosting
Your cPanel hosting includes free, automatically renewing AutoSSL certificates, so standard sites are covered at no extra cost and without manual renewals. If you need a paid certificate — for example an OV/EV certificate for a larger organisation, or one with a warranty — those are available too; see SSL Certificates. Ready to make sure your whole site uses it? Continue to Installing an SSL Certificate and Forcing HTTPS.