County report card · Indiana
Montgomery County, Indiana
County portal uses a JavaScript challenge which deters automated access but may be bypassed by determined actors; its robots.txt also disallows automated access to 14 paths (/prod/court/ViewCaseActors, /prod/in/court/ViewCaseActors, /prod/mi/court/ViewCaseActors…)
- Population
- 38,633
- Portal
- Assessor & Recorder
- Portal vendor
- Schneider Geospatial
What the audit checked
Four low-cost protections every online records portal can have. How we rate counties.
- robots.txtYes — permissive
- Terms of useNot checked
- Bot challengeCloudflare bot detection
- Owner notificationUnknown
Portal audited: beacon.schneidercorp.com/Application.aspx?AppID=200&LayerID=2653&PageTypeID=2&PageID=1504, www.doxpop.com/prod/in/common/ViewCountyDetails?countyId=18107, www.in.gov/dlgf/understanding-your-tax-bill/assessed-value-search/, beacon.schneidercorp.com/?site=MontgomeryCountyIN, www.invoicecloud.com/portal/(S(ebtfikpdjvyq05qo4wjt4p21))/2/customerlocator.aspx?iti=8&bg=0b3648b3-dc85-4da4-9141-7e408a7cd7da&vsii=1&return=Site.aspx%3fG%3de457c8e9-dd69-4932-a778-48945f7ed9c0
Doing well
- Technical barriers (cloudflare) that deter casual bulk access
Room to grow
- Expanding the robots.txt file to disallow automated scrapers
What to ask for
Three low-cost steps that have worked in other counties to close gaps like this one:
1. Adding clear robots.txt rules that disallow automated scrapers
2. Updating the Terms of Use to prohibit automated access
3. Implementing a notification system that alerts residents when their records are accessed
The full playbook is What Counties Can Do.