User-Agent

TelegramBot (like TwitterBot)

first seen 2026-06-17 18:16 · last seen 2026-09-16 18:34 · JSON

Last 7 days (3 observations)

Distinct clients per day (last 30 days, peak 2/day)

Distinct clients are counted by IP-hash per complete UTC day — unlike observation counts this is insensitive to one chatty client, but NAT merges clients and address rotation splits them.

Decomposed attributes

Browser / clientTelegramBot
Device classbot
Noteinferred from the self-declared string — a claim, not a measurement; compare with the wire fingerprints above

Co-observed signals

Signals from other families seen in the same observation. A fingerprint spread thinly across many lower-layer signatures is a classic inconsistency signal.

TLS ClientHello (JA4)

fingerprintco-occurrences
t13d3113h2_e8f1e7e78f70_ce5650b735ce19

HTTP request (JA4H)

fingerprintco-occurrences
ge20cn04enus_91b626dfdddd_a9337a894088_83d3e9453f1518
ge20cn05enus_b807b64f9f29_a9337a894088_83d3e9453f151

HTTP/2 frames (Akamai)

fingerprintco-occurrences
3:100;4:33554432;2:0|33488897|0|m,p,s,a Match?Exact match in Thumbprint's published controlled catalog captures: php-curl 7.88.1.The fingerprint page shows the full measured match list. More on the catalog.19

TCP SYN (p0f)

fingerprintco-occurrences
4:47+17:0:1240:65535,10:mss,sok,ts,nop,ws:df,id+:011
4:53+11:0:1240:65535,10:mss,sok,ts,nop,ws:df,id+:08

TCP SYN (JA4T)

fingerprintco-occurrences
65535_2-4-8-1-3_1240_1018

Country

fingerprintco-occurrences
NL · Netherlands19

Network (ASN)

fingerprintco-occurrences
AS62041 · Telegram Messenger Inc19