Bot protection glossary
Short definitions of the cookies, headers, challenges and endpoints you meet when working against Akamai, DataDome, Incapsula and Kasada bot protection. Each entry links on to the Hyper Solutions guide or docs page that goes deeper.
A
C
D
H
I
R
S
T
U
V
X
_abck cookie
_abck is the main cookie of Akamai Bot Manager. The protected site sets it, and it becomes valid after the browser posts sensor data to the site's Akamai script endpoint. Protected actions such as login, add-to-cart or checkout check it.
CookieRead entry AkamaiAkamai sensor data
Akamai sensor data is the payload that Akamai Bot Manager's client-side script builds in the browser from environment and behavior signals and POSTs to the site's Akamai script endpoint. A valid submission updates the _abck cookie.
ChallengeRead entry GeneralClient hints (sec-ch-ua)
User-agent client hints are HTTP request headers, such as sec-ch-ua, sec-ch-ua-mobile and sec-ch-ua-platform, in which Chromium-based browsers describe their brand, version and platform. Anti-bot systems compare them with the User-Agent; a mismatch is an automation signal.
HeaderRead entry DataDomedatadome cookie
datadome is the cookie DataDome uses to identify a client session. DataDome sets it on the protected site's responses, including block pages, and issues a new value when a challenge is solved or telemetry is accepted. The current value goes with every later request.
CookieRead entry DataDomeDataDome interstitial
The DataDome interstitial is a device-check challenge, which DataDome calls Device Check, served on a 403 block page. It is identified by 'rt':'i' in the page's dd object and a reference to ct.captcha-delivery.com/i.js, and is solved without a captcha.
ChallengeDocs DataDomeDataDome slider captcha
The DataDome slider captcha is a challenge that DataDome serves on a 403 block page. The challenge itself is loaded from geo.captcha-delivery.com under the /captcha/ path. Once it is solved, DataDome issues a new datadome cookie and the blocked request can be retried.
ChallengeRead entry GeneralHAR file
A HAR (HTTP Archive) file is a JSON-formatted recording of HTTP requests and responses, including headers, cookies, bodies and timing. In request-based scraping it is used to compare what your code sends with what a real browser sends.
ConceptRead entry GeneralHeader order
Header order is the exact sequence of HTTP headers, including the HTTP/2 pseudo-headers, that a client sends. Anti-bot systems compare it with real browsers, so it must match the browser exactly.
FingerprintingDocs Incapsula_Incapsula_Resource
/_Incapsula_Resource is a URL path that Imperva Incapsula serves on the protected site's own domain. Its query parameter decides what it returns: a challenge script, the captcha block page shown in an iframe, or the endpoint that accepts a solved challenge.
EndpointRead entry Incapsulareese84
reese84 is the cookie Imperva Incapsula's core bot check uses to mark a session as validated. You post a generated sensor payload to the site's reese84 script path, and the response returns the token you set as the reese84 cookie.
CookieDocs GeneralRequest-based scraping
Request-based scraping fetches pages and APIs with plain HTTP requests instead of running a headless browser. Against bot protection it only works when every request looks like it came from a real browser and the anti-bot challenges are answered with generated payloads.
ConceptRead entry AkamaiSBSD (Akamai)
SBSD (State Based Scraping Detection) is an Akamai Bot Manager check that loads its own script and expects generated sensor payloads. Many sites run it passively next to normal pages; others answer with an SBSD challenge or a 429 until valid payloads arrive.
ChallengeDocs GeneralTLS fingerprinting
TLS fingerprinting identifies an HTTP client by the details of its TLS handshake: the cipher suites, extensions and their order in the ClientHello. Because this happens before any HTTP header is sent, changing the User-Agent does not change the fingerprint.
FingerprintingRead entry Incapsula___utmvc cookie
___utmvc (three underscores) is an Imperva Incapsula cookie produced by the site's /_Incapsula_Resource?SWJIYLWA= challenge script. It is activated by a request to the SWKMTFSR submit path.
CookieDocs KasadaVercel BotID
Vercel BotID is Vercel's bot protection for applications hosted on Vercel. Its Deep Analysis mode is powered by Kasada. Hyper Solutions supports it in all three SDKs.
ChallengeDocs Kasadax-kpsdk-ct and x-kpsdk-cd headers
x-kpsdk-ct and x-kpsdk-cd are request headers used on Kasada-protected sites. x-kpsdk-ct carries a token issued after Kasada's challenge is solved; x-kpsdk-cd carries a proof-of-work value that has to be generated fresh for every request.
HeaderRead entry