JA4 Fingerprint Directory

t12d080800_723ebca51f63_cc8988690cb2

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.2

Server name

server name sent

Cipher suites offered

8

Extensions offered

8

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 8

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA

Extensions 8

• server_name
• supported_groups
• ec_point_formats
• signature_algorithms
• signature_algorithms_cert
• extended_master_secret
• supported_versions
• renegotiation_info

Named groups 3

• secp256r1
• secp384r1
• secp521r1

Point formats 1

• uncompressed

771,49196-49195-49199-49171-49172-156-47-53,0-10-11-13-50-23-43-65281,23-24-25,0

Seen in live traffic

Connections

4

First seen

2026-08-24 17:08 UTC

Last seen

2026-08-24 17:10 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.