How an SSL certificate works, explained in plain terms
In short: an SSL certificate encrypts the connection between a visitor's browser and your server, so no one in between can eavesdrop on or alter the data being sent. The padlock confirms encryption, but it is not a promise that the site itself is honest.
Everyone knows you "need the padlock", but few people know what it actually does. Below we explain it without jargon, so you understand what the certificate is responsible for, and what not to expect from it.
What SSL actually does
When you type data into a site without SSL, it travels across the network in plain text. Every point along the way, from public wi-fi to your internet provider, can in theory read it. An SSL certificate encrypts that traffic. Data leaves the browser encrypted and is only decrypted by your server. That protects passwords, form data and card numbers.
The handshake
Before the connection starts, the browser and server exchange keys. The server presents its certificate, the browser checks that a trusted authority issued it and that it matches the domain, and then both sides agree on a key to encrypt this particular session. The whole dance takes a fraction of a second and ends with the padlock. If something is off, for example the certificate has expired, the browser stops and shows a warning.
What the padlock does not guarantee
This is the most common misunderstanding. The padlock says "the connection is encrypted", not "this site can be trusted". A DV certificate can also belong to a phishing site, because it only confirms control of the domain. So the padlock is necessary, but a site's safety also depends on up to date software, no malicious code and good passwords. How to check that, we show in the post on how to tell a site has a virus.
SSL or TLS, DV or EV
In practice SSL and TLS are the same thing, TLS is just the newer name for the technology. Certificates differ by validation level: DV confirms the domain and is free, OV and EV additionally verify the company. For a typical business site and most shops, DV is perfectly enough, for example a free Let's Encrypt certificate.
Why Google requires it
For years browsers have marked sites without SSL as "not secure", and Google treats https as a quality signal. No certificate is now a real minus in the eyes of both customers and the search engine. On top of that comes HSTS, a header that tells the browser to always connect over https, which we cover in security headers.
How to check your certificate
You do not need to know cryptography to see whether yours is fine. Our SSL and domain check shows whether the certificate is valid, until when, and whether renewal is near. If something is wrong, we can help fix it.