Proxy tier benchmark › Targets
Do you need a proxy for King County WA property records?
County property records · minimum viable tier: no proxy needed · measured 2026-08-18
No. King County's eReal Property application returned the expected content on 60 of 60 requests — 100% on all six configurations including unproxied. Measured 2026-08-18.
What was measured
| URL | https://blue.kingcounty.com/assessor/eRealProperty/ |
| Content assertion | eReal Property |
| 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% | 501 ms | 714 ms | 51,816 | success 10 |
| datacenter, one pinned exit | 100% | 1,589 ms | 4,554 ms | 51,816 | success 10 |
| datacenter, rotating exit | 100% | 645 ms | 1,320 ms | 51,816 | success 10 |
| anti-detect, one pinned exit | 100% | 1,614 ms | 4,328 ms | 53,372 | success 10 |
| anti-detect, rotating exit | 100% | 750 ms | 2,824 ms | 53,372 | success 10 |
| residential, rotating exit | 100% | 2,073 ms | 28,006 ms | 53,372 | success 10 |
What protects this target
Nothing. No challenge signature, no 403, no soft block and no transport error across 60 requests.
The number worth carrying away is the latency tail. Unproxied, the 95th percentile was 714 ms. Through a residential exit, on identical content and an identical pass rate, it was 28,006 ms — a thirty-nine-fold penalty bought on a target that refused nothing. Median response times tell the same story more gently: 501 ms against 2,073 ms.
A second, smaller effect shows up in the byte counts, and it is a billing question rather than an access one: the plain arms received 51,816 bytes per page and the fingerprinted arms 53,372. The content assertion matched both.
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://blue.kingcounty.com/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 eReal Property application's entry page was measured, not a submitted parcel search or a parcel detail record.
- 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
- Does the Broward County property appraiser block proxies?
- Can you scrape Clark County NV parcel data without a proxy?
- Is the Harris County HCAD property search blocked by Cloudflare?
- 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_wa_king_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.