JA4 t13d131200_f57a46bbacb6_9249cab70c77

t13d131200_f57a46bbacb6_9249cab70c77

OAI-SearchBot — 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

13

Extensions offered

12

ALPN

none offered

Same tool, different options

These 10 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.

• t13i131100_f57a46bbacb6_9249cab70c77
• t13d1313h2_f57a46bbacb6_9249cab70c77
• t13d1413h1_cbb2034c60b8_9249cab70c77
• t13d1413h2_cbb2034c60b8_9249cab70c77
• t13d1913h2_9dc949149365_9249cab70c77
• t13d251200_b78ed14e2fd0_9249cab70c77
• t13i2512h2_b78ed14e2fd0_9249cab70c77
• t13i191100_9dc949149365_9249cab70c77
• t13i251100_b78ed14e2fd0_9249cab70c77
• t13d191200_9dc949149365_9249cab70c77

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_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

Extensions 12

• server_name
• ec_point_formats
• session_ticket
• renegotiation_info
• extended_master_secret
• signed_certificate_timestamp
• status_request
• supported_groups
• signature_algorithms
• supported_versions
• key_share
• psk_key_exchange_modes

Named groups 5

• SecP256r1MLKEM768
• x25519
• secp256r1
• secp384r1
• secp521r1

Point formats 1

• uncompressed

771,49195-49199-49196-49200-52393-52392-49161-49171-49162-49172-4865-4866-4867,0-11-35-65281-23-18-5-10-13-43-51-45,4588-29-23-24-25,0

Seen in live traffic

Connections

234

First seen

2026-08-25 21:47 UTC

Last seen

2026-09-02 10:41 UTC

Transport

TCP

User-Agents seen on this fingerprint

• Mozilla/5.0 (compatible; OAI-SearchBot/1.4; robots.txt; +https://openai.com/searchbot) 4×
• Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:78.13) Gecko/20100101 Firefox/78.13; compatible; WhatsApp/10.0.2.1 1×
• Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; TelegramBot/1.0 1×
• Mozilla/5.0 (Linux; Android 15; SM-S918B) AppleWebKit/537.36 (KHTML, like Gecko; compatible; ChatGPT-User/1.0; +https://openai.com/bot) Chrome/114.0.790.27 Mobile Safari/537.36 1×
• Mozilla/5.0 (compatible; Bytespider; +https://zhanzhang.toutiao.com/) 1×
• Mozilla/5.0 (compatible; Discordbot/2.0; +https://discordapp.com) 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.