How Veriphone identifies the operator behind a phone number with a carrier lookup (sometimes called an HLR lookup) — built on numbering-plan data and national portability registries.
Every valid phone number belongs to a range that a national regulator has allocated to a specific operator. These allocations — published in national numbering plans and consolidated by the International Telecommunication Union (ITU) — are the foundation of carrier identification: from the number range alone, Veriphone can tell which operator a number was originally assigned to, along with its line type and region.
Numbers move, though. With number portability, a subscriber can switch operators and keep their number, so the original assignment can go stale. To answer the question "Which operator serves this number today?", Veriphone consults national portability registries — the authoritative records of every ported number. Veriphone never probes the phone network itself: a lookup sends no signaling traffic and cannot tell you whether a device is switched on or reachable.
How Veriphone Resolves the Carrier
A Veriphone carrier lookup is a single HTTPS request. Under the hood, the API combines two data sources: numbering-plan data, which maps every number range to the operator it was originally assigned to, and national portability registries, which record where ported numbers have moved.
The standard lookup — Static — resolves the original carrier from numbering-plan data. Adding mode=current upgrades the request to a Current lookup, which resolves the carrier currently serving the number from portability registries.
How It Works
1Your application sends a phone number to the Veriphone API at https://api.veriphone.io via HTTPS.
2The number is parsed and normalized to E.164, and its country and number range are identified.
3The range is matched against numbering-plan data to determine validity, line type, region, and the original carrier.
4With mode=current, the number is also checked against national portability registries to resolve the current carrier and report whether it has been ported.
5The API returns this data as a structured JSON response to your application.
Key Point
A carrier lookup is a data lookup, not a network probe. No signaling traffic reaches the carrier and the user's phone never rings or lights up — the process is entirely silent and frictionless. By the same token, the result does not indicate whether the device is switched on or reachable.
What Carrier Data Reveals
A successful carrier lookup returns several critical data points that go far beyond simple "valid or not" checks:
Carrier and Line Type
The operator behind the number, and how the line is classified:
Mobile — cellular subscriber numbers; the right target for SMS
Fixed line — landlines; SMS will not reach them
VoIP — internet-based numbers, a common fraud and disposable-number signal
Special-purpose — toll-free, shared-cost, and premium_rate ranges
Ported Number Detection
By comparing the original carrier (based on the number range) with the current carrier (from portability registries), a Current lookup reveals whether the number has been ported. This is critical for SMS routing, as messages must reach the current carrier, not the original one — and for compliance and fraud checks that depend on knowing the true serving operator.
Static and Current Modes
Every verification includes a Static lookup — the original carrier resolved from numbering-plan data — for 1 credit. Adding mode=current performs a Current lookup, resolving the carrier currently serving the number from national portability registries — ported or not — for 10 credits. See the API reference for request details and Current coverage for the list of supported countries.
Debunking Validation Myths
There are several widespread misconceptions about what phone number validation and carrier lookups can and cannot do. The following table separates fact from fiction:
Myth
Reality
Implication
A valid number means an active user
Numbers stay valid after deactivation/reassignment
Pair carrier lookups with OTP verification for proof of possession
A carrier lookup contacts the phone
Veriphone resolves carriers from numbering-plan data and portability registries — nothing reaches the device
Lookups are silent and frictionless, but say nothing about reachability
The original carrier is always the current carrier
Number portability lets subscribers change operators and keep their number
Use Current lookups when the serving carrier matters, e.g. SMS routing
OTPs make validation unnecessary
OTPs verify immediate possession, not long-term accuracy
Continuous validation needed for database accuracy
Important Limitations
A carrier lookup tells you which operator stands behind a number — it does NOT tell you what is happening on the device. Because Veriphone works from numbering-plan data and portability registries rather than probing the network, the following are out of scope:
Device status — whether the phone is switched on, in coverage, or reachable
SMS delivery — identifying the right carrier improves routing, but delivery is never guaranteed
Account standing — whether the subscriber's account is suspended or barred by the carrier
User identity — who owns or answers the number
Carrier data is authoritative but bounded: portability registries update within hours to days of a porting event, per national regulations, so Current lookups reflect the serving carrier with high fidelity — but they remain carrier intelligence, not device intelligence. To prove the person at the other end is who they claim to be, you need OTP verification.
Key Takeaway
Carrier lookups tell you which operator is behind a phone number — silently, without alerting the user. Use Static lookups to validate and enrich your data at scale, and Current lookups when the serving carrier matters, such as SMS routing or fraud screening. But they cannot prove the person at the other end is who they claim to be. For that, you need OTP verification.