JA4 Fingerprint Directory

t13d1312h2_a44d0ee8b3cc_7c86852a3392

Seen in live traffic; not in the curated database.

What this fingerprint encodes

Transport

TCP

TLS version

TLS 1.3

Server name

server name sent

Cipher suites offered

13

Extensions offered

12

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 13

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_3DES_EDE_CBC_SHA

Extensions 12

• server_name
• extended_master_secret
• renegotiation_info
• supported_groups
• ec_point_formats
• session_ticket
• application_layer_protocol_negotiation
• signature_algorithms
• key_share
• psk_key_exchange_modes
• supported_versions
• padding

Named groups 7

• x25519
• secp256r1
• secp384r1
• secp521r1
• SecP256r1MLKEM768
• X25519Kyber768Draft00
• 65074 (0xfe32)

Point formats 1

• uncompressed

771,4865-4866-4867-49195-49196-49199-49200-49171-156-157-47-53-10,0-23-65281-10-11-35-16-13-51-45-43-21,29-23-24-25-4588-25497-65074,0

Seen in live traffic

Connections

5

First seen

2026-08-23 00:14 UTC

Last seen

2026-08-23 02:24 UTC

Transport

TCP

User-Agents seen on this fingerprint

• http://stlweb.dev/wp-admin/install.php?step=1 1×
• http://pqpdf.com/wp-admin/install.php?step=1 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.