Proxy tier benchmark › Targets

What blocks the Nevada SilverFlume business entity search?

State business entity registries · minimum viable tier: no tier sufficient · measured 2026-08-18

Imperva (Incapsula), and no tier tested got past it. All 60 requests returned HTTP 200 carrying Imperva's JavaScript bootstrap stub rather than the entity search, giving 0% on all six configurations including residential. Measured 2026-08-18.

What was measured
URL https://esos.nv.gov/EntitySearch/OnlineEntitySearch
Content assertion Entity Search — never verified against a live page
Arms 6
Rounds per arm 10
Requests 60
Measured 2026-08-18, 15:38–18:09 UTC
Benchmark host DigitalOcean droplet, New York (nyc3)

A request counts as a success only if the expected content is present. An HTTP 200 carrying a challenge page, an empty body or the wrong page is a failure, because it is not a page you can use.

This measures whether a tier works, not long-run stability under sustained load. Ten requests per arm, at a two-second floor, never approach a per-IP rate limit — which is the thing a rotating pool exists to defeat.

Results by arm

Arm Success p50 p95 Bytes per success Outcomes
direct (no proxy) 0% 155 ms 319 ms n/a challenge 10
datacenter, one pinned exit 0% 402 ms 999 ms n/a challenge 10
datacenter, rotating exit 0% 378 ms 1,159 ms n/a challenge 10
anti-detect, one pinned exit 0% 426 ms 1,021 ms n/a challenge 10
anti-detect, rotating exit 0% 400 ms 948 ms n/a challenge 10
residential, rotating exit 0% 1,682 ms 2,837 ms n/a challenge 10

What protects this target

Imperva/Incapsula, identified by _Incapsula_Resource in the response body.

Fifty-one of the 60 responses were 212 bytes long, HTTP 200, with zero characters of extractable text in the reconnaissance probe. That is the smallest response in the study, and it is a success by every status-code measure. The remaining responses ranged from 930 to 6,058 bytes — Imperva's escalation path — and none carried the search page.

The identification is confirmed from an independent direction. nursys.com, the national nurse licence verification system, was dropped from this study at the compliance gate; the census notes that BotProxy's own production access logs already show _Incapsula_Resource paths against boardsofnursing.org. Two different licensing and registry systems, the same vendor, seen once in a probe and once in a year of customer traffic.

A 212-byte 200 is the failure mode that quietly ruins a scraper: no exception, no retry, no alert, and a parser that returns an empty result set forever.

robots.txt status

The URL measured is allowed by the host's robots.txt.
Status allowed
File https://esos.nv.gov/robots.txt
Crawl-delay not declared
Fetched as the benchmark's own User-Agent
Note robots.txt 1041 bytes via benchmark_ua

Limits of this result

  • The content assertion was never verified against a live page. It does not affect the result: the Imperva signature is matched in the body independently of the assertion.
  • The search page was measured, not a submitted query.
  • Ten rounds per arm in a single three-hour window on 2026-08-18. Anti-bot behaviour drifts; a result older than a few months is a historical record, not a current one.
  • One exit geography. Every request left from a US datacenter host or a US exit, so nothing here describes how this target answers traffic from elsewhere.
  • The unproxied arm ran from a clean, previously unused cloud IP with no accumulated reputation. It is a best case a production scraper will not sustain.

Run date: 2026-08-18 · Full benchmark report · Harness and raw data · All 32 targets

The 60 rows behind this page are in results/six-arm/raw.csv; filter them with grep '^[^,]*,us_nv_esos,' raw.csv.

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.

Test your target See plans