// vendor intelligence
what kasada detects
kasada is a pow-wall vendor. it declares native attestation (3/3), strong js fingerprint (2/3), strong behavioral (2/3), strong challenge (2/3) capability. below: the layers it enforces and the cookie, endpoint, and header tells it leaves.
catalog data undated speculative
enforced detection layers
| detection layer | capability | what it covers |
|---|---|---|
| tls / network fingerprint | unaddressed | the ja3/ja4 clienthello and http/2 settings signature the edge reads before any javascript runs. |
| ip reputation | unaddressed | asn, proxy-class, and abuse-history scoring of the connecting address. |
| js fingerprint | 2/3 strong | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | 2/3 strong | mouse, keyboard, and timing biometrics read from interaction cadence. |
| challenge | 2/3 strong | interactive or invisible captcha and proof-of-work gates. |
| attestation | 3/3 native | hardware or os-backed integrity checks (webauthn, play integrity, device attestation). |
| server coherence | unaddressed | cross-checking headers, tls, ip, and js for internal consistency. |
unaddressed means this tool type does not operate at that layer, so it is not a failing score. a red 0/3 is a real, declared score of zero. both are declared capability, not live pass-rates.
tells
- cookies
- KP_UIDz
- endpoints
- /149e9513-.../2d206a39.../ips.js
- header tells
- KP_UIDz, x-kpsdk-cd, x-kpsdk-ct
- gate token
- x-kpsdk-cd
ips.js loader solves a managed PoW returning x-kpsdk-ct/x-kpsdk-cd; no captcha - a bad session gets a bare 429 silent drop.
questions
- what does kasada detect?
- it declares native attestation (3/3), strong js fingerprint (2/3), strong behavioral (2/3), strong challenge (2/3) capability. layers not listed are not enforced by kasada.
- what are kasada's tells?
- header/script tells: KP_UIDz, x-kpsdk-cd, x-kpsdk-ct. cookies: KP_UIDz. endpoints: /149e9513-.../2d206a39.../ips.js.
sites defended by this vendor
other vendors
where to go from here
layer intensities are catalog-declared (0..3), speculative, and the catalog carries no capture date for this record. layer definitions in the glossary.