Check out the sections below for information about the SSL/TLS client you used to render this page.
Yeah, we really mean "TLS", not "SSL".
Good Your client is using TLS 1.3, the most modern version of the encryption protocol. It gives you access to the fastest, most secure encryption possible on the web.
Improvable Your client does not support post-quantum key agreement. Without that support, your traffic could be stored by adversaries today and decrypted once sufficiently powerful quantum computers become available. The expected timeline for cryptographically-relevant quantum computers has shifted earlier, and support for post-quantum cryptography is necessary to defend against "harvest now, decrypt later" attacks.
Good Ephemeral keys are used in some of the cipher suites your client supports. This means your client may be used to provide forward secrecy if the server supports it. This greatly increases your protection against snoopers, including global passive adversaries who scoop up large amounts of encrypted traffic and store them until their attacks (or their computers) improve.
Good Session tickets are supported in your client. Services you use will be able to scale out their TLS connections more easily with this feature.
Good Your TLS client does not attempt to compress the settings that encrypt your connection, avoiding information leaks from the CRIME attack.
Good Your client doesn't use any cipher suites that are known to be insecure.
Good Your client is not vulnerable to the BEAST attack because it's using a TLS protocol newer than TLS 1.0. The BEAST attack is only possible against clients using TLS 1.0 or earlier using Cipher-Block Chaining cipher suites that do not implement the 1/n-1 record splitting mitigation.
The cipher suites your client said it supports, in the order it sent them, are:
The named groups your client said it supports, in the order it sent them, are: