t13d050700_fe8b0b18143e_2f3d4148c47a
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
t13d050700
handshake shape, human-readable
fe8b0b18143e
truncated hash of the cipher list
2f3d4148c47a
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 5
- Extensions offered
- 7
- ALPN
- none offered
The hello it was computed from
Recovered because the proxy now stores the pre-hash JA3 string alongside the digest. Every number below came out of this client's ClientHello; anything we cannot name in the IANA registry is shown as its raw value rather than guessed at.
- Version
- TLS 1.2
Cipher suites 5
-
TLS_AES_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_CCM_SHA256 -
TLS_AES_128_CCM_8_SHA256
Extensions 7
-
server_name -
ec_point_formats -
session_ticket -
signature_algorithms -
supported_versions -
supported_groups -
key_share
Named groups 1
-
17 (0x0011)
Point formats 3
-
uncompressed -
ansiX962_compressed_prime -
ansiX962_compressed_char2
Raw JA3 string
771,4865-4866-4867-4868-4869,0-11-35-13-43-10-51,17,0-1-2Seen in live traffic
- Connections
- 46
- First seen
- 2026-10-06 20:48 UTC
- Last seen
- 2026-10-06 20:48 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 46
The same client, 46 different JA3s
This one JA4 covers 46 distinct JA3 hashes. A JA3 hashes the cipher and extension lists in the order they arrived, so a client that shuffles them — which Chrome and its derivatives do on purpose — produces a new JA3 almost every connection and fragments into what looks like 46 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
85b0cf15f152518ab9aea9f97fc1548773444a6778efdcb70f80d3ce720cd88035c7935a6e9ff94f4b497ab10e23ea197788ee51381b988668637524dd589ea6b07a936672e8fecef4b21800fdd2a78ec6e9a04786ee0efc9a02d5e4c1809a6a3e04a33522e602de5067c5cd02581e6bdd7fe923444f8bee84ab45bec299ad2e2736d7d4ceb50d02a9d8be75129a09b763daac68608cd01efb47a228f6d681ee888df0f4f0968b277476d775740dedb4d76c541ef3bee12901c40aa2ac69b822- … and 34 more
This entry is an observation, not a policy decision. It is here because the edge saw it, not because anyone reviewed it, and it blocks nothing on its own. Only the curated tier drives classification and banning.