JA4 t13d020800_62ed6f6ca7ad_81ef6f8817e6

t13d020800_62ed6f6ca7ad_81ef6f8817e6

Shares its JA4_c (81ef6f8817e6) 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

Transport

TCP

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

2

Extensions offered

8

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.

• t13i030700_55b375c5d22e_81ef6f8817e6

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_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384

Extensions 8

• server_name
• status_request
• supported_groups
• signature_algorithms
• supported_versions
• psk_key_exchange_modes
• signature_algorithms_cert
• key_share

Named groups 10

• x25519
• secp256r1
• secp384r1
• secp521r1
• x448
• ffdhe2048
• ffdhe3072
• ffdhe4096
• 259 (0x0103)
• 260 (0x0104)

771,4865-4866,0-5-10-13-43-45-50-51,29-23-24-25-30-256-257-258-259-260,

Seen in live traffic

Connections

4

First seen

2026-10-21 01:14 UTC

Last seen

2026-10-21 01:14 UTC

Transport

TCP

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.