t10i150700_0dfbaf47f5cc_e144c465795a
Probe (legacy TLS, no SNI, no ALPN) — inferred from the JA4 handshake shape.
What this fingerprint encodes
t10i150700
handshake shape, human-readable
0dfbaf47f5cc
truncated hash of the cipher list
e144c465795a
truncated hash of extensions + signature algorithms
- Transport
- TCP
- TLS version
- TLS 1.0
- Server name
- no server name (IP literal)
- Cipher suites offered
- 15
- Extensions offered
- 7
- 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.
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.0
Cipher suites 15
-
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA -
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA -
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA -
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA -
TLS_DHE_RSA_WITH_AES_256_CBC_SHA -
56 (0x0038) -
TLS_DHE_RSA_WITH_AES_128_CBC_SHA -
50 (0x0032) -
49157 (0xc005) -
49167 (0xc00f) -
49156 (0xc004) -
49166 (0xc00e) -
TLS_RSA_WITH_AES_256_CBC_SHA -
TLS_RSA_WITH_AES_128_CBC_SHA -
TLS_EMPTY_RENEGOTIATION_INFO_SCSV
Extensions 7
-
status_request -
supported_groups -
ec_point_formats -
status_request_v2 -
extended_master_secret -
session_ticket -
supported_versions
Named groups 10
-
x25519 -
secp256r1 -
secp384r1 -
secp521r1 -
x448 -
ffdhe2048 -
ffdhe3072 -
ffdhe4096 -
259 (0x0103) -
260 (0x0104)
Point formats 1
-
uncompressed
Raw JA3 string
769,49162-49172-49161-49171-57-56-51-50-49157-49167-49156-49166-53-47-255,5-10-11-17-23-35-43,29-23-24-25-30-256-257-258-259-260,0
Seen in live traffic
- Connections
- 1
- First seen
- 2026-09-06 23:30 UTC
- Last seen
- 2026-09-06 23:30 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.