HoneyLabs

Akin HTTP request fingerprint

a11cun040_0000004d_1d05953d

Seen 2026-09-22 to 2026-09-23 across the retained window.

1

Source IPs

1

Networks

1

Countries

1

Ports hit

2

Events

1

IPs / network

This fingerprint is spread thinly across many networks, which is the shape of a common, widely-used client.

Top networks

Countries

TR 1

Ports targeted

What it requests

User agents claimed

Python/3.12 aiohttp/3.14.31 IPs2
Source IPCCNetwork Last seenEvents
45.93.168.203TRAS48011 Turunc Smart Bilgisayar Teknoloji Ve Dis Ticaret Limited Sirketi2026-09-232

Related fingerprints

Clients whose header set is within two of this one, measured from the tokens themselves.

a11cun040_0000004d_aa48e2c8same header set1.4K IPs9.5Ka11cun040_0000004d_4110f156same header set10 IPs3.0Ka11cun040_0000004d_c2bd490fsame header set29 IPs235a11cun040_0000004d_f36dd82esame header set6 IPs160a11cun040_0000004d_c5bb04c5same header set3 IPs70a11cun051_0000004d_a7cb51b4same header set1 IPs12a11cun051_0000004d_6289c865same header set6 IPs6a11cun062_0000004d_c61c0cf4same header set1 IPs4

About this fingerprint

Akin fingerprints an HTTP client from the request head alone: the protocol version, line endings, body framing, which headers are present, and the grammar of the negotiation header values. The User-Agent string and the request path are deliberately excluded, because both are trivially changed and both were measured varying within a single operator, so a scanner that rotates either keeps one fingerprint. The middle section is a presence bitmap rather than a hash, so two tokens can be compared directly to see how many headers the clients differ by.