Incapsula bypass, reese84 generated.

An Incapsula bypass without a browser (Incapsula is now sold as Imperva). Takion returns a working reese84 token or ___utmvc cookie from one API call, so your requests clear the challenge and reach the data.

Last updated · Coverage tested against a live Incapsula / Imperva target.

Getting blocked by Incapsula?

Incapsula will not serve you until your request carries the cookie its challenge expects: a reese84 token on sites running the current challenge, or ___utmvc on the classic one. Takion builds it server-side from the live challenge and returns it ready to set. Keep the session cookies your own requests picked up, add the one Takion returns, and Incapsula lets you through.

How Incapsula works

Incapsula runs two challenge families, and a site uses one of them. The classic one loads an obfuscated script from /_Incapsula_Resource and sets the ___utmvc cookie. The current one, reese84, loads its script from a path that is randomized on every delivery, builds an interrogation payload, POSTs it back to that same path, and gets a token that becomes the reese84 cookie (the value starts with 3:). Both are heavily obfuscated and both rotate.

Takion has one endpoint per family. For reese84, /solve takes the site and your proxy, fetches the live challenge itself, and returns the finished token as a ready cookie, with a hint for when to renew it. If you would rather send the final request yourself, /generate returns the payload and the endpoint to POST it to. For ___utmvc, /utmvc takes the challenge script and returns the cookie value plus the validation pings to replay.

Takion does not hand you Imperva's session cookies (incap_ses_*, visid_incap_*, nlbi_*). Your own requests to the site set those. Keep them in your cookie jar, add the cookie Takion returns, and the session is complete.

  • Challenges Takion covers
  • reese84 challenge, on its randomized script path
  • Classic ___utmvc challenge from /_Incapsula_Resource
  • Own-transport mode: the reese84 payload, for you to POST

What one call returns

One call returns the cookie for the challenge the site runs: a reese84 token from /solve, or the ___utmvc value and its validation pings from /utmvc.

reese84

the token, as a ready-to-set cookie, plus when to renew it

___utmvc

the cookie value, plus the validation pings to replay

# reese84: full solve, returns the token
curl -X POST https://incapsula.takionapi.tech/solve \
  -H "x-api-key: $TAKION_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "site": "https://www.example.com", "proxy": "http://user:pass@host:port" }'
# → { "token": "3:...", "cookie": "reese84=3:...", "renew_in_sec": 815, ... }
#
# Own the transport: POST /generate → { "payload": {...}, "endpoint": "..." }
#   then POST the payload as a raw text/plain body to that endpoint, from the same IP.
# Classic ___utmvc: POST /utmvc { "site", "script" } → { "cookie", "value", "validation_pings" }

Read the Incapsula / Imperva docsSame key, every wall. Same JSON shape, every vendor.

How the Incapsula bypass works, end to end

One endpoint per challenge family. No browser, no de-obfuscating Imperva's script by hand.

  1. 1

    You hit the wall

    Instead of the page, Incapsula serves a challenge: the reese84 script, from a path that changes every time, or the classic /_Incapsula_Resource script that sets ___utmvc.

  2. 2

    You call the matching endpoint

    For reese84, send the site and your proxy to /solve. For ___utmvc, send the site and the raw challenge script to /utmvc. One call, no SDK.

  3. 3

    We solve it server-side

    Takion runs what Imperva's obfuscated script would have run. For reese84 it fetches the live script through your proxy and earns the token there, so it is bound to your IP. No headless Chrome anywhere.

  4. 4

    You set the cookie and replay

    Set reese84, or set ___utmvc and replay its validation pings, next to the session cookies you already hold. Send your request again through the same proxy and User-Agent and you are in.

The Incapsula cookies, decoded

Two challenge cookies, the session cookies around them, and the page you see when a check fails:

reese84
the current challenge's cookie. The value starts with 3:, and it is earned by POSTing an interrogation payload to a script path that changes on every delivery
___utmvc
the classic challenge cookie, computed by the obfuscated script at /_Incapsula_Resource
incap_ses_* / visid_incap_*
the session and visitor cookies Imperva sets on your own requests. They tie everything to one session
nlbi_<site id>
load-balancer cookies, like nlbi_2682446 and nlbi_2682446_2147483392, also set by your own requests
Error 15
Imperva's block page: a 403 with an incident ID and error code 15 (codes vary). X-Iinfo is on every response, but a block carries a bot flag like B15(14,0,0) in it, where a clean pass shows q(0 0 0 0)

Why request-based beats a headless browser here

reese84 is heavily obfuscated and it rotates. The browser way to beat it is a fleet of headless Chrome instances, each running Imperva's script, building the payload, and hoping the fingerprint holds. It works until Imperva re-obfuscates, and it costs you a browser farm, constant patching, and seconds per request.

Takion reverses the challenge and builds the payload directly. A solve is one HTTP call instead of a full page render. No Chrome farm to babysit, no Selenium retries when a container dies mid-challenge. You send the site and your proxy, you get the cookie back. Same story for ___utmvc.

What gets an Incapsula session flagged

A valid cookie is necessary, not sufficient. Imperva watches for these the moment you replay:

  • User-Agent drift. The most common failure. Your User-Agent has to be identical on the challenge, the Takion call, and the final request. One mismatch and the token reads as a different client.
  • Changing IP after the solve. The reese84 token is bound to the IP it was earned on. Solve and replay through the same proxy.
  • Proxy or TLS mismatch. Even a valid token fails behind a bad proxy or a mismatched TLS stack. Keep the client consistent and the proxy clean.
  • Treating the payload as the cookie. With /generate, POST the payload to the endpoint we return and set the token the site answers with. Or use /solve and skip that step.
  • Skipping the validation pings. After setting ___utmvc, replay the pings /utmvc returns, or the cookie never validates.
  • Dropping the session cookies. A reese84 or ___utmvc without the incap_ses, visid_incap and nlbi cookies your own requests picked up reads as an incomplete session.

The one rule that kills most 403s

Keep one User-Agent and one proxy across the whole session. Same UA on the challenge, the Takion call, and the final request, through the same clean proxy, and Imperva stays cleared.

Some sites using Incapsula

Incapsula / Imperva guards these sites. Takion clears it on each, so a accor bypass is the same one POST as any other wall.

Accor

reese84 on the login flow

Pokémon Center

reese84, with DataDome layered on top

Incapsula bypass FAQ

Both, with one endpoint each. A site runs one of the two families. reese84 goes to /solve (or /generate), the classic ___utmvc goes to /utmvc. Call the one that matches the challenge you see.
Yes. Incapsula is the original name of Imperva's bot protection, and most developers still call it that. The reese84 and ___utmvc flows are the same whichever name the target uses.
Send the site URL and the proxy you browse through to /solve. Takion fetches the challenge through that proxy, builds the payload, and returns the token, a ready reese84=3:... cookie, and renew_in_sec, which tells you when to refresh it. The token is bound to the IP it was earned on, so keep your traffic on the same proxy.
Use /solve if you just want the cookie. Use /generate if you want to own the transport: it returns the payload and the endpoint. POST the payload as a raw text/plain body to that endpoint from the same IP you generated on, then set the token the site answers with as your reese84 cookie. The payload itself is not the cookie.
Pull the /_Incapsula_Resource script URL out of the page HTML, load the script, and POST its raw JavaScript to /utmvc with the site. We return the ___utmvc cookie and a list of validation pings. Set the cookie, replay the pings, then retry your original request. No browser anywhere in it.
Besides reese84 or ___utmvc, Imperva sets session and visitor cookies on your own requests: incap_ses_*, visid_incap_*, and load-balancer cookies like nlbi_2682446. Takion does not generate those. Keep the ones the site gives you and send them with the cookie Takion returns.
Yes. reese84 rotates, re-obfuscates, and serves its script from a new path on every delivery. /solve works against the live script on each call, so there is no fixed path or old copy for your code to depend on.
Almost always a User-Agent, proxy, or TLS mismatch. The token is bound to the session and IP it was earned on. Use the same User-Agent on the challenge, the Takion call, and the final request, and replay through the same clean proxy with consistent TLS. A valid cookie replayed from a different fingerprint reads as a hijack, and Imperva answers with its block page: a 403 with an incident ID and error code 15 (other codes, like 17, show up too).
Takion is for data you are authorized to reach: your own accounts, public listings, ticket price and availability, sites you have permission to automate. It is not for fraud or abuse, and our acceptable-use policy draws that line. What you do with a cleared session is on you.

Every other wall

Start bypassing Incapsula today.

Start free, no card. One key clears every wall, and your first solve lands within the hour.