What Is a TLS Certificate? What the Padlock Really Proves
A TLS certificate ties a domain name to a public key so browsers can trust the connection. Here is what it proves, what it never proves, and the errors you will meet.
A TLS certificate is a digital file that ties your domain name to a public key, signed by a third party that browsers already trust. When someone visits your site over HTTPS, the browser uses the certificate to confirm it is talking to the real owner of that domain, then sets up an encrypted connection. No valid certificate, no padlock, and a full-page warning instead of your app.
People still say "SSL certificate". SSL is the old name for the protocol. TLS replaced it, and what is installed on servers today is TLS. The two phrases mean the same file in everyday talk.
What TLS gives you
The MDN guide to Transport Layer Security lists three protections:
Encryption. Attackers on the network cannot read the data.
Integrity. Attackers cannot change the data without detection.
Authentication. Each side can prove who it is. On the web, usually only the server proves itself to the client.
The certificate is the authentication part. Per MDN, it contains a digitally signed copy of the public key that matches your site's private key, and it binds that key to your domain name. That is how a browser knows that https://example.com is really example.com and not something in the middle.
The handshake in four moves
The browser connects and asks for a secure session.
The server sends its certificate.
The browser checks it. In general, that means the signature comes from a certificate authority it trusts, the dates are still valid, and the name matches the address typed in.
If it passes, both sides agree on a secret key and the traffic is encrypted. MDN notes that TLS 1.3 is the current version and the most widely used.
The private key never leaves your server. The certificate is public by design. Anyone can read it, which is exactly what lets a browser verify it.
Who issues certificates
A certificate authority (CA) is the organization that signs certificates. Browsers ship with a list of CAs they trust, and a certificate only works if it chains back to one of them. MDN names Let's Encrypt as a widely used nonprofit CA that issues free certificates, and adds that many hosting services handle certificates for you, either by default or through a setting.
For most AI-built apps the practical answer is simple. If you deploy on a managed platform, the certificate is already handled. If you run your own server, use an automated client and let it renew for you instead of copying files by hand.
What a certificate does not prove
This is the part that matters for safety. The padlock means the connection to that domain is encrypted and the domain is the one named. It does not mean:
the site is honest,
the company behind it is real,
the content is safe to trust.
A scam site gets a perfectly valid certificate for its own scam domain. When you teach someone to spot a phishing page, "it has the padlock" is not evidence of anything. Read the actual domain instead, and see what HTTPS is and is not for the longer version.
Common certificate errors and the mistake behind each
Certificate expired. Renewal was manual, or the automation silently broke. Set an alert well before the date.
Name mismatch. The certificate covers
example.combut the visitor usedwww.example.com, or a subdomain that was never included.Untrusted issuer or incomplete chain. The server sent its own certificate but not the intermediate one, so some browsers cannot connect it to a trusted root.
Mixed content. The page loads over HTTPS but pulls a script or image over plain HTTP, and the browser blocks or flags it.
Certificate fine, site down. A wrong DNS record or a proxy pointing at nothing looks like a TLS problem but is not. Check DNS and the reverse proxy before blaming the certificate.
Why this matters when AI writes your config
Coding assistants love the fast fix. When a certificate error blocks a local test, a common suggestion is to disable verification, for example by setting NODE_TLS_REJECT_UNAUTHORIZED=0 or passing a flag like -k to curl. That is fine for a thirty-second experiment on your own machine and dangerous the moment it reaches production, because it turns off the authentication half of TLS and lets anyone in the middle impersonate the server.
Put a line in your instructions file: never disable certificate verification, and if a certificate error appears, report it and fix the cause. Search the codebase for those flags before every release. The same discipline applies to exposed keys, where a quick shortcut becomes a standing hole.
Encryption on the wire also does not protect data sitting on a disk, which is a different problem covered in encryption in transit versus at rest.
FAQ
Is a TLS certificate the same as an SSL certificate?
In practice, yes. SSL is the older protocol name that people kept using. The certificates installed today are used with TLS.
How do I get a TLS certificate for free?
Use a free certificate authority such as Let's Encrypt, or deploy on a host that issues and renews certificates for you. Automate renewal so it never expires unnoticed.
Does the padlock mean a website is safe?
No. It means the connection is encrypted and the domain matches the certificate. Scam sites can have valid certificates for their own domains.
What does "your connection is not private" mean?
The browser could not verify the certificate. Typical causes are an expired certificate, a name mismatch, or a missing intermediate certificate.
Do I need a TLS certificate for a small site with no logins?
Yes. Browsers flag plain HTTP pages as not secure, and without TLS anyone on the network can read or alter what your visitors see.
How did this land?
About the author

Senior Editor, AI & Product
Cecilia leads the Swarmz editorial desk. She has spent a decade turning complex AI and product topics into writing people actually finish, and she owns the blog's quality bar.


