What Really Matters Behind the Numbers
Start with records your team expects to find and review the results against official registry references. Jurisdiction counts and dataset size provide context; finding the expected records is the practical test.
A returned candidate still needs identity and source review. A no-result response should be interpreted in the context of the inputs and available source information.
Jurisdiction Coverage, Record Count, and People Are Different Measures
Coverage describes the registry jurisdictions included in a service. Record count describes entries under the service's counting method. Neither number, on its own, is a verified count of distinct people or a guarantee that every expected record will be returned.
| Measure | What It Tells You | What It Does Not Prove |
|---|---|---|
| Jurisdiction coverage | Which registry jurisdictions the service covers | That every source is available on every request |
| Registry records | The dataset total under the stated counting method | A one-to-one count of distinct people |
| Expected-record results | Whether known records were found in a defined evaluation | Universal accuracy for all inputs and future searches |
What Offenders.io's 184-Jurisdiction Coverage Includes
The published footprint spans all 50 states, Washington, DC, U.S. territories, and tribal registry jurisdictions. These are registry jurisdictions, not 184 states or 184 counties.
Coverage is a platform-level description. A particular source's availability, public fields, and update timing can differ. Review supported search modes and the available record details for your use case. Review Search Modes and Fields.
Why Deduplication Changes Published Record Counts
The same person can have entries in more than one jurisdiction. Adding every entry together can produce a larger total without increasing the number of people that a search can find.
Reasonable deduplication does not turn the published record total into a certified unique-person count. Useful results preserve the source context needed to review overlapping entries.
Why One Person Can Appear in Multiple Registries
The NSOPW FAQ explains that registration obligations can involve jurisdictions where a person lives, works, attends school, or was convicted. It also explains that some jurisdictions keep an entry after a person relocates. This is why overlap needs context rather than simply being labeled an error. NSOPW FAQ.
Coverage, Freshness, and Source Availability Are Separate
Offenders.io standard data is continuously synchronized. Extensive Mode performs live registry lookups where available. Those are different access paths: a platform's nationwide coverage does not mean that every jurisdiction supports every field or every live lookup.
Review the available source references and update context, and use the matching mode documented for your workflow. Results and field availability vary by jurisdiction and source. Review Search Modes and Fields.
A Practical Coverage Evaluation Checklist
Evaluate the result you need, not just the largest published number.
- Identify the jurisdictions and search inputs your workflow needs.
- Check records you are authorized to review and inspect possible matches against official source references.
- Review overlapping entries, missing fields, and source availability in context.
- Confirm the documented search mode, service commitment, and access requirements before production use.
For the broader selection criteria, read Why Offenders.io Is the Best Sex Offender API.
Sex Offender API Coverage FAQ
Does nationwide coverage mean every field is available everywhere?
No. Public fields, source availability, and update timing differ by jurisdiction. Review the available record details and the documented search mode rather than assuming identical data from every source.
Does 900K+ records mean 900K+ distinct people?
The published figure is a registry-record count after reasonable cross-jurisdiction deduplication, not a certified distinct-person count. People can have records in multiple jurisdictions.
Does a no-result response prove someone has no registry record?
No. Interpret it alongside the supplied identifiers, matching mode, and source information available to the search. Investigate expected missing records with the relevant official registry.
Coverage Is Context. Expected Records Are the Test.
Use Offenders.io Search to evaluate the records and jurisdictions that matter to your team, and use official references to review the results.
Explore Offenders.io SearchRead the API Buyer Guide