Submit up to 1,000 phone numbers and have each checked against publicly available directory listings. Built for verifying records you already hold - and constrained by rules you should read before you sign up, not after.
This section sits before the feature list on purpose. Identity data carries obligations that most scraping doesn't, and the restrictions are not negotiable ones we've invented - they're law in the places most of our customers operate.
Do not use this to decide employment, credit, insurance, housing or tenant applications. In the US those are regulated purposes requiring a consumer reporting agency, and this is not one.
Do not use it to find, approach, monitor or contact a private person who has not asked to hear from you. Using data to trace someone is not a grey area and accounts doing it get closed.
Checking whether a number attached to an account you already hold matches public listings is an ordinary data-quality task, and it's what this service is for.
When someone contacts your business and the details look inconsistent, checking the number they gave against public records is a defensive use rather than an investigative one.
If the job you have in mind is on the first list, this is the wrong service and no configuration of it will make that right. If you only need to know whether a number is a mobile and which network runs it - a far more common requirement - use the Phone Numbers Enricher instead. It answers that without touching identity data at all.
The reference and the real output say different things here, and on a service like this the difference matters more than it would anywhere else in the catalogue.
The reference for this endpoint documents the request side - a phone number, up to 1,000 per run - and then defines the response only as far as echoing back the number you submitted. It does not publish a list of the fields a lookup returns.
Real exports do, and the data dictionary below is built from them rather than from the reference: four columns, and a match on 18% of numbers. We have published the columns because they are measured, not guessed - but note what that means in practice. Two of the four are personal details about an identifiable person, and most rows come back without them. Read the permitted uses above before you rely on either.
What that means practically: run a small batch on the free tier - ideally numbers you already know the answers for - and look at the file before you plan anything around it. That costs nothing and tells you exactly what this returns for the countries you care about. Other services here do publish their columns; the Phone Numbers Enricher and Company Insights both list theirs in full.
A small schema, and the honest headline is not the columns but how often two of them are filled.
Most numbers do not match. Across 44 numbers in 26 runs, owner_name and address were filled on 18% of rows - 8 numbers. found is populated on every row precisely so a miss is unambiguous rather than an empty cell you have to guess about. Budget on the assumption that most rows come back with the number and nothing else, and read the permitted-use section above before you plan anything around the ones that do match.
Worth knowing before you budget a run, because it's the difference between a useful export and an empty one.
In our own testing, US numbers returned details while numbers in several other countries did not. That isn't a quirk of one provider - in much of the world, subscriber details for mobile numbers simply aren't public information, so there is no public record for any service to read. Directory-style listings are far more established in the US than in most of Europe or Asia.
The practical consequence: if your list is largely non-US mobile numbers, expect thin results and test before committing spend. If you need coverage of business numbers internationally, a company-level service is the better route - Company Insights returns a company phone from a domain, and Leads & Contacts Enrichment returns numbers with the page each was found on. Both work on organisations rather than individuals, which is a lighter question in every sense.
A phone number is the entire input. There is nothing else to configure.
Numbers work in international form - the documented example is +1 281 236 8208.
Every one of these starts from a record you already hold or an approach someone made to you.
When a new enquiry or order carries details that don't hang together, checking the number given against public listings is a reasonable defensive step. You're validating something volunteered to you, not going looking for a stranger - and that distinction is what keeps the use legitimate.
Databases accumulate numbers whose provenance nobody remembers. Checking a batch you already hold tells you which entries still correspond to a public listing, so you can retire the rest instead of carrying dead records indefinitely.
Two accounts, similar details, one number between them. A public-records check can tell you whether you're looking at one entity or two - a housekeeping question that gets expensive when a CRM is full of near-duplicates.
No subscription, no minimum. Your first 500 rows are on us - and on this service, using them to test coverage first is the sensible move.
Every new account, one-time. No credit card required. Use them to check what this actually returns for your countries before you spend anything - that's the specific advice on this page rather than a generic invitation.
Roughly $2 per 1,000 numbers, one row per number. Bear in mind you pay per lookup regardless of whether a public record exists, which is another reason to test coverage first.
Volume pricing, SLAs and dedicated workers. For this service we'll also want to understand the use case before onboarding - not a formality, given what the data is.
If one of these answers your question, use it instead. Less data about people, better coverage, and no permitted-use analysis required.
Carrier and line type for up to 1,000 numbers, with its three columns published in full. If the question is "can this receive an SMS", this is the answer and it involves no personal data.
Works from a company domain to business contacts - the right tool for reaching people in a professional capacity, with a documented schema and far broader international coverage.
Elsewhere on this site the legal note is short because the answer is easy. Here it isn't, and pretending otherwise would be doing you a disservice.
Reading publicly available directory listings is lawful. That is where the easy part stops. Information identifying a private individual is personal data in every regime that matters, and unlike a business email address there is rarely an obvious legitimate interest in holding it. Under GDPR and similar laws you need a lawful basis to process it at all - not merely to act on it - plus transparency about what you hold and a route for people to have it erased.
In the United States there is a second, sharper line. Using data to decide someone's employment, credit, insurance, housing or tenancy makes it a consumer report, and consumer reports may only be supplied by a consumer reporting agency for a permissible purpose. This service is not one and must not be used that way. That isn't a disclaimer we're hiding in a footer - it's the reason the permitted-use section is at the top of this page.
We will close accounts using this to trace, monitor or approach private individuals. If you're unsure whether your use qualifies, ask us before you run anything - we would genuinely rather have that conversation than take the money.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
Most phone questions are answered better by the Phone Numbers Enricher, with published columns and wider coverage. If you do need public-records checks, talk to us about the use case first - we'd rather get it right than get the order.
The Phone Identity Finder checks phone numbers against publicly available directory listings, accepting up to 1,000 numbers in a single run with a number in international form as the only input. It exists for a narrow set of jobs: confirming that numbers already in your database still correspond to a public listing, sanity-checking details someone volunteered when they contacted your business, and resolving records that may be duplicates of one another. Those uses share a shape - each begins with data you already hold or an approach that was made to you, rather than with an attempt to find a stranger.
Two limitations need stating before anyone signs up, because both affect whether this service is worth buying. The first is that the reference for this endpoint does not publish the fields a lookup returns. It documents the request side and echoes back the number submitted, and stops there. On a firmographics service we would treat a guessed column list as sloppy; on a service dealing in details about identifiable people, publishing a guess would mean advertising specific personal information we cannot confirm you will receive, so this page names no fields at all. The remedy is concrete rather than rhetorical: spend a small part of the one-time 500 free rows on numbers whose answers you already know, and read the file. The second limitation is coverage. In our own testing, US numbers returned details while numbers in several other countries did not, which is less a provider quirk than a fact about the world - subscriber details for mobile numbers are simply not public in much of Europe and Asia, so there is no public record for any service to read. Because you are charged per lookup rather than per result, testing coverage before committing spend is the practical advice.
The compliance position deserves more attention than a footer disclaimer. Reading public listings is lawful, but information identifying a private individual is personal data under GDPR and comparable regimes, and unlike a business email address there is rarely an obvious legitimate interest in holding it. You need a lawful basis to process it at all, not merely to act on it, plus transparency about what you hold and a route for people to have it erased - and those duties sit with you as the controller. In the United States a second and sharper restriction applies: using data to decide someone's employment, credit, insurance, housing or tenancy makes it a consumer report, and consumer reports may only be supplied by a consumer reporting agency for a permissible purpose. This service is not one and must not be used that way. Nor may it be used to trace, monitor or approach private individuals; accounts doing either will be closed.
For most people reading this page, the honest recommendation is a different product. If the question is whether a number can receive an SMS and which network carries it, the Phone Numbers Enricher answers it, publishes all three of its columns, has substantially better international coverage and touches no personal data whatsoever. If you need to reach people in a professional capacity, Leads & Contacts Enrichment works from a company domain to business contacts with a fully documented schema, and Company Insights returns a company phone number from nothing but a domain. Those are lighter questions in every sense - legally, operationally and in what they cost you to get right. If you genuinely do need public-records checks, talk to us about the use case before running anything; we would rather have that conversation than process the order.