t12d520600_7554301188de_e51b7354d87f
Shares its JA4_c (e51b7354d87f) with 1 fingerprint classified as scanner, and nothing else in that family disagrees — the same tool under different cipher options. Inferred from the family, not observed directly.
What this fingerprint encodes
t12d520600
handshake shape, human-readable
7554301188de
truncated hash of the cipher list
e51b7354d87f
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.2
- Server name
- server name sent
- Cipher suites offered
- 52
- Extensions offered
- 6
- ALPN
- none offered
Same tool, different options
These 3 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.
- t12d130600_2d7513195f68_e51b7354d87f
- t12d400600_44c89e5422f1_e51b7354d87f
- t12i130500_2d7513195f68_e51b7354d87f
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 52
-
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA -
TLS_ECDHE_RSA_WITH_RC4_128_SHA -
TLS_DHE_RSA_WITH_AES_256_CBC_SHA -
64 (0x0040) -
102 (0x0066) -
163 (0x00a3) -
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 -
106 (0x006a) -
TLS_RSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA -
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_ECDSA_WITH_RC4_128_SHA -
3 (0x0003) -
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA -
TLS_RSA_WITH_AES_128_CBC_SHA -
TLS_RSA_WITH_RC4_128_MD5 -
8 (0x0008) -
162 (0x00a2) -
TLS_RSA_WITH_AES_256_CBC_SHA256 -
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA -
19 (0x0013) -
25 (0x0019) -
50 (0x0032) -
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 -
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 -
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA -
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 -
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 -
TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 -
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 -
TLS_RSA_WITH_AES_256_CBC_SHA -
TLS_RSA_WITH_AES_128_CBC_SHA256 -
TLS_DHE_RSA_WITH_AES_128_CBC_SHA -
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 -
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 -
TLS_RSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 -
TLS_RSA_WITH_3DES_EDE_CBC_SHA -
17 (0x0011) -
18 (0x0012) -
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 -
21 (0x0015) -
20 (0x0014) -
23 (0x0017) -
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 -
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA -
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA -
6 (0x0006) -
56 (0x0038) -
TLS_RSA_WITH_RC4_128_SHA
Extensions 6
-
server_name -
status_request -
supported_groups -
ec_point_formats -
signature_algorithms -
renegotiation_info
Named groups 3
-
secp256r1 -
secp384r1 -
secp521r1
Point formats 1
-
uncompressed
Raw JA3 string
771,49162-49169-57-64-102-163-49200-106-156-49172-158-49159-3-49160-47-4-8-162-61-49170-19-25-50-103-49199-159-49195-22-107-49191-52394-49192-53-60-51-52392-49188-157-49187-10-17-18-49196-21-20-23-52393-49161-49171-6-56-5,0-5-10-11-13-65281,23-24-25,0Seen in live traffic
- Connections
- 9
- First seen
- 2026-09-03 18:52 UTC
- Last seen
- 2026-10-13 09:37 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 9
The same client, 9 different JA3s
This one JA4 covers 9 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 9 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
70c5e951d944813c658de9c7ac81fe32a72c59c9a862b8f9522d96da837cd017f05eba3492d1816dc560613ee4e2920077f345bb6929f410f22cdc2cc7d5c0528298ab6c91b5647b1cd77b0f585455b8c322cf491f2f9418d627ab16c153646f0094cf67bcf806caefa0a8244ee1cd77e9da4e41318323918a489cf658abff0817441c51b7f60ac9ceea81da25a495cc
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.