If your site shows a padlock in the address bar, that is SSL/TLS doing its job. Certificates encrypt the traffic between a visitor and your server and prove your site is who it claims to be. Here is what they actually do and how to get one set up correctly.
What SSL/TLS Actually Does
SSL (and its modern successor TLS) does two things at once. It encrypts data in transit so that anyone intercepting the connection sees scrambled bytes instead of passwords or card numbers, and it authenticates the server so visitors can trust they are talking to the real site rather than an impostor. When people say "SSL certificate" today, they almost always mean a TLS certificate.
HTTP vs HTTPS
HTTP sends data in plain text. HTTPS is the same protocol wrapped in TLS, so the connection is encrypted end to end. Browsers now mark plain HTTP pages as "Not Secure," and search engines treat HTTPS as a ranking signal, so there is no longer a good reason to serve a public site over HTTP.
Types of Certificates
Domain Validation (DV) certificates only confirm you control the domain and issue in minutes, making them ideal for most sites. Organization Validation (OV) and Extended Validation (EV) certificates add checks on the legal entity behind the site and suit larger businesses. A wildcard certificate covers every subdomain of a domain, while a multi-domain (SAN) certificate covers several distinct names on one certificate.
How a Certificate Is Issued
A Certificate Authority (CA) signs your certificate after you prove control of the domain, usually by serving a token over HTTP or adding a DNS record. Your server then presents that signed certificate during the TLS handshake, and the browser checks the signature against its list of trusted CAs.
Free vs Paid Certificates
Free automated certificates from authorities like Let's Encrypt are perfect for most sites and renew automatically every few months. Paid certificates add longer validity options, organization validation, warranties, and support, which can matter for ecommerce and enterprise sites.
Common Pitfalls
Most certificate problems come down to expiry, mismatched names, or an incomplete chain. Let an expired certificate slip through and visitors get a full-page warning, so automate renewal wherever possible. Make sure the certificate covers the exact hostname being requested, and always install the intermediate chain so older clients can verify trust.
How Noded Can Help
Whether you are enabling HTTPS for the first time, moving to a wildcard certificate, or chasing down a chain or renewal issue, we can help you get TLS configured cleanly. Tell us what you are hosting and we will walk you through issuing, installing, and auto-renewing the right certificate.
FAQ
What is the difference between SSL and TLS?
They are the same idea at different ages. SSL is the original protocol, now deprecated, and TLS is its secure modern replacement. The term "SSL certificate" stuck around, but the encryption in use today is TLS.
Do I really need HTTPS for a small site?
Yes. Browsers flag plain HTTP as not secure, search engines favor HTTPS, and even a simple site can leak form data without it. Free automated certificates make it easy, so there is no real downside.
How often do certificates need renewing?
It depends on the issuer. Free automated certificates typically last around 90 days and renew on their own, while paid certificates often run a year. The key is to automate renewal so nothing expires unnoticed.
What is a wildcard certificate?
A wildcard certificate secures a domain and all of its direct subdomains with a single certificate, for example covering both shop and blog under one name. It simplifies management when you run many subdomains.