Proxy tier benchmark › Targets
Does the Broward County property appraiser block proxies?
County property records · minimum viable tier: no proxy needed · measured 2026-08-18
No. The Broward County Property Appraiser record page returned the expected content on 10 of 10 unproxied requests (100%), and every proxied configuration scored lower — as low as 50% on a rotating datacenter exit. The site never refused a request; the losses were all proxy-side failures. Measured 2026-08-18.
What was measured
| URL | https://bcpa.net/RecInfo.asp |
| Content assertion | Broward County Property Appraiser |
| 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) | 100% | 352 ms | 375 ms | 24,610 | success 10 |
| datacenter, one pinned exit | 70% | 395 ms | 1,172 ms | 24,610 | success 7, error 3 |
| datacenter, rotating exit | 50% | 381 ms | 10,427 ms | 24,610 | success 5, error 5 |
| anti-detect, one pinned exit | 70% | 2,669 ms | 2,865 ms | 24,610 | success 7, server error 3 |
| anti-detect, rotating exit | 60% | 2,489 ms | 2,928 ms | 24,610 | success 6, server error 4 |
| residential, rotating exit | 90% | 5,670 ms | 11,515 ms | 24,610 | success 9, server error 1 |
What protects this target
None that the run could detect. bcpa.net returned no 403, no
challenge signature and no soft block on any of the 60 requests.
Every failure was ours. The two datacenter arms produced eight
ProxyError transport failures between them, and the two anti-detect arms
produced seven HTTP 502s — errors raised on the proxy hop, before or instead of
a response from Broward. On a target that served 100% of unproxied requests
in a median of 352 ms, routing through a proxy took the pass rate down
to 50% on the worst arm without the target ever saying no.
This is the least flattering result in the study for the product, and it is a straightforward one to read: for this target the proxy is the failure mode.
robots.txt status
The URL measured is allowed by the host's robots.txt.
| Status | allowed |
| File | https://bcpa.net/robots.txt |
| Crawl-delay | not declared |
| Fetched as | the benchmark's own User-Agent |
| Note | robots.txt 30 bytes via benchmark_ua |
Limits of this result
- The record-information page was measured, not a submitted parcel or owner search.
- 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
- Real estate data
- Can you scrape Clark County NV parcel data without a proxy?
- Is the Harris County HCAD property search blocked by Cloudflare?
- Do you need a proxy for King County WA property records?
- 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_fl_broward_prop,' 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.