What is SSL encryption?
SSL stands for Secure Sockets Layer. It was an early protocol for encrypting data sent over the internet, including web traffic. SSL is obsolete and should not be used to protect modern connections.
SSL was designed to protect information in transit through encryption and authentication. Known weaknesses mean it no longer provides an acceptable level of protection. Modern secure connections use TLS, its successor.
How SSL worked
SSL combined a handshake, authentication, and encryption to protect data in transit. These mechanisms explain its historical role, not a recommendation to use the obsolete protocol.
Handshake
The client and server performed a handshake to agree on protocol settings and establish keys. The server typically presented a certificate to authenticate itself.
Encryption
After the handshake, symmetric session keys encrypted the data exchanged between client and server.
Decryption
The receiving party used the session keys to decrypt the data. Vulnerabilities in SSL could undermine the protection this process was intended to provide.
Key components of SSL
SSL used certificates, cryptographic keys, and cipher suites. TLS retains these broad concepts with updated protocol design and security requirements.
Certificates
Certificates helped authenticate the server. The marketing term “SSL certificate” is still widely used today, but a modern certificate normally supports a TLS connection and does not imply use of the SSL protocol.
Keys
Asymmetric keys supported authentication and, in some cipher suites, key exchange. Symmetric session keys encrypted the connection’s application data.
Ciphers
Cipher suites defined the algorithms used by the connection. Obsolete SSL protocols and weak algorithms must not be treated as modern security controls.
SSL vs TLS
SSL is obsolete, while TLS is its successor. A secure modern website uses a supported, correctly configured TLS implementation.
SSL
SSL was the original protocol for securing web traffic. It has been deprecated due to security vulnerabilities.
TLS
TLS is the successor to SSL and is the current standard for securing web traffic. It includes improvements in security and performance.
Versions
SSL 3.0 was the final SSL version. All SSL versions are obsolete. Modern deployments use TLS 1.2 or TLS 1.3 with suitable cipher suites and secure configuration.
Why SSL was replaced
SSL has known vulnerabilities that make it unsuitable for protecting sensitive information. Its former security role is now served by TLS.
Obsolete protection
SSL cannot provide the protection expected from a modern encrypted connection. Systems should disable it and use securely configured TLS.
Certificate terminology
An “SSL certificate” label does not tell you which protocol a connection uses. A valid certificate alone also does not establish that the website’s content or operator is trustworthy.
Security standards and compliance
PCI DSS does not recognise SSL or early TLS as strong cryptography. GDPR calls for security measures appropriate to the risk rather than requiring SSL or a named TLS version.
Connection security
Correctly configured TLS provides encryption, integrity protection, and authentication for data in transit. Obsolete SSL should not be relied on to prevent interception or tampering.
How to check a website’s encrypted connection
Use your browser’s address bar and connection information when checking a website. These checks do not apply to a native app.
HTTPS
An HTTPS URL indicates an encrypted web connection. Modern HTTPS uses TLS; the HTTPS prefix does not mean that the obsolete SSL protocol is in use.
Browser connection information
Open the site-information or connection controls beside the website address. Browser icons vary, so a padlock is not shown in every browser.
Certificate details
Use the browser’s certificate viewer to inspect the issuer and validity period. Detailed security information may also show the negotiated protocol, depending on the browser.
SSL encryption and XPlace
XPlace uses TLS encryption, the successor to SSL, to protect data sent between your device and its servers. This helps keep your personal and payment information secure.
For the XPlace website, check HTTPS and your browser’s connection details. The native app has no browser address bar, so these checks apply only to the website.

