HoneyLabs

Akin HTTP request fingerprint

b11cuq093_00050813_59548195_x8e84d668e7f3

Seen 2026-02-18 to 2026-09-30 across the retained window.

The feed is a URL your firewall, MISP or SIEM polls; it needs a free account so it can be revoked. Or watch the top network: AS49870 sends an email when it next hits a sensor.

1

Source IPs

1

Networks

1

Countries

4

Ports hit

3.0K

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

POST/app493
POST/_next492
POST/492
POST/api492
POST/api/route490

User agents claimed

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.01 IPs299
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.361 IPs295
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.1 IPs279
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.361 IPs274
Mozilla/5.0 (Linux; Android 9; AFTWMST22 Build/PS7233; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/88.0.4324.152 Mobile Safari/537.361 IPs270
Source IPCCNetwork Last seenEvents
160.119.71.92SCAS49870 Alsycon B.V.2026-09-303.0K

Related fingerprints

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

b11cuq093_00050813_e9212bf4_x8e84d668e7f3same header set2 IPs14b11cuq071_00050813_aee6d12e_xe7f32 headers apart51 IPs349

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.