πŸ“„
Webhosting

SSL handshake explained: how does a connection work?

πŸ“… 19 November 2026 ✏️ 19 November 2026 ⏱ 5 min leestijd

Curious how an SSL/TLS handshake works? Read step by step how your browser and server set up a secure connection.

Every time you visit a website with HTTPS, a so-called SSL handshake takes place in the background. This is the process in which your browser and the web server make agreements about how they will communicate securely, even before a single piece of content is loaded. In this article we explain which steps are involved, why this is important, and what you can do if something goes wrong.

What is an SSL handshake?

The term SSL handshake is still widely used, but nowadays virtually all secure communication runs on TLS (Transport Layer Security), the successor to SSL. The name has stuck, but the principle remains the same: browser and server negotiate a secure connection before any data is exchanged.

During this negotiation, three things happen at once: the server proves who it is (via the SSL certificate), both parties agree on which encryption algorithm to use, and a shared key is agreed upon with which further traffic will be encrypted. Without this handshake, no padlock would appear in the browser bar and traffic would travel unencrypted over the internet.

The steps of the handshake

A handshake roughly consists of a number of fixed steps. The exact order differs slightly per TLS version, but the principle remains the same.

1

Client Hello

The browser sends a message to the server with the supported TLS versions, encryption methods, and a randomly generated number.

2

Server Hello and certificate

The server chooses a suitable TLS version and encryption method, and sends its SSL certificate back so the browser can check whether the server really is who it claims to be.

3

Certificate check

The browser checks whether the certificate was issued by a trusted certificate authority, is still valid, and belongs to the correct domain.

4

Key exchange

Browser and server together compute a shared secret key, without it ever traveling unencrypted over the line.

5

Encrypted connection starts

From this point on, all communication between browser and server is encrypted with the agreed key.

πŸ’‘ Tip: This entire process takes only a fraction of a second, but with slow servers or outdated configurations it can cause noticeable delays. A fast server and up-to-date TLS settings therefore really do make a difference for your site’s loading time.

TLS versions and differences

Several versions of TLS have been in circulation. Older versions are no longer supported by modern browsers because they contain vulnerabilities. The newest version performs the handshake more efficiently, with less back-and-forth traffic between browser and server, making the connection faster without sacrificing security.

Which version is used depends on what both the browser and server support: they automatically choose the highest version both parties share. As a server administrator, you can configure which versions are allowed, so that outdated and insecure versions are rejected.

Recognizing and solving handshake problems

Sometimes a handshake fails and a visitor gets an error message in the browser instead of your website. Common causes are an expired certificate, an incorrectly configured certificate chain, a mismatch between the domain name and the certificate, or a server that only supports outdated TLS versions which the browser rejects.

If you encounter problems, first check whether the certificate is still valid and matches the correct domain name. Then look at the server configuration: in Plesk you can find the SSL settings per domain, where you can also see which certificate is active and when it expires. An incorrect or incomplete certificate chain is also a common cause, which you often recognize by warnings that only appear on certain devices or browsers.

If you get stuck, check the knowledge base for more background articles, or ask for help if you have a web hosting package with Tandata.

Frequently asked questions

Is SSL the same as TLS?

SSL is the predecessor of TLS. The name SSL is still often used out of habit, but technically speaking virtually all secure internet traffic now runs on TLS.

Why does a handshake sometimes take longer?

This can be due to a slow server, a long certificate chain, outdated TLS settings, or network delay between browser and server.

Can I see for myself which TLS version is being used?

Yes, in most browsers you can see the certificate details of a website (click the padlock in the address bar) to find out which TLS version and encryption method are being used.

Does a handshake also work for email?

Yes, email traffic via SMTP, IMAP, and POP3 can also be encrypted via TLS with a similar handshake. This is relevant when setting up business email.

Conclusion

The SSL handshake is the invisible process by which browser and server build a trust relationship before exchanging data. It combines certificate verification, encryption, and key exchange within a matter of seconds. A well-configured server with a valid certificate and modern TLS settings ensures a fast, secure connection without error messages.

View web hosting β†’

Was dit artikel nuttig?