q13d0411h3_16476d049b0b_8d0f06507a4e
curl — inferred from the User-Agent on its requests.
What this fingerprint encodes
q13d0411h3
handshake shape, human-readable
16476d049b0b
truncated hash of the cipher list
8d0f06507a4e
truncated hash of extensions + signature algorithms
- Transport
- QUIC
- TLS version
- TLS 1.3
- Server name
- server name sent
- Cipher suites offered
- 4
- Extensions offered
- 11
- 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 4
-
TLS_AES_256_GCM_SHA384 -
TLS_CHACHA20_POLY1305_SHA256 -
TLS_AES_128_GCM_SHA256 -
TLS_EMPTY_RENEGOTIATION_INFO_SCSV
Extensions 11
-
server_name -
supported_groups -
application_layer_protocol_negotiation -
encrypt_then_mac -
extended_master_secret -
post_handshake_auth -
signature_algorithms -
supported_versions -
psk_key_exchange_modes -
key_share -
quic_transport_parameters
Named groups 1
-
SecP256r1MLKEM768
Raw JA3 string
771,4866-4867-4865-255,0-10-16-22-23-49-13-43-45-51-57,4588,Seen in live traffic
- Connections
- 2
- First seen
- 2026-09-09 21:35 UTC
- Last seen
- 2026-09-09 21:35 UTC
- Transport
- QUIC
User-Agents seen on this fingerprint
curl/8.18.0-DEV2×
A User-Agent is self-declared and trivially forged, so this names an observation rather than proving an identity. It is still the strongest signal available: the fingerprint comes off the TLS handshake and the User-Agent off the request that followed, and one client build keeping a stable JA4 while changing what it calls itself is a finding in its own right.
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.