JA4 t13d1611h2_e3d26ca8fde7_7b6bd56f487f

t13d1611h2_e3d26ca8fde7_7b6bd56f487f

Go net/http — inferred from the User-Agent on its requests.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

16

Extensions offered

11

ALPN

h2

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 16

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA

Extensions 11

• application_layer_protocol_negotiation
• ec_point_formats
• supported_versions
• server_name
• session_ticket
• signature_algorithms
• psk_key_exchange_modes
• renegotiation_info
• supported_groups
• status_request
• key_share

Named groups 5

• SecP256r1MLKEM768
• x25519
• secp256r1
• secp384r1
• secp521r1

Point formats 1

• uncompressed

771,4866-4867-156-49200-52392-49187-52393-49191-157-49196-49199-10-53-49170-49172-47,16-11-43-0-35-13-45-65281-10-5-51,4588-29-23-24-25,0

Seen in live traffic

Connections

1

First seen

2026-10-04 20:23 UTC

Last seen

2026-10-04 20:23 UTC

Transport

TCP

User-Agents seen on this fingerprint

• Go-http-client/2.0 1×

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.