How a LeadProof list is actually built

What “verified” means, in one paragraph

Every delivered address was checked against the mail server that would receive it, and that server confirmed it would accept mail. Addresses on domains that accept all mail cannot be confirmed either way, so they are excluded from delivery rather than shipped as likely-valid. This is the single claim the whole product rests on, so it is stated in one sentence and documented in full below.

The documents

Google Maps sourcing

Where listings come from, how category matching behaves, and what “fresh” means precisely: /methodology/google-maps-sourcing/

Mailbox verification

The exact rule for what ships, which address we pick, and what a deliverable mailbox does not tell you: /methodology/mailbox-verification/

CRM suppression

How your own export is matched, why domain matching matters, and why the run stops rather than risk duplicates: /methodology/crm-suppression/

What we do not sell

• A LeadProof list says a business exists, is reachable, and matches your filters. It does not say the business is shopping, hiring, or dissatisfied with its current supplier. We sell no intent signal and no technographic data, and any page implying otherwise is wrong. Observed 2026-08-02.
• We deliver the business's published contact address, not a named individual's direct line or personal inbox. If your outreach depends on reaching a specific person by name, this is the wrong product. Observed 2026-08-02.

How we correct mistakes

Every observation we publish carries the date it was made. When one turns out to be wrong, we change the page rather than quietly leaving it up, and the quality policy records what we commit to and what we do not.

Our own bugs are documented alongside the fixes — the vendor-address failure on the verification page is one we shipped, found and closed, and it stays published because a methodology page that only lists successes is marketing.