Solutions › Property & real-estate data
Property data comes from two very different kinds of source, and most pipelines need both: listing portals, which are modern sites behind commercial WAFs, and county assessor, recorder, and land-record systems, which hold the official ownership, valuation, and transfer data but are often older, slower, and hidden behind a challenge page. Rotating datacenter IPs with a browser-like fingerprint and a US exit handle both, because the real obstacle in each case is a per-address request budget and a generic WAF — not serious bot detection.
The government half of this list works exactly like the rest of the public-records world, and the details are on the public records and government registries page. This page covers the property-specific side.
There's no national property database in the United States — there are thousands of county systems. We tested 50 US state and federal public-data URLs from a clean US datacenter IP, and only 36% returned usable content. The blockers were all off-the-shelf products, not custom defenses: Cloudflare challenges (FL, CO, NC, IA, GA), a Cloudflare hard block (UT), Imperva/Incapsula (MA, NV), DataDome (AK), reCAPTCHA (LA), a CloudFront 403 (AR), and plain connection timeouts (NE, MO, TN, WI, OK, OH).
Two failure modes are worth planning for. One state real-estate commission returned HTTP 202 with an empty body — a soft block that any status-code check counts as a success, leaving you with rows that look fine but are empty. And timeouts here are often real: county systems can be genuinely slow rather than hostile, so a short client timeout will create failures that a patient one wouldn't.
Location is checked before fingerprinting. In our test, two state sites served a US datacenter IP normally and returned 403 to a European IP for the same request. Counties are even more restrictive than states. If you're collecting US property data from servers in Europe or Asia, exit from the US — and use a state-level location when the portal is regional:
pxu1000-0+US+county-batch-11
pxu1000-0+us-fl+county-batch-11 # Florida exit for a Florida county systemThe commercial side of property data works like the rest of the modern web: a WAF that checks TLS fingerprints, a per-IP request budget, and content rendered client-side. None of this needs residential IPs — it needs a browser-shaped fingerprint and enough distinct addresses to keep each one under the budget. What it does need is attention to terms of service — listing data is often licensed, and MLS-derived content usually has explicit redistribution rules. Check what you're allowed to store and republish before scaling a crawl, not after.
Rotation doesn't happen automatically. Every request through BotProxy runs inside a session, and a session keeps one exit IP for its lifetime. If you don't set a session ID, a single default session is used and every request goes out from the same address. The session ID is the last field of the proxy login:
login + location + SESSIONID
Change the session ID to change the IP. A session is dropped after 5 minutes of
inactivity, and limit_session_age caps its total lifetime —
60 seconds on most credentials, or 0 for no cap.
What that means for property work:
limit_session_age on the credential you use for them.Anti-Detect Mode rewrites your client's TLS and HTTP/2 handshake to match a real browser. It's what gets past the WAF-based blocking listed above — AWS WAF, Imperva, and Cloudflare fingerprint checks. It's on by default. Because it works as a man-in-the-middle, your client needs to accept the proxy's certificate, and the browser profile supplies the User-Agent, replacing the one your client sends.
County systems are where the web's oldest technology still lives: ASP.NET postback navigation, frames, session-bound pagination, and documents served only as scanned PDFs. Listing portals have the opposite problem — map-driven single-page apps with no server-rendered content at all. Both are handled by the cloud Chrome workers included with every plan: fill the form, page through results, download the document, take a screenshot. Same account, same IP pool, same bill. See the Browser API reference.
Many counties publish assessor and parcel data as downloadable extracts, ArcGIS or Socrata endpoints, or records requests that cost less than a week of engineering. Those files are more complete and more reliable than anything scraped from a search UI. Outside the US, data.gov.uk and OpenStreetMap cover a lot of the same ground. Scrape the counties that don't publish anything, the fields the extract leaves out, and the daily changes a quarterly file can't give you.
Portals behind a Cloudflare managed challenge, anything that requires an agent login or MLS credentials, and data whose license forbids redistribution aren't jobs for a rotating proxy. The rest — slow county systems, WAF interstitials, geo-gates, and per-IP rate limits — is ordinary work.
Paste your URL into the live tester and see the real response before creating an account. Every plan includes all locations, Anti-Detect Mode, and the Browser API. You're billed on traffic volume only.
Test your target See plans Read the documentation
From our published proxy tier benchmark: what each of these targets actually required, measured rather than asserted.
Licensing boards, Secretary of State business registries, county assessors and recorders. About 1,450 separate government domains, each with its own stack and its own WAF.
Company and professional profiles, directories, and firmographic enrichment — long-running pipelines that re-check the same records on a schedule.
Marketplace and retailer product pages, price history, and stock tracking across many sites at once.
Search result pages by keyword and locale, rank monitoring, and share-of-voice reporting for agencies and in-house teams.
Airline and OTA fare and availability checks, where the price depends on the country the request comes from.
Listing portals plus the county assessor, recorder, and land-record sources that hold the official ownership and tax data.
Marketplace listings and product images collected on a schedule to find copies of your products and document them for takedowns.