HoneyLabs

Akin HTTP request fingerprint

a11cun040_0000004e_96e5f17b

Seen 2026-09-23 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

SC 1

Ports targeted

What it requests

GET/2

User agents claimed

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.361 IPs2
Source IPCCNetwork Last seenEvents
160.119.71.32SCAS49870 Alsycon B.V.2026-09-232

Related fingerprints

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

a11cun040_0000004e_608dab68same header set443 IPs5.5Ka11cun040_0000004e_36fbce14same header set296 IPs334a11cun040_0000004e_dd8e68f3same header set2 IPs4a11cun117_0000004e_d140c656same header set1 IPs1a11cun040_0000004e_e9e60c84same header set1 IPs1a11cun117_0000004e_d17eaa69same header set1 IPs1a11cun030_0000004c_13ee3d341 header apart1.7K IPs4.0Ka11cun050_0000004f_0d8a8ff51 header apart77 IPs736

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.