HoneyLabs

Akin HTTP request fingerprint

a11cuq030_00000608_e62b6d85

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

3

Source IPs

1

Networks

1

Countries

1

Ports hit

3

Events

3

IPs / network

Top networks

Countries

US 3

Ports targeted

What it requests

POST/3
Source IPCCNetwork Last seenEvents
198.235.24.102AS0 Google LLC2026-09-231
205.210.31.59AS0 Google LLC2026-09-231
147.185.132.66AS0 Google LLC2026-09-221

Related fingerprints

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

a11cuq062_00000648_f2f3ae251 header apart2 IPs110a11cuq040_08000608_f46b29fb1 header apart6 IPs6a11cuq040_0000060a_94522fdb1 header apart1 IPs4a11cuq051_00000609_6eb31df91 header apart4 IPs4a11cuq040_0000060a_2daa70d61 header apart3 IPs3a11cuq051_0000060a_f421b8ce1 header apart1 IPs3a11cuq051_00000648_800b45671 header apart2 IPs2a10cuq031_00000600_bfd477e01 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.