Detect Akamai Web Application Protector
Akamai Web Application Protector is designed for companies looking for a more automated approach to web application firewall (WAF) and distributed denial-of-service (DDoS) security.
Detection looks at script sources, javascript globals across 3 fingerprint rules among the site's public responses.
Websites using Akamai Web Application Protector
Loading website list…
Signal classes
PluginView evaluates public page signals in these classes when identifying Akamai Web Application Protector. Individual fingerprint rule bodies are proprietary and are not published.
- Script sources
- JavaScript globals
Example public indicators for Akamai Web Application Protector
Illustrative indicators derived from public catalog metadata for Akamai Web Application Protector. A live scan may match additional proprietary rules beyond these examples.
- ds-aksb-a.akamaihd.net/aksb.min.js
- aksb.min.js
- AKSB
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Akamai Web Application Protector signature (3 rules) at the time of the scan.
- Does not establish
- A sitewide install of Akamai Web Application Protector, an active vendor contract, exclusive use, or that Akamai Web Application Protector is still in place today.
How to check a site for Akamai Web Application Protector
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Akamai Web Application Protector signals.
- 2. PluginView reads only public responses (script sources, javascript globals) and scores them against the Akamai Web Application Protector signature set (3 rules).
- 3. Review the confidence score and text explanation for Akamai Web Application Protector on the results page.
Commonly implies
A confirmed Akamai Web Application Protector match also implies these technologies are present.
FAQ: detecting Akamai Web Application Protector
- Can PluginView detect Akamai Web Application Protector without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Akamai Web Application Protector — typically script sources, javascript globals. It does not bypass authentication or paywalls.
- What category is Akamai Web Application Protector?
- Akamai Web Application Protector is classified under Security in the PluginView directory.
- How many fingerprint rules cover Akamai Web Application Protector?
- This reference currently tracks 3 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Akamai Web Application Protector?
- Illustrative public indicators for Akamai Web Application Protector include ds-aksb-a.akamaihd.net/aksb.min.js; aksb.min.js; AKSB. A live scan may match additional proprietary rules beyond these examples.
