---
title: "HLR Lookup Explained: What It Returns and When to Use It"
description: "HLR lookup and number validation explained: what a lookup returns, how it differs from format checks and MNP, use cases, accuracy limits and privacy rules."
canonical: "https://omnichannels.ai/blog/hlr-lookup-number-validation/"
language: "en"
updated: "2026-10-10"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "sms"
primaryQuery: "hlr lookup"
keywords: ["what is hlr lookup", "phone number validation", "mnp lookup", "number portability lookup", "sms list cleaning", "mobile number status check", "hlr lookup accuracy"]
published: "2026-10-09"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 8
answer: "An HLR lookup asks a mobile operator's home location register, the database of its subscribers, about a phone number. Typical results show whether the number is valid and active, which network currently serves it, whether it has been ported and sometimes whether the handset is reachable or roaming. Businesses use it to clean lists, route SMS and screen for fraud, but results vary by country and phone numbers are personal data."
takeaways: ["An HLR lookup is a live network query, unlike format validation, which only checks that a number looks correct, and unlike an MNP lookup, which checks portability databases.", "Typical results include validity, current network (MCC and MNC), ported status and, where the network returns it, reachability and roaming information.", "Accuracy and detail vary by country and operator, because some operators mask, limit or proxy responses, for example through SMS home routing.", "A reachability result is a snapshot: a phone that is switched off is not the same as an invalid number.", "Phone numbers and network status are personal data under laws such as the GDPR, so lookups need a lawful purpose, minimal retention and a reputable provider."]
faq: 
  - q: "What is an HLR lookup?"
    a: "An HLR lookup is a query to the home location register of a mobile number's network. The HLR holds subscriber records used to route calls and SMS. A lookup returns information such as whether the number is valid and active, the network currently serving it and whether it was ported. Lookup providers make these queries through telecom signalling connections and return the results through an API."
  - q: "What is the difference between HLR lookup and number validation?"
    a: "Basic number validation checks format: country code, length and whether the number falls in a mobile range. It is offline, fast and cheap but cannot tell if a number is in use. An HLR lookup queries the network and can indicate whether the number is currently active and which operator serves it. Many teams use format validation everywhere and HLR lookup selectively."
  - q: "How accurate are HLR lookups?"
    a: "Accuracy depends on the destination network and the lookup provider's connectivity. Some operators return full results, while others mask details, return generic answers or route queries through intermediate systems. Reachability can change minutes later. Test a provider on known numbers in your target countries and treat results as strong signals rather than certainties."
  - q: "Is HLR lookup legal under privacy laws?"
    a: "It can be, when done for a legitimate purpose with a reputable provider. Phone numbers relate to identifiable people, so laws such as the EU GDPR and data protection laws in the UAE and Saudi Arabia apply. Define the purpose, request only the fields you need, keep results only as long as necessary and avoid using roaming status to infer location."
  - q: "Does HLR lookup tell me if a number is on WhatsApp?"
    a: "No. An HLR lookup only reflects the mobile network's view of the number, not app registrations. WhatsApp availability is determined by WhatsApp itself when you send messages through the WhatsApp Business Platform. Use delivery status from WhatsApp, and fall back to SMS where a message cannot be delivered."
sources: 
  - title: "3GPP TS 29.002: Mobile Application Part (MAP) specification"
    url: "https://www.3gpp.org/dynareport?code=29002"
  - title: "3GPP TR 23.840: Study into routeing of MT-SMs via the HPLMN"
    url: "https://www.3gpp.org/dynareport?code=23840"
  - title: "Interworking Security — GSMA"
    url: "https://www.gsma.com/solutions-and-impact/technologies/security/cybersecurity-knowledge-base/interworking-security/"
  - title: "Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex"
    url: "https://eur-lex.europa.eu/eli/reg/2016/679/oj"
---

# HLR Lookup Explained: What It Returns and When to Use It

Canonical: https://omnichannels.ai/blog/hlr-lookup-number-validation/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for CRM, messaging and fraud teams who need to know whether phone numbers are real and reachable before sending SMS or approving sign-ups. It explains what an HLR lookup is, what the results mean, where it adds value and where its limits and privacy obligations lie.

## What is an HLR lookup?

An HLR lookup is a query about a mobile number sent to the home location register (HLR), the database a mobile operator uses to hold subscriber records and route calls and SMS. In newer network generations the equivalent function sits in other core-network databases, but "HLR lookup" remains the common commercial name.

Inside the network, SMS delivery depends on this kind of query. The Mobile Application Part (MAP) protocol, defined in 3GPP TS 29.002, includes a service that lets the SMS gateway ask the HLR for the routing information needed to deliver a short message. Commercial lookup services build on telecom signalling access of this kind and return the results to businesses through an API.

## What does an HLR lookup return?

Results vary by provider and destination network, but a typical response includes some or all of the following fields.

| Field | What it tells you | Typical use |
|---|---|---|
| Validity / status | Whether the number is allocated and active | Remove dead numbers |
| Current network (MCC/MNC) | Mobile country and network code of the serving operator | Route and price SMS correctly |
| Original network | The network the number range was first allocated to | Detect porting |
| Ported flag | Whether the number moved to another operator | Correct routing in portability markets |
| Reachability | Whether the subscriber is currently attached or absent | Decide timing; not proof of invalidity |
| Roaming indicator | Whether the number is served by a foreign network | Fraud signals; handle with care for privacy |
| Error or reason code | Unknown subscriber, absent subscriber, barred, and so on | Explain failures |

Some providers also return identifiers such as an IMSI (the SIM's subscriber identity), often truncated. For most business uses you do not need these, and requesting them adds privacy risk.

## How does HLR lookup compare with other checks?

There are three common levels of number checking, and each answers a different question.

| Check | Question answered | How it works | Speed and cost | Main limitation |
|---|---|---|---|---|
| Format validation | Does this look like a valid mobile number? | Offline rules for country code, length and number ranges | Instant, near free | Cannot tell if the number is in use |
| MNP lookup | Which operator owns this number now? | Query of number portability data | Fast, low cost | Does not show if the number is active |
| HLR lookup | Is this number active, and where is it served? | Live query toward the home network | Slower, paid per query | Detail and accuracy vary by network |

A sensible design uses format validation on every input, MNP data where routing depends on the current operator, and HLR lookup where the value of knowing a number's status is higher than the cost of the query.

## When is an HLR lookup worth using?

Use HLR lookups where a wrong or inactive number costs you money, risk or customer experience. Common cases:

### List cleaning before large campaigns

For old or imported lists, a lookup identifies numbers that no longer exist before you pay to message them. Clean lists improve delivery rates and reduce the chance that your sender ID is associated with poor-quality traffic. See [bulk SMS best practices](/blog/bulk-sms-best-practices/) for the rest of list hygiene.

### Routing and pricing

In markets with number portability, the number's prefix no longer reliably shows the operator. Knowing the current network lets providers route to the right operator and lets you estimate costs accurately.

### Fraud and risk checks

At sign-up, a lookup can flag numbers that are unallocated, inactive, or behaving unusually, such as those served by an unexpected network. This helps against fake account creation and SMS pumping; see our [SMS pumping prevention guide](/blog/sms-pumping-fraud-prevention/). Combine it with other signals rather than blocking on one field.

### Data quality in CRM

Periodic checks of key customer numbers can flag records that need updating before an important transactional message, such as a payment reminder, fails.

### When not to use it

- For every OTP send in real time, where the added latency and cost may outweigh the benefit; sending the OTP is itself a test.
- To track individuals' movements through roaming status.
- As a substitute for consent: a valid number does not mean the person agreed to receive marketing.

## What are the limits of HLR lookups?

HLR data is useful but imperfect. Plan for the following:

- **Inconsistent detail by operator.** Some networks return full results; others mask fields, return generic "valid" answers or reject queries.
- **SMS home routing.** Some operators route SMS signalling through a home-network node, an approach studied by 3GPP in TR 23.840, so queries may be answered by that node rather than the HLR, with limited or masked detail.
- **Snapshots, not facts.** "Absent subscriber" may mean the phone is switched off for an hour. Do not delete numbers on one absent result.
- **Recycled numbers.** An active number may now belong to a different person. HLR cannot confirm identity or ownership.
- **Not every number is mobile.** Fixed-line and some virtual numbers may not return HLR results at all.
- **Provider quality varies.** GSMA's interworking security work lists unauthorised HLR lookups among A2P SMS risks operators defend against, so choose providers with legitimate network access.

## What privacy rules apply?

Phone numbers, network status and roaming information relate to identifiable people, so data protection laws apply. In the EU, the GDPR's principles of purpose limitation, data minimisation and storage limitation are directly relevant. The UAE and Saudi Arabia both have personal data protection laws with comparable principles; confirm details with counsel.

### Privacy checklist for HLR lookups

1. **Document the purpose**, for example list cleaning or fraud prevention, and the lawful basis.
2. **Request only the fields you need**; avoid IMSI and roaming detail unless essential.
3. **Set a retention period** for lookup results, separate from the contact record.
4. **Restrict access** to raw lookup data.
5. **Assess your provider**: data processing terms, sub-processors and how it obtains network access.
6. **Mention lookups in your privacy notice** where required.

## Worked example: a Kuwait telecom retailer cleans its list

"Bawaba Mobile" (synthetic) has 300,000 phone numbers collected over several years and plans a reactivation campaign.

- **Format first:** offline validation removes malformed and non-mobile entries at no cost.
- **Lookup selectively:** numbers with no purchase or engagement in recent years receive an HLR lookup; recent active customers do not.
- **Interpretation:** numbers returned as unknown are removed; absent numbers are kept but scheduled for a second check.
- **Privacy:** only status, network and ported flag are requested; results are deleted after the campaign, keeping only a "removed as invalid" marker.
- **Outcome:** the team compares delivery rate and cost per delivered message with its previous campaign to judge whether lookups paid off.

## How OmniChannels.ai helps

OmniChannels.ai runs [SMS campaigns](/channels/sms/) through BroadNet Technologies, a telecom messaging company with SMS operator connectivity. HLR and number lookup is available, so you can check numbers before sending. Campaign uploads from Excel or CSV include duplicate filtering, and delivery reports, with summary and advanced views, filters and CSV export, show which numbers failed and why, giving you data to clean lists over time. Arabic and English are supported. [Contact our team](/contact/) to discuss your use case and integration needs.