TLS Connection Inspector — the handshake behind this page

Protocol version, negotiated cipher suite, HTTP version and handshake round-trip time for the exact connection you are reading this page over.

TLS version	TLSv1.3
Cipher suite	AEAD-AES256-GCM-SHA384
HTTP protocol	HTTP/2
TCP handshake RTT	2 ms
Edge datacenter	CMH
Client address	216.73.216.227

Reading the result

Protocol version TLSv1.3

TLS 1.3 is current. It removes the round trip that 1.2 needed, encrypts more of the handshake, and drops every cipher suite with a known structural weakness.

HTTP version HTTP/2

HTTP/2. Multiplexed and fine, though a single lost packet still stalls every stream on the connection.

TLS fingerprinting goes considerably further than this. The exact ordering of cipher suites, extensions and elliptic curves in your Client Hello forms a JA3 or JA4 hash that identifies your client software independently of anything you can change in settings. We explain that here.

Frequently asked

Why does my TLS version show 1.2 when my browser supports 1.3?

Almost always a TLS-intercepting middlebox: corporate security appliances and some antivirus suites terminate your TLS connection, inspect it, then open their own connection onwards, often with older settings.