JA4 t12d040400_058957366436_326c0be892b4

t12d040400_058957366436_326c0be892b4

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

4

Extensions offered

4

ALPN

none offered

Same tool, different options

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

• t12d640400_1715b94e3896_326c0be892b4
• t12d640400_1e98fdfb27e9_326c0be892b4
• t12d640400_a3acda31d846_326c0be892b4
• t12d640400_e31a90cd0803_326c0be892b4
• t12d640400_e7b476f9520b_326c0be892b4
• t12d640400_f559eb9565fd_326c0be892b4

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 4

• 49185 (0xc021)
• 49178 (0xc01a)
• 49181 (0xc01d)
• 49184 (0xc020)

Extensions 4

• supported_groups
• server_name
• ec_point_formats
• signature_algorithms

Named groups 5

• secp256r1
• secp384r1
• secp521r1
• x25519
• ffdhe2048

Point formats 1

• uncompressed

771,49185-49178-49181-49184,10-0-11-13,23-24-25-29-256,0

Seen in live traffic

Connections

1

First seen

2026-10-03 09:38 UTC

Last seen

2026-10-03 09:38 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.