Imperva, previously known as Incapsula, sells enterprise bot management and a web application firewall. A classic CAPTCHA is not guaranteed: a suspicious client may get a JavaScript challenge, an "Access denied" page, or a third-party CAPTCHA embedded in the block page. The verdict is based on TLS, IP, cookie and browser signals before any puzzle is shown.
How to identifyLink to How to identify
- Cookies named
visid_incap_*,incap_ses_*,nlbi_*and___utmvc - Requests to
/_Incapsula_Resource?SWJIYLWA=... - A block page mentioning an "Incapsula incident ID" or "Access to this page has been denied"
- A JavaScript challenge that reloads the page after a moment
- A reCAPTCHA, hCaptcha or GeeTest widget inside the block page
- Response headers like
X-IinfoandX-CDN: Incapsula
How it worksLink to How it works
- At the edge, the first request is scored on IP reputation, TLS/JA3 fingerprint, headers and cookies.
- Trusted clients get the page. Doubtful ones get a JavaScript challenge or a block page.
- The challenge script gathers browser signals and sets the
___utmvcandincap_ses_*cookies. - Later requests need that cookie jar. If the score drops, the challenge comes back.
- Some sites stack a visible CAPTCHA (reCAPTCHA, hCaptcha or GeeTest) on top of the JS challenge.
- There is no single token to win. The session itself acts as the credential.
Free & open-source bypass methodsLink to Free & open-source bypass methods
| Tool | What it does | Success Rate | Link |
|---|---|---|---|
| Patchright / Camoufox | Stealth browsers that hide most automation traces | 50–80% | Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox |
| DrissionPage | A real Chromium session that keeps cookies and handles challenges | 45–75% | g1879/DrissionPage |
| SeleniumBase UC mode | Selenium with patches, suited to JS challenges | 45–75% | seleniumbase/SeleniumBase |
| curl_cffi | Mimics browser TLS/JA3 for API-heavy targets | 30–60% | lexiforest/curl_cffi |
| undetected-chromedriver / nodriver | Chrome automation with detection patches | 40–70% | ultrafunkamsterdam/undetected-chromedriver · ultrafunkamsterdam/nodriver |
Practical approachLink to Practical approach
- Work from a persistent, real browser profile and a residential IP in the target's region.
- Open the page and let the challenge script run without blocking it.
- Wait for the reload or for the content to show, then keep the entire cookie jar.
- Carry the same cookies, User-Agent and TLS fingerprint into every following request.
- If a visible CAPTCHA sits in the block page, solve it as usual and stay in that session.
- For API calls, warm the cookies up in a browser first, then replay them through
curl_cffi.
Practical tipsLink to Practical tips
- Imperva judges the whole session. Clearing one challenge does not unlock every path on the site.
- Datacenter IPs and inconsistent TLS fingerprints are turned away before any JavaScript runs.
- A brand-new profile with no history raises suspicion. Reuse a warmed-up profile where possible.
- Blocking analytics or the challenge script usually lowers the score instead of helping.
- Challenge pages and cookie names differ between customers and change over time, so avoid hard-coding a single flow.