HoneyLabs

Akin HTTP request fingerprint

a11cuq051_0000060a_f421b8ce

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

1

Source IPs

1

Networks

1

Countries

1

Ports hit

3

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

Source IPCCNetwork Last seenEvents
85.90.246.159AS0 Akamai Connected Cloud2026-09-233

Related fingerprints

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

a11cuq040_0000060a_94522fdbsame header set1 IPs4a11cuq040_0000060a_2daa70d6same header set3 IPs3a11cuq061_0000064a_ffe601071 header apart14 IPs25a11cuq050_0000064a_9b8c433a1 header apart3 IPs24a11cuq050_0000060b_650ae0b21 header apart5 IPs5a11cuq030_00000608_e62b6d851 header apart3 IPs3a11cuq041_0000020a_bf8a4cbb1 header apart2 IPs2a10cun020_0000000a_78f1f19c2 headers apart104 IPs456

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.