Proxy tier benchmark › Targets
Why does the Missouri business search fail, and can a proxy get through?
State business entity registries · minimum viable tier: no tier sufficient · measured 2026-08-18
No tier tested reached the page, and each tier failed differently. Unproxied requests hung for 30 seconds and timed out; plain datacenter requests received an HTTP 200 of 4,319 bytes that did not contain the search page; every anti-detect and residential request was refused with HTTP 403. All six arms scored 0%. Measured 2026-08-18.
What was measured
| URL | https://bsd.sos.mo.gov/search/business/businessSearch.aspx |
| Content assertion | Business 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% | 30,123 ms | 30,200 ms | n/a | error 10 |
| datacenter, one pinned exit | 0% | 782 ms | 6,452 ms | n/a | blocked 1, soft block 9 |
| datacenter, rotating exit | 0% | 1,100 ms | 30,133 ms | n/a | blocked 4, soft block 5, error 1 |
| anti-detect, one pinned exit | 0% | 462 ms | 1,131 ms | n/a | blocked 10 |
| anti-detect, rotating exit | 0% | 480 ms | 1,066 ms | n/a | blocked 10 |
| residential, rotating exit | 0% | 1,348 ms | 4,068 ms | n/a | blocked 10 |
What protects this target
Three distinct responses, selected by what the request looks like.
Unproxied: ten ReadTimeout failures at the harness's 30-second ceiling,
zero bytes returned. The tarpit signature PROTECTION-CENSUS.md records against
bsd.sos.mo.gov — the connection is accepted and never answered.
Plain datacenter: fourteen requests returned HTTP 200 with a 4,319-byte body that did not match the content assertion, and five more returned HTTP 403 with a 5,620-byte body. A 4.3 KB response where the search application is expected is almost certainly an interstitial, but that is inference from size: the assertion for this target was never verified against a live page, so "not the search page" is what the data supports and "a block page" is not.
Anti-detect and residential: thirty requests, thirty HTTP 403s, each 6,115 bytes, in a median under half a second. Adding a browser fingerprint moved this target from an ambiguous 200 to an unambiguous refusal.
The ladder runs backwards here. The cheapest proxied configuration got the most content, and every increase in tier — and price — got less.
robots.txt status
The host serves no robots.txt — the request returns HTTP 404. Nothing is disallowed, and nothing is granted either.
| Status | allowed |
| File | https://bsd.sos.mo.gov/robots.txt |
| Crawl-delay | not declared |
| Fetched as | the benchmark's own User-Agent |
| Note | no robots.txt (HTTP 404) |
Limits of this result
- The content assertion was never verified against a live page. The fourteen HTTP 200 responses are recorded as content-assertion failures; whether they are a block page or a page the assertion simply missed cannot be settled from the published data.
- 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.
Related
- Public records scraping
- Why does the Nebraska corporate search time out, and does a proxy fix it?
- Do you need residential proxies for the Arkansas business entity search?
- Does the Colorado business entity search block datacenter proxies?
- Proxy tier benchmark: full report
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_mo_sos_biz,' 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.