Proxy tier benchmark › Protection systems
Which property portals return a JavaScript shell instead of data?
A JavaScript shell is not a block, and treating it as one is a
mistake in both directions. The server answers HTTP 200 with a valid page that
contains navigation, a title and no data; everything a user sees arrives later
from an API call the browser makes. A plain-fetch harness cannot measure such a
target at all, and PROTECTION-CENSUS.md sets the rule accordingly: "it must
be excluded rather than scored".
One target was scored anyway, and it scored 100%.
Portals behind JavaScript shell 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_clark_prop |
six-arm run | 484 characters of text, 7,915 bytes — scored 100% on five of six arms because the assertion Clark County Assessor is in the shell's title element |
us_fl_miamidade_prop |
census probe only | 19 characters of text, title Property Search — excluded from the target list as unmeasurable |
us_hi_search |
census probe only | 249 characters of text, no title — excluded from the target list as unmeasurable |
Clark County should have been excluded
Miami-Dade was dropped at 19 characters of extractable text. Maricopa County's
/mcs/ application was dropped at 259. Clark County, at 484 characters, was
kept and benchmarked, and its probe body reads: "Clark County Assessor Parcel
Detail Various parcel attribute values Parcel History Ownership history Parcel
Sa..." — section headings with no values under them.
Every one of the 60 requests matched the content assertion. No parcel attribute was ever returned. The difference between 259 characters and 484 is not a difference in kind, and the Clark County page says so.
One census row is misfiled here
PROTECTION-CENSUS.md describes Maricopa's /mcs/ response as "a JS shell with
no server-rendered content (259 characters)". The probe's own title column for
that response is Page not found: Maricopa County Assessor's Office. It was
a 404, not a shell. Maricopa was excluded from the run for a different reason
anyway — its robots.txt disallows the path.
What these targets need
A rendered browser, not a proxy tier. See the Browser API. And before that: many county assessors publish the underlying data as a bulk export, which is cheaper than rendering a page per parcel by any measure.
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.