t13i051300_fe8b0b18143e_5fd1edc2d7a6
Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.
What this fingerprint encodes
t13i051300
handshake shape, human-readable
fe8b0b18143e
truncated hash of the cipher list
5fd1edc2d7a6
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- no server name (IP literal)
- Cipher suites offered
- 5
- Extensions offered
- 13
- 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 13
-
supported_versions -
signature_algorithms -
status_request -
supported_groups -
key_share -
record_size_limit -
signed_certificate_timestamp -
extended_master_secret -
compress_certificate -
renegotiation_info -
ec_point_formats -
psk_key_exchange_modes -
padding
Named groups 50
-
583 (0x0247) -
4585 (0x11e9) -
4589 (0x11ed) -
65053 (0xfe1d) -
12103 (0x2f47) -
65048 (0xfe18) -
12092 (0x2f3c) -
SecP384r1MLKEM1024 -
4591 (0x11ef) -
X25519MLKEM768 -
556 (0x022c) -
65042 (0xfe12) -
571 (0x023b) -
584 (0x0248) -
12107 (0x2f4b) -
12090 (0x2f3a) -
12089 (0x2f39) -
573 (0x023d) -
572 (0x023c) -
12215 (0x2fb7) -
557 (0x022d) -
12109 (0x2f4d) -
65057 (0xfe21) -
570 (0x023a) -
X25519Kyber768Draft00 -
65058 (0xfe22) -
65072 (0xfe30) -
12110 (0x2f4e) -
12214 (0x2fb6) -
558 (0x022e) -
585 (0x0249) -
12204 (0x2fac) -
12108 (0x2f4c) -
12093 (0x2f3d) -
4586 (0x11ea) -
4590 (0x11ee) -
SecP256r1MLKEM768 -
12105 (0x2f49) -
65040 (0xfe10) -
65056 (0xfe20) -
513 (0x0201) -
65073 (0xfe31) -
12176 (0x2f90) -
25498 (0x639a) -
568 (0x0238) -
514 (0x0202) -
12104 (0x2f48) -
12087 (0x2f37) -
65074 (0xfe32) -
65050 (0xfe1a)
Point formats 1
-
uncompressed
Raw JA3 string
771,4865-4866-4867-4868-4869,43-13-5-10-51-28-18-23-27-65281-11-45-21,583-4585-4589-65053-12103-65048-12092-512-4591-4587-556-65042-571-584-12107-12090-12089-573-572-12215-557-12109-65057-570-25497-65058-65072-12110-12214-558-585-12204-12108-12093-4586-4590-4588-12105-65040-65056-513-65073-12176-25498-568-514-12104-12087-65074-65050,0
Seen in live traffic
- Connections
- 24
- First seen
- 2026-11-16 14:12 UTC
- Last seen
- 2026-11-16 15:33 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 21
The same client, 21 different JA3s
This one JA4 covers 21 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 21 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
574f34ae13c2219ed12405cce703a286522de63f701dcde48021a36855a85fa4fa4b655472e2555fd5dcd6ca89a20ce18d78e9c85ba2d4d95f4f0107ced4a9636aecd73bf3d14ffd4f5946cae06483d3db63500a078e7f3e5bff6a08dd6fb8799dde77b3c2f66986032ed4ca6030dd13b1a3e4319188405cceaff5daa41abff253ddf3f015533069e7129e0918bb36643f90a5f929e35f4121bbd73cc748286e6a27a4f3ad5f8bd6ccb4bcf7e998613950e0b2192a4a5432b7878f511a2f765d- … and 9 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.