JA4 t13d0207h2_fffbd61365f3_e2515e582fb5

t13d0207h2_fffbd61365f3_e2515e582fb5

Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

2

Extensions offered

7

ALPN

h2

Same tool, different options

These 8 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.

• t13d0107h2_019185d5a21d_e2515e582fb5
• t13d0107h2_0f2cb44170f4_e2515e582fb5
• t13d0107h2_58070c528ac8_e2515e582fb5
• t13d0107h2_8ecb5bcd8cd8_e2515e582fb5
• t13d0107h2_b870aa68d133_e2515e582fb5
• t13d0107h2_c7f4f146491d_e2515e582fb5
• t13d0107h2_ee47968ec53b_e2515e582fb5
• t13d0707h2_c2f3549b8eb7_e2515e582fb5

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 2

• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_256_GCM_SHA384

Extensions 7

• server_name
• supported_versions
• supported_groups
• key_share
• signature_algorithms
• psk_key_exchange_modes
• application_layer_protocol_negotiation

Named groups 1

• SecP256r1MLKEM768

771,4867-4866,0-43-10-51-13-45-16,4588,

Seen in live traffic

Connections

13

First seen

2026-10-06 13:47 UTC

Last seen

2026-10-06 15:06 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.

• 722596e5ab1ea65390b4cc4fdb46e7f7
• 0c8bb028ea7476fe26f885610d4989b3

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.