JA4 Fingerprint Directory

t00d1410h2_45de795eb070_4a1f08c76dc1

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

What this fingerprint encodes

Transport

TCP

TLS version

unknown (00)

Server name

server name sent

Cipher suites offered

14

Extensions offered

10

ALPN

h2

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.

• t13d1810h2_29a2cd9e9f10_4a1f08c76dc1

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 14

• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_3DES_EDE_CBC_SHA

Extensions 10

• renegotiation_info
• server_name
• status_request
• supported_groups
• ec_point_formats
• signature_algorithms
• session_ticket
• application_layer_protocol_negotiation
• supported_versions
• key_share

Named groups 6

• x25519
• secp256r1
• secp384r1
• secp521r1
• ffdhe2048
• ffdhe3072

Point formats 1

• uncompressed

771,4865-4867-4866-49195-49199-52393-52392-49196-49200-49171-49172-47-53-10,65281-0-5-10-11-13-35-16-43-51,29-23-24-25-256-257,0

Seen in live traffic

Connections

1

First seen

2026-08-23 18:31 UTC

Last seen

2026-08-23 18:31 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.