ARTIFACTORY: How to check TLS version being used for an endpoint

AuthorFullName__c
Deepti Sharma
articleNumber
000006024
FirstPublishedDate
2024-02-04T09:14:21Z
lastModifiedDate
2025-07-22

ARTIFACTORY: How to check TLS version being used for an endpoint

What does TLS do?

TLS (Transport Layer Security) is  like a special tool that helps keep our online communication safe and private.
So, when you're on the internet, and you visit a website, TLS works to make sure that the information you share, like passwords or personal details, is encrypted or scrambled. This way, it's harder for anyone to peek at what you're doing online.

TLS is super important because it helps protect our sensitive information when we're using websites or apps. It's like a virtual lock that keeps our data safe as it travels between our devices and the internet.

TLSv1.3 vs TLS v1.2

We have more advantages definitely of using TLS 1.3 over TLS 1.2 for our online communication. TLS 1.3 offers faster and more secure HTTPS connections through a streamlined handshake process, requiring only one round trip or none for repeat connections. This reduces latency and enhances the overall user experience.
Additionally, TLS 1.3 addresses vulnerabilities present in TLS 1.2 by dropping support for older, potentially compromised cryptographic algorithms. This proactive security measure significantly strengthens resistance to cyber-attacks.
In Jfrog, We surely support TLSv1.3 but we don't restrict other TLS versions also.

How to check which TLS version is used for JFrog url:-

You can use openssl command to verify which TLS version it is using. This command will result in protocol of TLS ,as follows, which also shows protocol for TLS:-

#openssl s_client -showcerts -servername servername.jfrog.io -connect servername.jfrog.io:443
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: 0A104AFBxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx24