Dashboard

What Is HTTPS? What the Padlock Does and Does Not Prove

The padlock means a connection is encrypted and tied to a domain. It does not mean the site is honest or your data is safe. Here is what HTTPS covers and what it leaves out.

Cecilia Iona
Cecilia Iona
Senior Editor, AI & Product
21 October 20261 min read

HTTPS is the secure version of HTTP, the protocol browsers use to load web pages. MDN describes it as "an encrypted version of the HTTP protocol" that "uses TLS to encrypt all communication between a client and a server." In practice that means the padlock in your browser shows that what travels between your device and the site cannot be read or changed along the way. It does not show that the site itself is trustworthy, and that gap is where most confusion comes from.

What HTTPS actually does

Without HTTPS, anything you send, such as a login form or a payment page, crosses the network as readable text. Anyone sitting on the path, like a shared Wi-Fi network, could read it. With HTTPS, the browser and the site first agree on keys, then scramble everything that follows. The system that does this is TLS. You may also hear "SSL", which is the older name for the same idea and is still used in everyday speech.

The site proves which domain it belongs to by presenting a certificate. Certificates are issued by a certificate authority after it checks that the requester controls the domain. Let's Encrypt, a free authority, describes the process: the client completes a challenge, such as placing a record in DNS or a file on the site, and the authority then issues a certificate for that domain.

What the padlock proves

  1. The connection is encrypted. Outsiders on the network cannot read it.

  2. You reached the holder of a certificate for this domain. The certificate was issued to whoever controlled that name.

  3. The data was not altered in transit. TLS is built to detect changes made along the way.

What the padlock does not prove

  1. That the site is honest. Anyone can get a certificate for a domain they control, including a lookalike address built to fool you. A phishing page can have a padlock. The attack described in what a ClickFix attack is works on pages like that.

  2. That the app is well built. HTTPS protects the road, not the building. A site can use HTTPS and still expose private records through a coding mistake.

  3. That your data is safe once it arrives. The server decodes the traffic. What happens next depends on how the data is stored, which encryption in transit versus at rest covers.

Three checks for a site an AI tool built

Hosting services usually switch HTTPS on for you, so the work is checking that nothing leaks around it.

1. Does the plain address redirect?

Type http:// followed by your domain. A well-set-up site sends you on to the https:// version. If it loads over plain HTTP, visitors who type the address by hand are exposed.

2. Is anything loaded insecurely?

A page served over HTTPS can still pull in an image or script from an http:// address. Browsers call this mixed content, and they may block it or show a warning. Open your browser's developer console on each main page and look for mixed content messages. AI-generated code that copies old example snippets is a common source.

3. Will the certificate renew?

Certificates expire. Let's Encrypt describes renewal as repeating the same validation and issuance steps, so something has to run that process. Managed hosting does it for you. If you run your own server, confirm the renewal job exists and ask who gets the failure email. When the domain points somewhere new, the certificate can fail to renew, which is one reason to understand what DNS is and why changes take time.

What to keep out of the browser

HTTPS protects traffic, not secrets left in the page itself. Keys placed in front-end code are visible to anyone who opens the page source, whether or not the connection is encrypted. If you are unsure whether your build did that, can an AI coding agent leak your API keys lists the places to look. SSH keys solve the same trust problem for server logins, and what an SSH key is explains how.

FAQ

Is HTTPS the same as SSL?

HTTPS today uses TLS. SSL is the older name for the same family of protocols and is still used in conversation. A "SSL certificate" is a TLS certificate.

Does HTTPS make my website secure?

It secures the connection only. You still need safe code, careful permissions and protected storage.

Can a scam site use HTTPS?

Yes. A certificate shows control of a domain, not good intent. Check the exact address, not just the padlock.

Is HTTPS free?

Free certificates exist. Let's Encrypt is one, and most hosting platforms include certificates in their service.

Do I need HTTPS for a site with no login?

Yes, it is still worth having. It stops others from altering your pages in transit, and many browsers flag plain HTTP sites as not secure.

How did this land?

About the author

Cecilia Iona
Cecilia Iona

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.

Share

Get the next post in your inbox

One email a month. Product updates, engineering posts, and the best of Built with Swarmz.

I agree to receive emails about AI building tips and Swarmz product news. Unsubscribe any time.