t10i640200_13a2a23d501b_c2f961105e84
Probe (legacy TLS, no SNI, no ALPN) — inferred from the JA4 handshake shape.
What this fingerprint encodes
t10i640200
handshake shape, human-readable
13a2a23d501b
truncated hash of the cipher list
c2f961105e84
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.0
- Server name
- no server name (IP literal)
- Cipher suites offered
- 64
- Extensions offered
- 2
- ALPN
- none offered
Same tool, different options
These 11 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.
- t10i640200_67f0ca237a44_c2f961105e84
- t10i640200_a3acda31d846_c2f961105e84
- t10i640200_e31a90cd0803_c2f961105e84
- t10i640200_e7b476f9520b_c2f961105e84
- t10i640200_f559eb9565fd_c2f961105e84
- t11i640200_13a2a23d501b_c2f961105e84
- t11i640200_67f0ca237a44_c2f961105e84
- t11i640200_a3acda31d846_c2f961105e84
- t11i640200_e31a90cd0803_c2f961105e84
- t11i640200_e7b476f9520b_c2f961105e84
- t11i640200_f559eb9565fd_c2f961105e84
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.0
Cipher suites 64
-
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 -
TLS_RSA_WITH_AES_256_GCM_SHA384 -
49212 (0xc03c) -
49232 (0xc050) -
49213 (0xc03d) -
49233 (0xc051) -
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA -
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 -
49274 (0xc07a) -
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA -
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 -
49275 (0xc07b) -
9 (0x0009) -
7 (0x0007) -
1 (0x0001) -
2 (0x0002) -
59 (0x003b) -
TLS_RSA_WITH_RC4_128_MD5 -
TLS_RSA_WITH_RC4_128_SHA -
TLS_RSA_WITH_SEED_CBC_SHA -
49180 (0xc01c) -
49183 (0xc01f) -
49186 (0xc022) -
49179 (0xc01b) -
49182 (0xc01e) -
49185 (0xc021) -
49178 (0xc01a) -
49181 (0xc01d) -
49184 (0xc020)
Extensions 2
-
supported_groups -
ec_point_formats
Named groups 6
-
secp256r1 -
secp384r1 -
secp521r1 -
x25519 -
ffdhe2048 -
SecP256r1MLKEM768
Point formats 1
-
uncompressed
Raw JA3 string
769,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-157-49212-49232-49213-49233-65-186-49274-132-192-49275-9-7-1-2-59-4-5-150-49180-49183-49186-49179-49182-49185-49178-49181-49184,10-11,23-24-25-29-256-4588,0Seen in live traffic
- Connections
- 5
- First seen
- 2026-08-27 08:43 UTC
- Last seen
- 2026-08-27 08:49 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 2
The same client, 2 different JA3s
This one JA4 covers 2 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 2 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
927880f6885de7ab44ce8fe3289a2e243dd271080769b41ca30134e5a6d6c6bd
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.