JA4 t13d081400_b8c177e1861e_dea00c3fd0b8

t13d081400_b8c177e1861e_dea00c3fd0b8

Chrome — 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

8

Extensions offered

14

ALPN

none offered

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 8

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• 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_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384

Extensions 14

• server_name
• status_request
• supported_groups
• ec_point_formats
• status_request_v2
• extended_master_secret
• session_ticket
• signature_algorithms
• supported_versions
• psk_key_exchange_modes
• signature_algorithms_cert
• key_share
• renegotiation_info
• pre_shared_key

Named groups 10

• x25519
• secp256r1
• secp384r1
• secp521r1
• x448
• ffdhe2048
• ffdhe3072
• ffdhe4096
• 259 (0x0103)
• 260 (0x0104)

Point formats 1

• uncompressed

771,49196-49195-49199-49200-49171-49172-4865-4866,0-5-10-11-17-23-35-13-43-45-50-51-65281-41,29-23-24-25-30-256-257-258-259-260,0

Seen in live traffic

Connections

7

First seen

2026-09-14 08:37 UTC

Last seen

2026-09-14 08:38 UTC

Transport

TCP

User-Agents seen on this fingerprint

• Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; HubSpot Crawler; +https://www.hubspot.com) Chrome/131.0.0.0 Safari/537.36 7×

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.