Phone Number Validation: Format, Carrier, HLR, MNP and Ownership

What are the layers of phone number validation?

1. 1. Normalize

   Convert Unicode digits and plus signs, separate extensions, and preserve the original input.

   Deterministic

2. 2. Parse

   Resolve country context and split the country code from the national significant number.

   Deterministic when context is known

3. 3. Numbering-plan check

   Check possible length, allocated ranges, and line-type patterns against maintained country data.

   Rules-based and date-sensitive

4. 4. Portability/carrier lookup

   Ask an authorised data source for the current routing network when the use case justifies it.

   Provider-reported and time-sensitive

5. 5. Reachability signal

   Use a permitted network or delivery signal to estimate whether a route can currently accept traffic.

   Operational signal, not certainty

6. 6. Proof of control

   Send a short-lived challenge when the user must demonstrate access to the phone or subscription.

   Transaction-specific evidence

What can HLR and MNP checks tell you?

HLR and HSS are mobile-network data functions described in 3GPP architecture. Commercial lookup services may use network, portability, allocation, or routing data to report fields such as line type, original network, current network, roaming or reachability indicators. The exact fields and meanings depend on the provider, destination market, lawful access, and time of the query.

How should validation results be labelled?

What is a provider-neutral validation workflow?

result = {
  original_input,
  normalized_e164: null,
  syntax: "unknown",
  allocation: "not_checked",
  carrier: null,
  reachability: "not_checked",
  control_verified_at: null,
  warnings: []
}

normalize_and_parse(result)
if country_is_ambiguous: stop_and_request_country()
check_numbering_plan(result)
if use_case_justifies_lookup: query_mnp_or_carrier(result)
if ownership_matters: send_short_lived_challenge(result)
store_each_result_with_source_and_timestamp()

Stop rather than guess when country context is ambiguous or the numbering plan is unsupported. Store the source and timestamp for time-sensitive carrier or reachability results, and set a retention period appropriate to the operational purpose.

How does the workflow change by use case?

A business validation workflow with explicit stop conditions

Choose validation layers from the operational decision, not from the fields a vendor happens to sell. The minimum workflow below keeps deterministic parsing, time-sensitive network evidence and user proof separate.