t12d600400_891918f05457_c54f48fd7c65
Shares its JA4_c (c54f48fd7c65) with 14 fingerprints 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
t12d600400
handshake shape, human-readable
891918f05457
truncated hash of the cipher list
c54f48fd7c65
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.2
- Server name
- server name sent
- Cipher suites offered
- 60
- Extensions offered
- 4
- ALPN
- none offered
Same tool, different options
These 20 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.
- t12d040400_058957366436_c54f48fd7c65
- t12d280400_860185aaa100_c54f48fd7c65
- t12d600400_68200713fd55_c54f48fd7c65
- t12d600400_6f32ba44e122_c54f48fd7c65
- t12d600400_bea8ef14a674_c54f48fd7c65
- t12d600400_f78222e0ad5a_c54f48fd7c65
- t12d600400_fd5e89c4ed05_c54f48fd7c65
- t12d640400_1715b94e3896_c54f48fd7c65
- t12d640400_1e98fdfb27e9_c54f48fd7c65
- t12d640400_a3acda31d846_c54f48fd7c65
- t12d640400_e31a90cd0803_c54f48fd7c65
- t12d640400_e7b476f9520b_c54f48fd7c65
- t12d640400_f559eb9565fd_c54f48fd7c65
- t12i040300_058957366436_c54f48fd7c65
- t12i640300_1715b94e3896_c54f48fd7c65
- t12i640300_1e98fdfb27e9_c54f48fd7c65
- t12i640300_a3acda31d846_c54f48fd7c65
- t12i640300_e31a90cd0803_c54f48fd7c65
- t12i640300_e7b476f9520b_c54f48fd7c65
- t12i640300_f559eb9565fd_c54f48fd7c65
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 60
-
49320 (0xc0a8) -
168 (0x00a8) -
141 (0x008d) -
175 (0x00af) -
49317 (0xc0a5) -
49321 (0xc0a9) -
169 (0x00a9) -
49252 (0xc064) -
49258 (0xc06a) -
49253 (0xc065) -
49259 (0xc06b) -
49300 (0xc094) -
49294 (0xc08e) -
49301 (0xc095) -
49295 (0xc08f) -
52395 (0xccab) -
44 (0x002c) -
176 (0x00b0) -
177 (0x00b1) -
138 (0x008a) -
98 (0x0062) -
97 (0x0061) -
96 (0x0060) -
100 (0x0064) -
8 (0x0008) -
6 (0x0006) -
3 (0x0003) -
147 (0x0093) -
148 (0x0094) -
182 (0x00b6) -
172 (0x00ac) -
149 (0x0095) -
183 (0x00b7) -
173 (0x00ad) -
49256 (0xc068) -
49262 (0xc06e) -
49257 (0xc069) -
49263 (0xc06f) -
49304 (0xc098) -
49298 (0xc092) -
49305 (0xc099) -
49299 (0xc093) -
52398 (0xccae) -
46 (0x002e) -
184 (0x00b8) -
185 (0x00b9) -
146 (0x0092) -
124 (0x007c) -
TLS_RSA_WITH_3DES_EDE_CBC_SHA -
125 (0x007d) -
TLS_RSA_WITH_AES_128_CBC_SHA -
TLS_RSA_WITH_AES_128_CBC_SHA256 -
TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256 -
TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256 -
TLS_RSA_WITH_AES_128_GCM_SHA256 -
126 (0x007e) -
TLS_RSA_WITH_AES_256_CBC_SHA -
TLS_RSA_WITH_AES_256_CBC_SHA256 -
TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384 -
TLS_ECDHE_ECDSA_WITH_ARIA_256_GCM_SHA384
Extensions 4
-
supported_groups -
ec_point_formats -
server_name -
signature_algorithms
Named groups 5
-
secp256r1 -
secp384r1 -
secp521r1 -
x25519 -
ffdhe2048
Point formats 1
-
uncompressed
Raw JA3 string
771,49320-168-141-175-49317-49321-169-49252-49258-49253-49259-49300-49294-49301-49295-52395-44-176-177-138-98-97-96-100-8-6-3-147-148-182-172-149-183-173-49256-49262-49257-49263-49304-49298-49305-49299-52398-46-184-185-146-124-10-125-47-60-49308-49312-156-126-53-61-49309-49313,10-11-0-13,23-24-25-29-256,0Seen in live traffic
- Connections
- 5
- First seen
- 2026-10-03 09:37 UTC
- Last seen
- 2026-10-24 09:41 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 3
The same client, 3 different JA3s
This one JA4 covers 3 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 3 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
f25adf0dcba24fa736de1a2cd1b202f65430a1fd0ac1e4b07d27cfd8c927e446ebe449121742cd5425ee782a9c0780c8
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.