Glossary · ENCheck a domain

Connection encryption

Connection encryption transforms data into a form that is difficult for outsiders to read while it travels between the two ends of a connection. The devices or programs at each end use digital keys to protect and recover the data. When a browser uses HTTPS, encryption helps keep the contents of the web conversation private from someone observing the network between the browser and the server.

What does encryption protect?

Encryption mainly protects the content sent over the connection from being read by someone who does not have the right keys. Modern secure protocols such as TLS also check that protected data has not been changed without detection. TLS can authenticate the server as well, so a browser can check that it has connected to a server presenting a certificate for the requested name.

For example, if Casey signs in over HTTPS on a public Wi-Fi network, a person watching that network should not be able to read the protected login data in transit. Casey's network operator may still see some connection details, such as that the device contacted a particular IP address, and encryption does not stop the website itself from receiving the submitted information.

Is encryption the same as identity verification?

No. Encryption makes the traffic unreadable to outsiders without the key, but it does not by itself tell a browser who is at the other end. A secure connection protocol combines encryption with checks for undetected changes and a way to verify the server's identity. In HTTPS, TLS uses certificate-based checks to help match the server to the domain in the address.

Encryption also does not prove that the website is honest or that its content is safe. A scam site can establish an encrypted connection. The protection applies to the connection, not to the truth or intent of the information being sent.

Related terms