Transport Layer Security meaning, in plain words

TLS encrypts traffic so it cannot be read, altered or spoofed in transit. What RFC 9846 and RFC 8996 say about versions, and what to check on your site.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

TLS is a mechanism that encrypts the content of communication to prevent snooping on the way. The name is short for Transport Layer Security, and the IETF's RFC 9846 describes it as a method designed to prevent eavesdropping, tampering, and message forgery. It is the foundation of HTTPS, which protects website traffic.

How does TLS work?

Picture a sealed registered letter. The contents are hidden by the envelope, and if someone opens it on the way, you can tell. You can also check that the receiving counter is the genuine one. TLS gives communication these three.

RFC 9846 sets out the properties required of a communication path as authentication, confidentiality, and integrity. In authentication, the server side is always checked, and checking the user side is optional. Confidentiality means that the data after the connection is established can be read only by the two end devices. Integrity means that if an attacker rewrites the data, it can be noticed.

The latest version is TLS 1.3, whose specification is defined in RFC 9846. RFC 2246 placed the first version, TLS 1.0, on the foundation of SSL 3.0. How older versions are treated is set out in insecure communication. If you want your encryption settings reviewed, contact us.

Why does TLS matter?

Older versions of TLS do not meet today's level. RFC 8996 rules that TLS 1.0 and TLS 1.1 must not be used and formally deprecates them. As reasons, the RFC cites that the weakness of SHA-1 affects the handshake and signatures, and that newer combinations of ciphers cannot be used. On your own site, check these points.

  • Disable TLS 1.0 and TLS 1.1.
  • Support the latest TLS 1.3.
  • Redirect HTTP access to HTTPS.
  • Go over the settings on a fixed schedule, for example once a year.

What TLS protects is the middle of the communication. It does not prevent flaws inside the site, so think of it together with other measures.

Related terms

  • SSL: the old name for TLS, a mechanism that encrypts communication
  • HTTPS: the way website communication connects safely, encrypted
  • SSL certificate: an electronic certificate that shows a site is genuine
  • HSTS: a mechanism that tells the browser to use only encrypted communication

Frequently asked questions

What is the difference between TLS and SSL?

SSL is an older method that came before TLS. RFC 2246 says TLS 1.0 was based on SSL 3.0. RFC 7568 ruled that SSL 3.0 must not be used. TLS is today's standard, and TLS 1.0 and TLS 1.1 also must not be used.

Is my site safe if it encrypts with TLS?

Not necessarily. What RFC 9846 covers is the protection of the communication path. It gives traffic authentication, confidentiality, and integrity, but it does not prevent flaws in how the site is built or weak administrator passwords. Think of it together with other measures.

Next step

Pitfalls of communication that is not encrypted are in insecure communication. The free URL check can read the public encryption information of your site, and to go over your settings in detail, contact us.

Frequently asked questions

What is the difference between TLS and SSL?

SSL is an older method that came before TLS. RFC 2246 says TLS 1.0 was based on SSL 3.0. RFC 7568 ruled that SSL 3.0 must not be used. TLS is today's standard, and TLS 1.0 and TLS 1.1 also must not be used.

Is my site safe if it encrypts with TLS?

Not necessarily. What RFC 9846 covers is the protection of the communication path. It gives traffic authentication, confidentiality, and integrity, but it does not prevent flaws in how the site is built or weak administrator passwords. Think of it together with other measures.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.