[ 01 ]What it looks like
Usually a blank “Request unsuccessful” page that reloads itself, sometimes a captcha widget.
Captcha type · Imperva
Imperva Incapsula captcha solver
Imperva Incapsula challenges solved into reese84 and session cookies you can replay. For the 403 loops that a plain proxy swap never clears.
Also searched asIncapsulareese84 token_Incapsula_Resourceincap_ses cookieDistil Networks
- Price
- $4.49
- per 1,000
- Token acceptance
- 97.0%
- Median solve
- 9.1s
- p95 solve
- 21.8s
[ 02 ]Why it is hard
There is no puzzle to answer. The gate is a reese84 fingerprint token POSTed to a per-site endpoint, plus the incap_ses_* and visid_incap_* cookie pair that comes back with it. The obfuscated sensor script is renamed and re-packed per customer and per deploy, so a payload builder written last month is already stale; it has to be re-derived continuously rather than reverse-engineered once.
[ 03 ]How we solve it
A dedicated Imperva pool tracks the sensor script per site and rebuilds the reese84 payload from the current script you point us at, so a re-obfuscation on their side is a model update on ours, not an outage on yours. The token is generated through your proxy and userAgent because the cookie pair is scored against both. When Imperva escalates to an embedded reCAPTCHA or hCaptcha widget, the task escalates automatically and still returns one usable cookie set.
[ 02 ]Solve it in five lines
Solve it in five lines
Post the task, get the token. Our SDKs collapse creation, polling and retries into one call.
imperva-incapsula.sh
curl -s https://api.nexcaptcha.net/createTask \
-H "Content-Type: application/json" \
-d '{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "IncapsulaTask",
"websiteURL": "...",
"incapsulaScriptUrl": "...",
"userAgent": "...",
"proxy": "..."
}
}'Required parameters
- API task type
- IncapsulaTask
- websiteURL
- required
- incapsulaScriptUrl
- required
- userAgent
- required
- proxy
- required
- Difficulty
- Very hard
[ 03 ]Where this one shows up
Where this one shows up
[ 05 ]Questions about this one
Questions about this one
$4.49 per 1,000 accepted solves, against $2.99 at 2Captcha on the 2026-09-22 benchmark. Failures are not billed. Median 9.1s, p95 21.8s, 97.0% accepted; it sits in the slow tier because the sensor payload is built per request.
Yes. incap_ses_* and visid_incap_* are scored against the IP and user agent that obtained them, so the token has to be earned from the exit you will use. Send the same proxy and userAgent on the task and on every follow-up request.
Yes, one product under three names. Imperva bought Incapsula and later Distil Networks; the current product is Advanced Bot Protection, but the cookie names and the reese84 endpoint still carry the old branding, which is why people search all three.
Because the block is not IP-based. Without a valid reese84 token and the matching session cookies, every fresh IP lands on the same interstitial. You need the token, and the token needs the sensor payload, which is the part we build for you.
Solve your first thousand on us.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.