TLS Client Hello Mirror
This service presents your browser's TLS Client Hello message in multiple formats. It can be used directly or in CI tests to check for TLS privacy pitfalls (session resumption , fingerprinting , system time exposure ) and security shortcomings (deprecated TLS versions, weak cipher suites, missing features, etc). Details here .
API endpoints
API documentation
TLS session resumption marginally speeds up the initiation of connections, but it affects privacy in much the same way that HTTP cookies do: the server provides a unique token that your browser sends back on subsequent connections, allowing the server to link your visits even if your IP address changes. The browser can mitigate this by enforcing a short TLS session lifetime: the paper linked below proposes a limit of 10 minutes or less.
Tracking Users across the Web via TLS Session Resumption
Supported features
Signed certificate timestamps: false
OCSP stapling: true
Supported TLS/SSL versions
Cipher suites
Extensions
psk_ key_ exchange_ modes
key_ share
supported_ groups
status_ request
ec_ point_ formats
application_ layer_ protocol_ negotiation
server_ name
signature_ algorithms
supported_ versions
extended_ master_ secret
pre_ shared_ key
Supported groups
x25519
secp256r1
secp384r1
Signature algorithms
ecdsa_ secp384r1_ sha384
ecdsa_ secp256r1_ sha256
ed25519
rsa_ pss_ rsae_ sha512
rsa_ pss_ rsae_ sha384
rsa_ pss_ rsae_ sha256
rsa_ pkcs1_ sha512
rsa_ pkcs1_ sha384
rsa_ pkcs1_ sha256
TLS fingerprint
JA3: 771 ,4866- 4865- 4867- 49196- 49195- 52393- 49200- 49199- 52392- 255 ,45- 51- 10- 5- 11- 16- 0- 13- 43- 23- 41 ,29- 23- 24 ,0
JA3 MD5: ba5f96fa524d73e1cbdc53cd68666986
NJA3v1: 769 ,771 ,4866- 4865- 4867- 49196- 49195- 52393- 49200- 49199- 52392- 255 ,5- 10- 11- 13- 23- 43- 45- 51 ,29- 23- 24 ,0 ,772- 771 ,1283- 1027- 2055- 2054- 2053- 2052- 1537- 1281- 1025 ,1 ,
NJA3v1 SHA256/128: 3a5ed305b1c7e28d0c2c3b16584b8673
Parameters in the Client Hello message differ between clients, enabling servers and on-path observers to detect what browser you are likely using (down to its version, or a range of versions) by deriving its fingerprint from said parameters. Worse, if you change any TLS-related settings, your TLS fingerprint becomes specific to a much smaller group of users, possibly even to you alone.
JA3 is a simple and popular type of TLS fingerprint. NJA3 is a similar style of fingerprint which aims to improve the robustness and accuracy of JA3.