Proxy tier benchmark › Protection systems
Which licensing and registry portals use Imperva Incapsula?
Imperva's signature in this dataset is a tiny HTTP 200. Not a 403, not a challenge page a scraper would notice — a response of a few hundred bytes, with a success status and no readable text, containing a JavaScript bootstrap that a real browser would execute and a plain HTTP client will not.
It is the failure mode that quietly ruins a collection pipeline: no exception, no retry, no alert, and a parser that returns an empty result set for as long as nobody checks.
Portals behind Imperva (Incapsula) in this census
Sixty-one candidate URLs were probed once each from a clean US datacenter IP on 2026-08-18; 1 of the portals below were then measured through all six proxy arms, ten rounds each.
| Portal | Measured in | Behaviour |
|---|---|---|
us_nv_esos |
six-arm run | 212-byte HTTP 200 with zero extractable text on 51 of 60 requests; identical on all six arms including residential |
us_ma_corpweb |
census probe only | HTTP 200, zero characters of text — excluded, robots.txt returned 403 to the benchmark UA and 302 to a browser UA |
us_nursys_lookup |
census probe only | HTTP 200, 83 characters of text — excluded, robots.txt unreadable |
Confirmed from two independent directions
Nursys is the national nurse licence verification system. The census identified
Imperva there from a single probe; separately, BotProxy's production access logs
already show _Incapsula_Resource paths against boardsofnursing.org, from
customer traffic that predates this study. A vendor identification that holds
in a one-shot probe and in a year of unrelated traffic is worth more than either
on its own.
What works
Nothing tested here. Nevada's entity search returned the same 212-byte stub on all six arms — unproxied, both datacenter configurations, both anti-detect configurations and residential. The exit network and the TLS fingerprint were both irrelevant, because the gate is a JavaScript challenge that only a browser executes. That is a Browser API problem, not a proxy tier problem.
Run date: 2026-08-18 · All protection systems · All 32 benchmarked targets · Full report · Census data
Test your own target
The result above describes one URL on one day. Paste your own URL into the live tester and see the real response before creating an account.