HoneyLabs

Akin HTTP request fingerprint

a11cun040_0000000f_ac71f7cf

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

1

Source IPs

1

Networks

1

Countries

72

Ports hit

72

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/72
Source IPCCNetwork Last seenEvents
160.119.66.48AS0 Alsycon B.V.2026-09-2372

Related fingerprints

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

a11cun050_0000004f_0d8a8ff51 header apart99 IPs826a11cun050_0000004f_af9246591 header apart32 IPs309a11cun050_0000004f_90cbaab31 header apart82 IPs160a11cun149_0000004f_abf74e9d1 header apart7 IPs129a11cun050_0000004f_16dcd1e41 header apart10 IPs70a11cun149_0000004f_0366fcae1 header apart6 IPs45a11cun050_0000004f_5938b4941 header apart5 IPs22a11cun050_0000004f_588d51ac1 header apart1 IPs21

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.