HoneyLabs

Akin HTTP request fingerprint

a11cuq070_0000064f_8574b2f3

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

1

Source IPs

1

Networks

1

Countries

1

Ports hit

1

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

SG 1

Ports targeted

What it requests

User agents claimed

python-requests/2.25.11 IPs1
Source IPCCNetwork Last seenEvents
148.66.135.237AS0 GoDaddy.com, LLC2026-09-221

Related fingerprints

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

a11cuq070_0000064f_c865e68fsame header set13 IPs17a11cuq070_0000064f_da0e6e28same header set1 IPs15a11cuq070_0000064f_af8c9b09same header set3 IPs7a11cuq070_0000064f_81cd6514same header set2 IPs2a11cuq070_0000064f_e01bd4b6same header set1 IPs1a11cuq060_0000064b_9e42e2331 header apart2 IPs108a11cuq071_0000064b_0f6de22c1 header apart1 IPs12a11cuq137_0000064e_d10db4251 header apart3 IPs10

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.