t13d030900_55b375c5d22e_4dd7917c528d
Shares its JA4_c (4dd7917c528d) with 1 fingerprint 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
t13d030900
handshake shape, human-readable
55b375c5d22e
truncated hash of the cipher list
4dd7917c528d
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 9
- ALPN
- none offered
Same tool, different options
These 1 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.
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_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_GCM_SHA256
Extensions 9
-
supported_groups -
session_ticket -
encrypt_then_mac -
extended_master_secret -
signature_algorithms -
supported_versions -
psk_key_exchange_modes -
key_share -
server_name
Named groups 1
-
65044 (0xfe14)
Raw JA3 string
771,4866-4867-4865,10-35-22-23-13-43-45-51-0,65044,Seen in live traffic
- Connections
- 385
- First seen
- 2026-11-09 13:35 UTC
- Last seen
- 2026-11-09 13:38 UTC
- Transport
- TCP
- JA3 hashes absorbed
- 149
The same client, 149 different JA3s
This one JA4 covers 149 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 149 unrelated clients. JA4 sorts those lists before hashing, which is why all of it lands here instead.
0ae4433d2f643c59bd9497056bf9b7710ed95b9cad7c57e88a4b6fe87439003b159d8f39b79719e6450c9e68cc6bc9141f6242c6f1ebe64475780abd43d215f827b4ffb3ac0e4eea68f3771421c5511f29c91625bb8a78cddb6c7b0b6e00aadc300fca9a4dc682cacaaa8bb23d153cfe3480c90fe1018bbc89552d87b7f28fe23fd660d79089de5e0f058ec5148c9c19429a14c4d353b1bfcdd327f8c71e6a4a453e22f43eac5a3f1d818c23a806186a45c39c094c4fb7628d116c8f3e7e6dec- … and 137 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.