JA4 t12i060000_be96723b04dc_000000000000

t12i060000_be96723b04dc_000000000000

Seen in live traffic; not in the curated database.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.2

Server name

no server name (IP literal)

Cipher suites offered

6

Extensions offered

0

ALPN

none offered

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.

• t00d170100_bee8bfcd7714_000000000000
• t00d620100_89149463b124_000000000000
• t00d990100_523035705075_000000000000
• t00d990100_896f75462ccc_000000000000
• t10d070100_c50f5591e341_000000000000
• t11d070100_c50f5591e341_000000000000
• t12i100100_61a7ad8aa9b6_000000000000
• t12i990000_43812149fb09_000000000000

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 6

• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384

771,49199-49195-158-52392-4865-4866,,,

Seen in live traffic

Connections

2

First seen

2026-09-01 21:32 UTC

Last seen

2026-09-02 15:52 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.