# TLS Fingerprints

What JA3 and JA4 identify, and what they cannot tell you.

A TLS fingerprint hashes the parts of a handshake a client picks for itself: versions, ciphers, extensions and their order. Those come from the TLS library, so the fingerprint follows the software, not the network.

That is the strength of the technique and the source of every way it gets misused. Many programs share a library.

## Related

- [PCAP Triage](https://www.cyberkit.win/tools/pcap-triage/)
- [Decoder: Certificate](https://www.cyberkit.win/tools/decoder/?tab=certificate)
- [Zeek Logs](https://www.cyberkit.win/reference/zeek-logs/)

Canonical: https://www.cyberkit.win/reference/tls-fingerprints/

This is a static reference page. It does not collect anything.
