HTTP & Networking

What is HTTPS?

HTTP encrypted with TLS, the same protocol, but every byte on the wire is authenticated and protected from eavesdroppers.

HTTPS is HTTP running inside a TLS-encrypted tunnel. The application-layer semantics are unchanged, you still send GET / and receive a status code, but the bytes that move between client and server are encrypted, integrity-checked, and authenticated against a server certificate.

In 2026, HTTPS is effectively mandatory. Browsers mark plain HTTP as "Not secure," HTTP/2 only runs over TLS in practice, and mixed-content rules block subresources loaded over HTTP from HTTPS pages. Free certificates from Let's Encrypt removed the last cost objection a decade ago.

When you fetch an HTTPS URL, your client validates the server's certificate against a chain of trusted CAs, negotiates a session key, and then exchanges normal HTTP messages over that encrypted channel. The cost is a small handshake overhead on the first connection, usually 1-2 round trips, that disappears with TLS 1.3 session resumption.

How Brand.dev uses https

Endpoints in the Brand.dev API where this concept comes up directly.

FAQ

Is HTTPS just HTTP with SSL?

Almost. HTTPS uses TLS, not SSL, SSL was deprecated years ago and is now a generic name people use. Modern HTTPS uses TLS 1.2 or 1.3.

Does HTTPS hide my URL?

It hides the path, query string, headers, and body from anyone watching your network. The destination hostname leaks via SNI on the initial handshake, and via DNS unless you use DoH/DoT.

Why do some sites still serve HTTP?

Almost always legacy infrastructure or redirects misconfigured. Every modern hosting platform terminates TLS for you for free.

Related terms

Ship an agent that actually knows things.

Free tier, 10-minute integration, and the same API powering agents at Mintlify, daily.dev, and Propane. No credit card to start.