HTTP vs. HTTPS: What's the Difference?
Read the comparison below, or explore it visually. Create a visual lesson comparing http and https using available credits or plan allowance.
HTTPS is HTTP sent through an encrypted TLS connection: the same web protocol, but with the data scrambled so eavesdroppers cannot read or alter it, plus a certificate proving the website really owns its domain name. Plain HTTP sends everything, including passwords typed into forms, as readable text, so browsers label HTTP pages 'Not secure'.
At a glance
| HTTP | HTTPS | |
|---|---|---|
| Encryption | None: data travels as plain text | Encrypted with TLS |
| Default port | Port 80 | Port 443 |
| Identity check | No proof of the site's identity | Server proves its identity with a digital certificate |
| Tampering | Data can be read or altered in transit | Any alteration in transit is detected |
| Browser label | Marked 'Not secure' | Shown as a secure connection, no warning |
Which should you use?
Plain HTTP survives mainly on closed networks and test setups, such as the settings page of an older home router opened at a local address like 192.168.1.1.
HTTPS should be used on every public website, and it is essential wherever people log in or pay, such as net banking, email accounts and online shopping checkouts.