q13d0307h3_55b375c5d22e_945b2dc88d6b
Completed a TLS handshake but never an HTTP request, so no User-Agent was ever presented.
What this fingerprint encodes
JA4_a
q13d0307h3
handshake shape, human-readable
JA4_b
55b375c5d22e
truncated hash of the cipher list
JA4_c
945b2dc88d6b
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 3
- Extensions offered
- 7
- ALPN
- h3
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 3
-
TLS_AES_256_GCM_SHA384 -
TLS_AES_128_GCM_SHA256 -
TLS_CHACHA20_POLY1305_SHA256
Extensions 7
-
key_share -
supported_versions -
signature_algorithms -
supported_groups -
server_name -
application_layer_protocol_negotiation -
quic_transport_parameters
Named groups 4
-
secp256r1 -
secp384r1 -
x25519 -
x448
Raw JA3 string
771,4866-4865-4867,51-43-13-10-0-16-57,23-24-29-30,Seen in live traffic
- Connections
- 6
- First seen
- 2026-09-13 03:09 UTC
- Last seen
- 2026-09-13 03:24 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.