JA4 t13d311000_8ae6a2f5ac15_7ef8eb972a3c

t13d311000_8ae6a2f5ac15_7ef8eb972a3c

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

31

Extensions offered

10

ALPN

none offered

Same tool, different options

These 1 other fingerprints share this one's JA4_c — the extension and signature-algorithm hash. A client that keeps its extension set constant while varying its cipher list produces exactly this pattern, which is what a scanner iterating cipher suites looks like. A JA3 cannot show you this: its single MD5 collapses ciphers and extensions together, so every variation looks like an unrelated client.

• t13d311000_e8f1e7e78f70_7ef8eb972a3c

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 31

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_256_CCM
• TLS_RSA_WITH_AES_256_CCM
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_128_CCM
• TLS_RSA_WITH_AES_128_CCM
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_ARIA_256_GCM_SHA384
• TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256
• TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV

Extensions 10

• server_name
• ec_point_formats
• supported_groups
• session_ticket
• encrypt_then_mac
• extended_master_secret
• signature_algorithms
• supported_versions
• psk_key_exchange_modes
• key_share

Named groups 5

• x25519
• secp256r1
• x448
• secp521r1
• secp384r1

Point formats 3

• uncompressed
• ansiX962_compressed_prime
• ansiX962_compressed_char2

771,4866-4867-4865-47-49196-49200-49327-49325-49195-49199-49326-49324-49188-49192-49187-49191-49162-49172-49161-49171-157-49313-49309-156-49312-49308-61-60-53-65-255,0-11-10-35-22-23-13-43-45-51,29-23-30-25-24,0-1-2

Seen in live traffic

Connections

96

First seen

2026-08-23 02:04 UTC

Last seen

2026-08-26 01:46 UTC

Transport

TCP

User-Agents seen on this fingerprint

• Mozilla/5.0 (compatible; SemrushBot/7~bl; +http://www.semrush.com/bot.html) 96×

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.