WellLookupPublic well record intelligence Check an address →
Methodology

Useful context without pretending a map point is certainty.

WellLookup treats public records as evidence, not as a guaranteed parcel-to-well match.

1. Address first

WellLookup geocodes the searched U.S. property and identifies its state. A lookup is only sent to a completed state adapter listed as live in the platform.

2. Query the documented public source

Each live state has its own adapter because agencies expose different APIs, fields, units, record types and location methods. The state source and agency remain visible in the result and on the corresponding state page.

3. Normalize only comparable fields

WellLookup converts compatible depth and distance units for display and maps state-specific fields into a common record shape. If a source field is absent, ambiguous or cannot be normalized responsibly, it is left blank or labeled as source context rather than estimated.

4. Compare nearby records

Nearby wells are sorted by mapped distance from the searched property. Local summaries such as median recorded depth or reported pumping values use only records that contain parseable source values. The Property Report compares multiple radii so one unusually close or unusual record does not silently define the whole area.

5. Keep location uncertainty explicit

Public well coordinates can represent an exact wellhead, a parcel, a geocoded address, a survey location or another approximate point depending on the state and record. Proximity is therefore treated as a research signal—not proof that a well serves the parcel.

6. Separate historical records from current condition

A public well record can describe construction history, reported depth, static water level, pump testing or geology where available. It cannot establish today's water quality, mechanical condition, sustainable household yield or legal status.

7. Preserve the verification path

WellLookup keeps the official state source visible so users can verify material facts. Property decisions should combine the public record with seller documents, well identifiers, current laboratory testing and qualified on-site inspection when appropriate.

State coverage standard

A state is not labeled live as a beta or partial integration. It is added only after the public source is documented, the adapter can return usable records reliably, state-specific limitations are written, and the customer-facing result can be presented without overstating certainty. There are currently 50 completed live state integrations.

Review every official state source →

How public record reviews are prepared

The state guides show dated examples before you submit an address. Maine, Pennsylvania, Colorado and New Hampshire use deliberately selected domestic-record teaching examples with worked interpretations and incomplete entries. Their agency index queries reproduce the particular published fields; Colorado and New Hampshire also link to detail pages checked against the record identifiers. These examples are selected for their research lessons, not to establish an attractive depth, yield or statewide average.

Other state reviews retrieve an existing regional lookup and keep up to the first three distinct public identifiers in returned distance order. Their search center and radius allow the query to be repeated. Both review types retain only allowlisted source fields; residential addresses, owner details and exact well coordinates are excluded. Selection methods are disclosed, missing values are left unknown, and a source zero requires its original meaning to be checked. Neither method establishes a representative statewide sample, expected drilling cost, water quality or the well serving a parcel.

For selected state indexes, separate count queries measure all published layer rows and a stated depth-field condition. Those counts include any repeat filings and non-household record types in that layer. A populated or positive field is not proof that the value is correct. Historical-import counts instead describe the checksum-verified subset documented in the import manifest; import, collection, record and review dates are distinct.

Examples are stored with the site release, so opening a guide does not start a live agency request. A review date remains the original retrieval date until a fresh review succeeds. The free address search queries the configured source or historical snapshot separately. Compare coverage and open the state reviews →

Domestic-led examples and a reproducible audit

Texas and Minnesota now lead with the first two domestic entries from a disclosed ID-ordered convenience sample, followed by one monitoring record to explain exclusion. The six-index field audit retains the exact rows, queries and retrieval dates. It measures the availability of selected numerical fields, not source accuracy or statewide well conditions. Read editorial responsibility, automation and corrections standards.