Phone Number Validation & Carrier Data
Validate a number, identify its country and line type, and name the operator its block is allocated to — with a confidence value and refresh date on every answer
- Validation, line type, and carrier in one call
- Built on official national number allocations
- Confidence and refresh date on every response, porting stated plainly
- Take the allocation table itself, not just the API
Illustrative example, not live data or a coverage metric.
why it holds up
A Carrier Answer You Can Trace
Most phone validation APIs hand back a carrier name and a price per lookup. What they rarely hand back is when the answer was last true, or how confident they are — which is exactly what you need when a number decides whether a message sends, a signup clears, or a payout goes out.
What if every answer told you how sure it is?
Validity and country are decided offline, with no network call. The carrier comes from the official national allocation of number blocks, refreshed on your schedule. Live routing, where it matters, is checked on request.
Three layers, one response — with the confidence and the refresh date attached, so a result you do not believe can be checked rather than argued about.
how a lookup is answered
Three Layers, One Answer
Each layer answers a different question, and each is authoritative for its own. Nothing is inferred from a field it does not own.
Parsing — is it real?
Numbering metadata evaluated offline decides validity, country, calling code, and the E.164 and national formats. No network call, no rate limit, no per-lookup fee.
Allocation — whose block is it?
Every prefix of the national number is tested against the allocated ranges in one indexed query, and the longest match wins. That match carries the operator, the line type, the region, and when it was last refreshed.
Routing — where does it go today?
Live routing records, checked on request. A routing hit survives porting and outranks the allocation, which is why a response tells you when one was found.
coverage
Countries Covered Today
Listed as they actually are, including where a country publishes less than you would like. Adding a country is a contained piece of work, not a rebuild.
France
Mobile, fixed and non-geographic
Every allocated block with its operator and official line type, down to five-digit prefixes for the non-geographic ranges.
United Kingdom
Every number range and sub-block
Every allocated sub-block across all number ranges, normalised into one prefix table with operator and line type.
United States
Code holder per NPA-NXX
Code holder per NPA-NXX. US allocations carry no official line type, and porting is pervasive — treat the result as the code holder rather than the serving carrier.
India
Telecom Circle per mobile MSC code
Every allotted five-digit mobile series with its licensee and Telecom Circle, reconciled across re-allotments and withdrawals. Names the allotted Circle, not the post-MNP operator, and marks unresolved series instead of guessing.
applications
Where a Number Decides Something
Anywhere a phone number gates a decision, the cost of a wrong answer is paid downstream.
Signup & Fraud Screening
Reject impossible numbers before they reach your OTP provider, and flag line types that correlate with abuse — VoIP and non-geographic ranges are visible in the allocation, not guessed at.
SMS & Voice Cost Control
Route and price by line type and operator before you send. Mobile, fixed, premium-rate, and non-geographic blocks carry very different economics, and every block is labelled.
CRM Hygiene
Normalise a contact database to E.164, drop the unreachable, and enrich the rest with country, region, and carrier — as a batch over the whole table, not one paid lookup at a time.
Telecom Analytics
Take the allocation table itself and analyse operator footprint, block utilisation, or numbering-plan change over time. Each sync is retained, so movement between plans is measurable.
KYC & Onboarding Evidence
Attach a dated, confidence-scored validation result to an onboarding record, so a reviewer months later can see what was checked and against what.
Deliverability Monitoring
Correlate failed sends against carrier and block rather than against raw prefixes, and see whether a delivery problem is concentrated in one operator's ranges.
delivery and compliance
Ready for Access Requirements
The details your security, legal, and data teams will ask about before the first dataset changes hands.
No personal data
Numbering plans describe ranges and the operators holding them. No subscribers, no lookups of individuals.
Public data only
Official, publicly available allocation data, dated per record. Nothing behind an authentication wall.
Runs in your stack
Take the allocation table as a dataset and resolve numbers inside your own perimeter, with nothing leaving it.
Any delivery target
API, or JSON, CSV, and Parquet into S3, GCS, Snowflake, or BigQuery on the cadence you set.
questions
Frequently Asked Questions
Everything you need to know before you send us your first request.
How is the carrier determined?
Does it account for number portability?
What does a lookup actually return?
Which countries are covered, and can you add ours?
How fresh is the allocation data?
What does the allocation data contain, and how can I access it?
Still have questions?
Talk to an engineerReady to Get Started?
Talk to us about your sources and volume. We'll return a sample dataset from your target sites before you commit to anything.
