Skip to main content
Every protection vendor leaves fingerprints in the traffic: the cookies it sets, the scripts it loads, and the shape of its block page. Record one visit with powhttp, then read the three places below.

Look at the cookies

Open the first response from the site’s own host and read its set-cookie headers. In a mobile app the same Akamai cookies appear on the app’s API host, and protected requests carry an extra header, X-acf-sensor-data, with a long opaque value. That header is the mark of Akamai BMP, the SDK version of Bot Manager.

Look for the script

Akamai Bot Manager loads one script from the site’s own host. Its path looks random, has no file extension, and is usually the last <script> before </body>:
The browser posts to that same path a moment later with a sensor_data body. If you see the pair, the site runs Akamai Web, and the Quickstart is your next stop. Two smaller scripts tell you which extras are on:

Look at the first blocked response

When a request is refused, the response itself names the vendor.

Pick the product

A site can run more than one layer. Solve the sensor first, then add SBSD, Sec-CPT or Pixel only when the recording shows the site uses them.