HTTP sends data as plain text, so anyone on the network path (public Wi-Fi, a router) could read or change it. HTTPS is HTTP inside a TLS connection, which gives three things:
Encryption: others cannot read the traffic.
Integrity: they cannot change it unnoticed.
Authentication: you know you are really talking to that website.
In simple terms, the TLS handshake works like this: the browser says which TLS versions it supports, the server replies with its certificate, the browser checks that a trusted certificate authority signed it and that it matches the domain, and both sides agree on a shared secret key. After that, all data is encrypted with that key.
Today HTTPS is the standard for every site. Browsers warn about plain HTTP, search engines prefer HTTPS, and free certificates are available (for example Let's Encrypt). Redirect HTTP to HTTPS and consider adding an HSTS header.
Markdown for AI
A clean, structured version of this page for AI assistants and LLMs.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
HTTP sends data as plain text, so anyone on the network path (public Wi-Fi, a router) could read or change it. HTTPS is HTTP inside a TLS connection, which gives three things:
In simple terms, the TLS handshake works like this: the browser says which TLS versions it supports, the server replies with its certificate, the browser checks that a trusted certificate authority signed it and that it matches the domain, and both sides agree on a shared secret key. After that, all data is encrypted with that key.
Today HTTPS is the standard for every site. Browsers warn about plain HTTP, search engines prefer HTTPS, and free certificates are available (for example Let's Encrypt). Redirect HTTP to HTTPS and consider adding an HSTS header.