About

What JailScope is

JailScope is an independent county jail information directory. It connects a location and a jail name to the responsible sheriff, detention, county, or corrections source that publishes available custody information. The goal is simple: help a visitor reach the relevant local source without guessing which agency owns the record.

The directory is built for people looking for a county jail roster, inmate search, booking information, or a verified county contact. It is also designed to make the limits of a result visible instead of presenting a source snapshot as a real-time legal conclusion.

How a county page is built

1. Source review. We identify an official county, sheriff, detention, corrections, or government source and record its URL and source type.
2. Connector testing. A parser or source adapter is checked against representative fixtures before it is enabled for scheduled refreshes.
3. Field normalization. Source fields such as name, booking number, booked date, charges, bond, and custody status are mapped into a consistent page structure when the source provides them.
4. Health checks. Each refresh records whether the source succeeded, is delayed, is stale, is degraded, or has not completed its first successful ingest.
5. Publication. A county page is published only when its source context and available record type can be described clearly.

Source types have different meanings

A JailScope page may represent a current roster snapshot, a recent booking feed, or an official search entry point. These are different source experiences. A page that lists recent bookings does not necessarily represent the entire current population, and an official search link may require a separate lookup on the agency’s system.

The page label, record fields, source status, and last successful sync should be read together. If a source is unavailable or has not refreshed successfully, the page explains that limitation and preserves the last verified context where appropriate.

What we add beyond a source link

• A consistent way to find county pages by state, county, or jail name.
• Normalized labels so similar fields are easier to compare across local systems.
• Freshness and source-status context for time-sensitive roster information.
• Verified contact, address, visitation, bond, or funds details only when an official source supports them.
• Clear warnings when an empty, delayed, or unavailable result cannot answer a custody question.

What JailScope does not claim

JailScope is not a government agency, court, detention operator, law firm, bail service, or records custodian. A booking, charge, or custody entry is not proof of guilt. A missing name or unavailable result does not prove release, transfer, or absence from custody. We do not infer legal outcomes, identity matches, or current status from incomplete source data.

For an urgent, legal, identity-sensitive, bond, visitation, or custody question, contact the responsible county agency or court through its official source. JailScope is a discovery and source-context tool.

Coverage and quality work

Coverage changes as official sources are reviewed and new county pages are verified. We do not imply that the directory includes every county or every record. Scheduled jobs preserve the last successful snapshot when a source temporarily fails, while the page reports the source health so a visitor can distinguish an older snapshot from a successful update.

Source changes, parser failures, and documented corrections are reviewed through the same provenance process used to publish a page. This keeps the directory useful without hiding uncertainty or inventing missing fields.

Corrections and source requests

If a page contains an incorrect source, contact detail, field, or freshness note, send the exact JailScope URL and a direct official source supporting the correction through the Contact page. Agency teams, researchers, and journalists can use the same channel for documented source onboarding or methodology questions.

For information about cookies, technical logs, or privacy requests, see the Privacy Policy and Cookie Policy.