q13d0115h3_0f2cb44170f4_fb190d169104
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
q13d0115h3
handshake shape, human-readable
0f2cb44170f4
truncated hash of the cipher list
fb190d169104
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 1
- Extensions offered
- 15
- ALPN
- h3
Same tool, different options
These 3 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.
- q13d0215h3_62ed6f6ca7ad_fb190d169104
- q13d0215h3_fffbd61365f3_fb190d169104
- q13d0315h3_55b375c5d22e_fb190d169104
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 1
-
TLS_AES_128_GCM_SHA256
Extensions 15
-
ec_point_formats -
psk_key_exchange_modes -
application_layer_protocol_negotiation -
signature_algorithms_cert -
extended_master_secret -
supported_groups -
quic_transport_parameters -
renegotiation_info -
status_request -
key_share -
signed_certificate_timestamp -
server_name -
signature_algorithms -
supported_versions -
session_ticket
Named groups 4
-
secp521r1 -
secp384r1 -
secp256r1 -
x25519
Point formats 1
-
uncompressed
Raw JA3 string
771,4865,11-45-16-50-23-10-57-65281-5-51-18-0-13-43-35,25-24-23-29,0
Seen in live traffic
- Connections
- 1
- First seen
- 2026-09-13 18:26 UTC
- Last seen
- 2026-09-13 18:26 UTC
- Transport
- QUIC
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.