t12d860600_e18388e7f3a3_25552ceac63b
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
t12d860600
handshake shape, human-readable
e18388e7f3a3
truncated hash of the cipher list
25552ceac63b
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.2
- Server name
- server name sent
- Cipher suites offered
- 86
- Extensions offered
- 6
- ALPN
- none offered
Same tool, different options
These 46 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.
- t12d020600_049d0968ef63_25552ceac63b
- t12d020600_04f72be57293_25552ceac63b
- t12d020600_0c0b01a5a80b_25552ceac63b
- t12d020600_0d62a58dd912_25552ceac63b
- t12d020600_104943d1f64b_25552ceac63b
- t12d020600_184f2be1a0c6_25552ceac63b
- t12d020600_24f557f1cbee_25552ceac63b
- t12d020600_2ac205266896_25552ceac63b
- t12d020600_46916985df61_25552ceac63b
- t12d020600_48762405b09c_25552ceac63b
- t12d020600_4eff32302ec7_25552ceac63b
- t12d020600_4f4bd29a6b59_25552ceac63b
- t12d020600_53d483789bba_25552ceac63b
- t12d020600_55a2bbf9cbd7_25552ceac63b
- t12d020600_57ba72230e7a_25552ceac63b
- t12d020600_59980b593f60_25552ceac63b
- t12d020600_5b44afd80a2d_25552ceac63b
- t12d020600_5cd2152a341f_25552ceac63b
- t12d020600_68cd44b4e773_25552ceac63b
- t12d020600_6a7d5ebe9983_25552ceac63b
- t12d020600_6d4732649639_25552ceac63b
- t12d020600_7368e9b57fb4_25552ceac63b
- t12d020600_89e01831f9a8_25552ceac63b
- t12d020600_8fc24edd70fe_25552ceac63b
- t12d020600_9b38dd297dfe_25552ceac63b
- t12d020600_a0546e0689fc_25552ceac63b
- t12d020600_a89416eb2da9_25552ceac63b
- t12d020600_adebd50f2b51_25552ceac63b
- t12d020600_b06afd972a5c_25552ceac63b
- t12d020600_b2ba452b8222_25552ceac63b
- t12d020600_bad2b1bd13d4_25552ceac63b
- t12d020600_c4610a930072_25552ceac63b
- t12d020600_c66b7cee1896_25552ceac63b
- t12d020600_cc27769a2ea2_25552ceac63b
- t12d020600_d0ac5cb1209a_25552ceac63b
- t12d020600_d576ba9a1b51_25552ceac63b
- t12d020600_efa2d734833b_25552ceac63b
- t12d020600_f09d9ff7e6fc_25552ceac63b
- t12d020600_f17337cd55b5_25552ceac63b
- t12d020600_f3042cbcf579_25552ceac63b
- t12d020600_f3e6ef936ef8_25552ceac63b
- t12d310600_f3b328a90fc1_25552ceac63b
- t12d340600_498eeac4deb3_25552ceac63b
- t12d490600_730fb1b0ac6a_25552ceac63b
- t12d650600_77b304177063_25552ceac63b
- t12d670600_3d07528e3801_25552ceac63b
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 86
-
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 -
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 -
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 -
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA -
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA -
165 (0x00a5) -
163 (0x00a3) -
161 (0x00a1) -
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 -
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 -
106 (0x006a) -
105 (0x0069) -
104 (0x0068) -
TLS_DHE_RSA_WITH_AES_256_CBC_SHA -
56 (0x0038) -
55 (0x0037) -
54 (0x0036) -
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA -
135 (0x0087) -
134 (0x0086) -
133 (0x0085) -
49202 (0xc032) -
49198 (0xc02e) -
49194 (0xc02a) -
49190 (0xc026) -
49167 (0xc00f) -
49157 (0xc005) -
TLS_RSA_WITH_AES_256_GCM_SHA384 -
TLS_RSA_WITH_AES_256_CBC_SHA256 -
TLS_RSA_WITH_AES_256_CBC_SHA -
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA -
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 -
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 -
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 -
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA -
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA -
164 (0x00a4) -
162 (0x00a2) -
160 (0x00a0) -
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 -
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 -
64 (0x0040) -
63 (0x003f) -
62 (0x003e) -
TLS_DHE_RSA_WITH_AES_128_CBC_SHA -
50 (0x0032) -
49 (0x0031) -
48 (0x0030) -
TLS_DHE_RSA_WITH_SEED_CBC_SHA -
153 (0x0099) -
152 (0x0098) -
151 (0x0097) -
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA -
68 (0x0044) -
67 (0x0043) -
66 (0x0042) -
49201 (0xc031) -
49197 (0xc02d) -
49193 (0xc029) -
49189 (0xc025) -
49166 (0xc00e) -
49156 (0xc004) -
TLS_RSA_WITH_AES_128_GCM_SHA256 -
TLS_RSA_WITH_AES_128_CBC_SHA256 -
TLS_RSA_WITH_AES_128_CBC_SHA -
TLS_RSA_WITH_SEED_CBC_SHA -
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA -
7 (0x0007) -
TLS_ECDHE_RSA_WITH_RC4_128_SHA -
TLS_ECDHE_ECDSA_WITH_RC4_128_SHA -
49164 (0xc00c) -
49154 (0xc002) -
TLS_RSA_WITH_RC4_128_SHA -
TLS_RSA_WITH_RC4_128_MD5 -
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA -
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA -
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA -
19 (0x0013) -
16 (0x0010) -
13 (0x000d) -
49165 (0xc00d) -
49155 (0xc003) -
TLS_RSA_WITH_3DES_EDE_CBC_SHA -
TLS_EMPTY_RENEGOTIATION_INFO_SCSV
Extensions 6
-
server_name -
ec_point_formats -
supported_groups -
session_ticket -
signature_algorithms -
heartbeat
Named groups 13
-
secp256r1 -
secp521r1 -
28 (0x001c) -
27 (0x001b) -
secp384r1 -
26 (0x001a) -
22 (0x0016) -
14 (0x000e) -
13 (0x000d) -
11 (0x000b) -
12 (0x000c) -
9 (0x0009) -
10 (0x000a)
Point formats 3
-
uncompressed -
ansiX962_compressed_prime -
ansiX962_compressed_char2
Raw JA3 string
771,49200-49196-49192-49188-49172-49162-165-163-161-159-107-106-105-104-57-56-55-54-136-135-134-133-49202-49198-49194-49190-49167-49157-157-61-53-132-49199-49195-49191-49187-49171-49161-164-162-160-158-103-64-63-62-51-50-49-48-154-153-152-151-69-68-67-66-49201-49197-49193-49189-49166-49156-156-60-47-150-65-7-49169-49159-49164-49154-5-4-49170-49160-22-19-16-13-49165-49155-10-255,0-11-10-35-13-15,23-25-28-27-24-26-22-14-13-11-12-9-10,0-1-2Seen in live traffic
- Connections
- 287
- First seen
- 2026-08-23 08:40 UTC
- Last seen
- 2026-10-10 05:33 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.
fd80fa9c6120cdeea8520510f3c644acb22b3950835f7eba2f3be0917e4f949e
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.