HTTPS
HTTPS is HTTP carried over an encrypted TLS connection.
HTTPS protects data in transit against passive reading and helps authenticate the server through certificates. Modern production websites normally use HTTPS for pages, forms, APIs and assets.
What TLS adds to HTTP
HTTPS protects data in transit against passive reading and helps authenticate the server through certificates. Modern production websites normally use HTTPS for pages, forms, APIs and assets. In practical terms, HTTPS belongs to the browser, server or document layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.
A protected browser-to-server exchange
https:// protects data in transit with TLS, so form submissions and page resources are encrypted between the browser and server.
Where HTTPS can still break
You do not need to memorize the term in isolation. It becomes useful when you can recognize it in the tool, browser, file or conversation where the concept is doing real work.
HTTPS is more than a padlock icon
HTTPS is HTTP carried over an encrypted TLS connection. By contrast, HTTP, the Hypertext Transfer Protocol, is the application-layer protocol used to transfer web resources and messages between clients and servers. The two can appear in the same project, but they describe different parts of the work and should not be used as interchangeable labels.
The mistake: assuming one secure page secures every resource
The common mistake is to use HTTPS as if it also meant HTTP. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Check the browser security indicator and verify that all page resources are also loaded over HTTPS.
Why transport security changes trust
In day-to-day work, HTTPS matters when HTTP traffic is protected with TLS encryption. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.
https:// protects data in transit with TLS, so form submissions and page resources are encrypted between the browser and server. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.
Related terms worth learning next
Sources and further reading
Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.