Skip to main content
OfflistMe

Broker knowledge base

1,000+ data broker profiles with evidence boundaries

Each profile records the provider route, request workflow, source-check date, identity-verification boundary, registry context when matched, and evidence to keep. Route reachability is not acceptance, delivery, deletion, or a promise that data will not reappear.

Browse the directory →Read the evidence methodology →Download the broker index →Open JSON index →Read the evidence roadmap →View enrichment priorities →Inspect field assessment →View the evidence program →Read the Justdial route guide →Read the Marketo privacy guide →Read the Twilio data guide →Read the Yellowbook route guide →Read the Yasni route guide →Read the InstantPeopleFinder route guide →Read the Reply.io data guide →

What makes OfflistMe different

A self-serve privacy workflow, with the evidence left visible

OfflistMe prepares broker-specific drafts and routes in the browser. You review the details, send or submit the request yourself, save any response, and follow up. That model means no OfflistMe account is required, no government ID is uploaded to OfflistMe, paid plans are one-time rather than recurring subscriptions, and the same paid access can be used by family and friends without an extra platform charge.

No account

Start without creating an OfflistMe account.

No ID upload to OfflistMe

If a broker asks for verification, you decide directly with that provider.

No recurring subscription

Paid access is designed around a one-time pass, not automatic renewal.

Family-friendly access

Share the same paid access with family and friends without an extra platform charge.

These are workflow and pricing distinctions, not a promise that a broker will accept, process, or complete a request. The person making the request remains responsible for reviewing and sending it.

Evidence completeness, precisely stated

All 1043 records have an explicit field state

The captured snapshot assesses 258 tracked fields per record. That gives every record a reviewable known, not-recorded, or unknown state; it does not claim every field is known or that every source was searched.

Open the full assessment →

113,372

Known states

155,653

Not recorded

69

Explicit unknowns

1,043

catalogued broker records

7

data-broker categories

24-hour

page revalidation window

817

records with registry context

0

records with unresolved conflicts

1026

records with open field review

20% authority focus

Start with the profiles where evidence adds the most clarity

Open the first 20% index →Read the evidence roadmap →

The first 209 profiles are ordered by catalog impact, category relevance, documented gaps, and route state. This is a maintenance priority—not a broker-quality ranking, a market-share estimate, or a removal-outcome claim.

209

High-impact profiles

catalog impact signal

209

Workflow sources

profiles with source URLs

187

Registry context

matched official records

207

Open evidence gaps

fields requiring source review

PayNet (Equifax)

Credit, Risk & Identity · entity and source review

Open recorded evidence profile →

The Trade Desk, Inc.

Advertising & Adtech · entity and source review

Open recorded evidence profile →

Quantcast

Advertising & Adtech · entity and source review

Open recorded evidence profile →

Nielsen Consumer LLC (NielsenIQ)

Marketing & Audience Data · route semantics review

Open recorded evidence profile →

Appily

Marketing & Audience Data · entity and source review

Open recorded evidence profile →

Phunware, Inc.

Advertising & Adtech · route semantics review

Open recorded evidence profile →

Nexsales Solutions Inc. (RightLeads)

B2B & Sales Intelligence · entity and source review

Open recorded evidence profile →

Reality Media, Inc.

Advertising & Adtech · entity and source review

Open recorded evidence profile →

Next authority tranche

Continue with the remaining High-impact profiles

View the full evidence roadmap →

The next 68 explicitly High-impact profiles are prioritized by evidence depth, route state, category relevance, and named gaps. This is a maintenance queue—not a ranking, competitor-share estimate, or removal-outcome claim.

16

Advertising & Adtech

9

B2B & Sales Intelligence

29

Marketing & Audience Data

14

Social, Marketplaces & Platforms

Unearth Campaigns LLC

Marketing & Audience Data · current_route_evidenced

Open recorded evidence profile →

Interactive Data, LLC

Marketing & Audience Data · current_email_route_recorded

Open recorded evidence profile →

Complete Mailing Lists LLC

B2B & Sales Intelligence · current_route_evidenced

Open recorded evidence profile →

Dataline, Inc.

Marketing & Audience Data · current_route_evidenced

Open recorded evidence profile →

Tunnl, LLC

Marketing & Audience Data · current_route_evidenced

Open recorded evidence profile →

Unacast

Advertising & Adtech · current_route_evidenced

Open recorded evidence profile →

Demand Science

B2B & Sales Intelligence · current_email_route_recorded

Open recorded evidence profile →

VideoAmp, Inc.

Advertising & Adtech · current_email_route_recorded

Open recorded evidence profile →

Evidence overview

A route map, not a removal promise

The counts below describe the evidence available for routing and research. They deliberately separate first-party or read-only route observations from mailbox acceptance and removal outcomes.

537

Web route checks

read-only URL observations

505

DNS-checked email routes

mailbox not verified

534

Current web evidence

positive route signal

1009

Observed URL routes

468 need route-semantics review

34

Route observation queue

failed URL observations queued for recheck

182,654

Evidence facts

source-linked observations

1043

Verified catalog records

provenance gate; outcomes not inferred

817

Registry context

matched public records

0

Evidence conflicts

kept explicit, not hidden

Deep evidence: 749Useful evidence: 294Basic evidence: 0
Review evidence freshness by category →Review unresolved route evidence →

How to read these labels: a catalog route is the route currently attached to a broker record; a provider-source URL is a first-party page observed for context but not automatically promoted as the submission route; a failed observation is retained and queued for recheck; none of these states proves a request was sent, accepted, completed, or not republished.

Evidence snapshot as of 2026-09-25. Source and route dates are shown on each broker profile; the knowledge base is refreshed on a rolling evidence cadence.

Browse every broker profile

Editorial guides remain available for high-intent brokers; these profiles make the long tail explicit and inspectable.

Generate review-and-send drafts →

Advertising & Adtech

141 profiles

Showing 12 of 141 profiles. View the complete category →

B2B & Sales Intelligence

148 profiles

Showing 12 of 148 profiles. View the complete category →

Credit, Risk & Identity

235 profiles

Showing 12 of 235 profiles. View the complete category →

Marketing & Audience Data

352 profiles

Showing 12 of 352 profiles. View the complete category →

People Search & Public Records

92 profiles

Showing 12 of 92 profiles. View the complete category →

Social, Marketplaces & Platforms

66 profiles

Showing 12 of 66 profiles. View the complete category →

Top German Data brokers

9 profiles

What “source-backed” means here

OfflistMe connects official registries, provider privacy pages, request forms, published contacts, and bounded route observations. A canonical route observation is a positive read-only result for the catalog route. A provider-source URL observation confirms only that a provider-published page was observed; it is not promoted as a submission route until its semantics are reviewed. A failed observation may reflect the observation environment and remains queued for recheck. None of these signals proves that a provider accepted a request, removed a profile, or will not republish information. Users review, submit, save confirmation, verify, and follow up themselves.

Knowledge base FAQ

How many data broker profiles are in the OfflistMe knowledge base?

The current captured catalog contains 1,043 broker profiles. 1043 pass the catalog provenance gate and 1039 pass the bounded evidence-ready gate; 1026 still have open field review. 817 have matched government-registry context, and the coverage dossier contains 182,654 evidence facts. These figures describe documented catalog evidence, not completed removals.

Are all 1,043 broker records fully verified?

No—not fully. All 1039 captured records pass OfflistMe's bounded provenance and route-evidence gate, and explicit approval is required for all 1043. All 1043 records have an explicit state for each of the 258 tracked fields in the captured snapshot, but 17 enrichment field reviews are complete and 1026 remain open.

What does source-backed mean on an OfflistMe broker profile?

A source-backed profile connects provider-published routes, official registry records, published privacy contacts, workflow evidence, or bounded read-only observations to a broker record. A reachable route does not prove request acceptance, delivery, deletion, monitoring, or non-republication.

Does a route check prove that a data broker removed my information?

No. A route check only records what the URL or email-domain observation showed at the stated time. Users must review, send or submit, save confirmation, re-check the source listing, and follow up themselves.

What is the difference between a canonical route observation and a provider-source URL observation?

A canonical route observation is a positive read-only result for the catalog route. The knowledge base now records 471 read-only semantic dispositions for provider-source URLs, but does not promote any page as a submission route until route semantics and entity identity are reviewed. Failed observations remain queued for recheck.