HoneyLabs

Akin HTTP request fingerprint

a11cun050_0000005b_e6fe1ac3

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

1

Source IPs

1

Networks

1

Countries

2

Ports hit

266

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/255
GET/en/3
GET/main/1
GET/en-de1

User agents claimed

Software Security Research/1.0 (+https://reverse-proxies-measurements.softsec.ruhr-uni-bochum.de)1 IPs266
Source IPCCNetwork Last seenEvents
185.73.23.162DEAS29484 Ruhr-Universitaet Bochum2026-09-23266

Related fingerprints

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

a11cun050_0000005b_09001b3esame header set963 IPs4.4Ka11cun050_0000005b_fda4f7dcsame header set1 IPs146a11cun050_0000005b_d5e10d85same header set11 IPs11a11cun060_0000007b_f55b17ef1 header apart2 IPs3.4Ka11cun040_0000004b_4c87b06e1 header apart113 IPs493a11cun060_0000005f_7d5e642b1 header apart89 IPs463a11cun040_0000004b_00b09b791 header apart1 IPs163a11cun060_0000005f_720361cc1 header apart2 IPs124

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.