HoneyLabs

Akin HTTP request fingerprint

a11cun050_0000004f_16dcd1e4

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

2

Source IPs

2

Networks

2

Countries

1

Ports hit

45

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

BG 1BE 1

Ports targeted

What it requests

User agents claimed

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.362 IPs45
Source IPCCNetwork Last seenEvents
185.218.86.25BGAS218785 Tc Datacenter Limited2026-09-2341
34.140.3.155BEAS396982 Google LLC2026-09-234

Fingerprint family: 2 shapes, 2 IPs, 172 events in 30 days

Every shape here is within one request header of the family's largest shape and comes from the same source addresses. One tool, several request shapes; a hashed fingerprint shows these as unrelated.

HTTP/1.1, 6 headers, no body: accept, connection, accept-encoding, host, accept-language, user-agent

asks for/ · /api/health (GET)
asMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) and 1 more
ports3000 · 80 · 443
fromBG · BE · Tc Datacenter Limited · Google LLC
a11cun060_0000005f_720361ccMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) · /2 IPs127a11cun050_0000004f_16dcd1e4 this one+/- accept-language · Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) · /api/health2 IPs45

Related fingerprints

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

a11cun050_0000004f_0d8a8ff5same header set84 IPs762a11cun050_0000004f_af924659same header set30 IPs248a11cun050_0000004f_90cbaab3same header set56 IPs132a11cun149_0000004f_abf74e9dsame header set7 IPs129a11cun149_0000004f_0366fcaesame header set6 IPs45a11cun050_0000004f_5938b494same header set1 IPs18a11cun050_0000004f_588d51acsame header set1 IPs18a11cun050_0000004f_94db1cf7same header set14 IPs14

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.