t13i030400_55b375c5d22e_7ec14cb91cd4
Probe (no SNI, no ALPN) — inferred from the JA4 handshake shape.
What this fingerprint encodes
t13i030400
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
7ec14cb91cd4
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- no server name (IP literal)
- Cipher suites offered
- 3
- Extensions offered
- 4
- 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 3
-
TLS_AES_128_GCM_SHA256 -
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 4
-
key_share -
supported_groups -
supported_versions -
signature_algorithms
Named groups 3
-
x25519 -
secp256r1 -
secp384r1
Raw JA3 string
771,4865-4866-4867,51-10-43-13,29-23-24,Seen in live traffic
- Connections
- 18
- First seen
- 2026-10-24 01:28 UTC
- Last seen
- 2026-10-26 09:12 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 18
The same client, 18 different JA3s
This one JA4 covers 18 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 18 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
d3e66925f1724a45148577c88a329e6bbcf8730df1e51228e1fa740ebdfa2ccfa0e5730b070b5a57ba9bd7fa5890ccf396dadc6f03f64b3e274edc505672c8cf1ccee73c14d0540b9f2fa27e12b2fb28e4fc77c2492598d854baabb58b58f4a8d31d14dcc7f8121d977e5654c7598ddc7d2872c6eb74336090931aaf57c0174c7ea585ef06e6012537ddf71fa454ac91f195e30223ebc7aa46fdd332b7aa6152f1007d3187557204c28eea7fd7ce0172894fc03d35f09838675b6f54fb9e9870- … and 6 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.