HoneyLabs

Akin HTTP request fingerprint

a11cun020_0000000a_4e1a3733

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

1

Source IPs

1

Networks

1

Countries

4

Ports hit

8

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

DE 1

Ports targeted

What it requests

GET/8
Source IPCCNetwork Last seenEvents
178.16.52.10AS0 Omegatech LTD2026-09-238

Related fingerprints

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

a10cun020_0000000a_78f1f19csame header set102 IPs454a11cun020_0000000a_78f1f19csame header set4 IPs37a11cun010_00000008_c4b2c4aa1 header apart341 IPs1.7Ka11cun030_0000004a_c91eaf541 header apart67 IPs216a10cun010_00000008_c4b2c4aa1 header apart18 IPs39a11cun030_0000000e_21fe282e1 header apart3 IPs16a11cuq041_0000020a_bf8a4cbb1 header apart2 IPs2a10cun030_0000004a_c91eaf541 header apart1 IPs1

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.