What Is an HLR Lookup? A Guide to Mobile Number Validation

Mobile numbers change constantly. People cancel contracts, change networks, replace SIMs and stop using old numbers. For businesses relying on phone calls or SMS, that means a perfectly good customer database can gradually fill up with numbers that no longer connect. We often see mobile degrading at a rate of 23% per year.

An HLR lookup is a way of checking a mobile number against live network information to help establish whether the number is valid and reachable, without calling the person or sending them a text.

For businesses managing customer, prospect or member data, HLR validation can help identify dead, incorrect or potentially unusable mobile numbers before they create wasted calls, unnecessary SMS costs or unreliable campaign reporting.

If you already have numbers you want to check, Data Soap's HLR lookup service can validate UK and international mobile numbers individually, in bulk or through an API.

HLR lookup in 30 seconds

If you only need the essentials:

• HLR stands for Home Location Register, a term associated with mobile-network subscriber information.

• An HLR lookup checks live mobile-network information rather than relying only on a number's format.

• It can help you establish information such as the network associated with a mobile and whether the handset is currently reported as switched on.

• The lookup happens silently. It does not need to ring the person's phone.

• HLR validation does not prove identity, consent or permission to contact somebody.

• HLR should be treated as one part of a wider phone-data-quality process rather than a complete compliance solution.

• Businesses can run HLR checks in bulk or automatically through an API.

What does HLR mean?

HLR stands for Home Location Register.

Traditionally, the HLR is part of a mobile operator's network infrastructure and stores information required to manage subscribers and their access to mobile services.

It is more accurate to think of mobile operators as maintaining their own subscriber information rather than there being one worldwide HLR containing every mobile subscriber.

Mobile-network architecture has also evolved. Later generations of mobile technology use components such as the Home Subscriber Server, or HSS, while 5G architecture includes newer subscriber-management components such as Unified Data Management, or UDM.

The telecoms industry nevertheless continues to use HLR lookup as a familiar term for live mobile-number validation.

For most businesses, the important distinction is much simpler:

An HLR lookup checks live network information instead of relying entirely on what a mobile number looks like or what an old database says about it.

What is an HLR lookup?

An HLR lookup is a live network query used to obtain information about a mobile telephone number.

With Data Soap, an HLR check can return information including:

• the network name

• Mobile Country Code

• Mobile Network Code

• whether the handset is currently reported as switched on

• a syntax result where appropriate

The lookup happens silently. It does not need to place a telephone call and the handset does not ring.

That distinction matters.

Checking that a number such as 07123 456789 looks like a correctly formatted UK mobile number only tells you that its structure appears valid.

It does not necessarily tell you whether the number currently corresponds to a usable mobile service.

HLR validation goes further by asking the mobile network for current information.

How does an HLR lookup work?

From the user's point of view, the process is straightforward.

1. You submit a mobile number through an online portal, file upload or API.

2. The validation service sends a query to the relevant mobile-network infrastructure.

3. The network returns the information available for that number.

4. The result is returned to your system or included in your cleaned data file.

5. You apply your own business rules to decide whether the number should be used, reviewed or suppressed.

The lookup can take place when cleaning an existing customer database or automatically when somebody enters a mobile number into a website, CRM or application.

Data Soap supports both bulk validation and real-time HLR lookup through an API.

What information can an HLR lookup return?

Exactly what you receive depends on the provider and product being used.

For Data Soap's HLR check, core results can include:

Result	What it tells you
networkName	The mobile network associated with the lookup result
mcc	The Mobile Country Code
mnc	The Mobile Network Code
on	Whether the handset is currently reported as switched on
Syntax result	Formatting and normalisation information that can provide additional context

It is important to separate HLR validation from Mobile Number Portability, or MNP, lookup.

Mobile customers can usually keep their telephone number when moving between networks. That means the network suggested by the original number range is not necessarily the network currently serving the subscriber.

Data Soap therefore offers MNP as a separate validation check.

This distinction avoids a common mistake: assuming the prefix at the beginning of a mobile number always tells you its current network.

How do you interpret an HLR lookup result?

Running the lookup is only half the job.

You also need to decide what the result means for your particular process.

Handset reported as switched on

If the network reports the handset as switched on, that provides a strong current signal that the mobile is active on the network at the point the lookup takes place.

It does not mean the person will answer a phone call or respond to an SMS.

It also does not prove that the person named in your CRM still owns or controls the number.

Network name

The network result can help you understand which mobile network is associated with the result.

This can be useful for reporting, routing and data analysis.

If determining the current network after number portability is specifically important to your process, you should consider an MNP lookup rather than assuming HLR alone answers every portability question.

MCC and MNC

The Mobile Country Code and Mobile Network Code are identifiers used within mobile networks.

Together, they provide technical information about the mobile network associated with the result.

For most marketing or CRM teams these fields may not need manual review, but they can be valuable in automated systems and technical integrations.

Syntax result

A syntax check looks at the structure and formatting of the telephone number.

It can help determine whether the number is correctly formed and can normalise it into a standard format.

This is useful context, but syntax and HLR answer different questions.

A number can be perfectly formatted while still being unusable.

Inconclusive or unavailable live result

Not every live network query will necessarily produce a definitive response.

Network behaviour, routing and operator restrictions can affect what information is available.

An inconclusive result should therefore not automatically be interpreted as meaning the number is dead.

A better approach is to create a business rule for inconclusive results. Depending on your use case, you might retain the number, flag it for review, run another validation method or treat it differently from a clearly negative result.

That distinction is important when cleaning large databases because incorrectly classifying uncertain numbers as invalid can be just as problematic as keeping genuinely bad data.

HLR lookup vs basic phone-number validation

Not every form of telephone validation answers the same question.

A syntax check asks:

"Does this look like a correctly formed telephone number?"

An HLR lookup asks:

"What does the mobile network currently tell us about this number?"

An MNP lookup asks:

"Which network currently serves the number, particularly where portability is relevant?"

For a customer-facing form, a syntax check can catch obvious formatting mistakes quickly.

For an existing marketing, service or sales database, a mobile HLR lookup can provide a stronger indication of whether the mobile data remains usable.

Which telephone validation check do you actually need?

Businesses sometimes use the phrase "phone validation" to describe several different checks.

They are not interchangeable.

If you need to know...	The relevant check
Is this telephone number formatted correctly?	Syntax validation
Does live mobile-network information indicate the mobile is active?	HLR lookup
Which network currently serves a mobile number after portability?	MNP lookup
Is a UK number registered with a marketing preference service?	TPS/CTPS screening
Does this person actually control the mobile number?	OTP or possession verification

This is why the best validation workflow often involves more than one check.

The right combination depends on what you are trying to achieve.

Why do businesses use HLR lookup?

The main reason is simple:

Bad telephone data costs money.

Consider a contact centre with hundreds of thousands of mobile numbers.

If a significant proportion of those records are no longer usable, agents can spend a large part of their working day attempting calls that have little or no chance of connecting.

The same problem applies to SMS.

Sending messages to unusable numbers consumes campaign budget without creating an opportunity for a response or conversion.

HLR validation helps businesses identify potentially problematic mobile data before using it.

Clean an old customer database

Telephone-number data does not remain accurate indefinitely.

Customers change their contact details, contracts end and numbers can eventually be reassigned.

The longer a database has gone without validation or customer updates, the greater the reason to review its contact data before launching a campaign.

Running HLR validation before using an older database helps distinguish stronger records from mobile numbers that may warrant additional review.

Reduce wasted call-centre activity

Dead and incorrect mobile numbers create unnecessary dial attempts.

Cleaning numbers before loading them into a dialler can allow agents to spend a greater proportion of their time dealing with records that have a realistic chance of connecting.

This is particularly valuable for:

• outbound sales teams

• customer-service operations

• debt collection and credit-control teams

• appointment teams

• research organisations

• customer-retention teams

Avoid unnecessary SMS spend

Businesses sending appointment reminders, service notifications or marketing messages normally pay according to message volume.

Checking mobile numbers beforehand can help prevent budget being allocated to data that is already known to be poor quality.

For large SMS databases, even a relatively small improvement in mobile-data quality can have a meaningful operational impact.

Validate numbers at the point of capture

HLR validation does not have to happen months after a number enters your CRM.

A real-time API can check a number when somebody:

• completes a web form

• creates an account

• submits an enquiry

• updates their customer profile

• enters a competition

• requests a callback

Data Soap's API supports HLR as one of the checks that can be requested programmatically.

Point-of-capture validation can be particularly useful because poor data is normally easier to deal with before it spreads into multiple systems.

A sensible mobile-number validation workflow

Rather than expecting one lookup to solve every telephone-data problem, businesses can build validation in stages.

A typical workflow might look like this:

1. Normalise and syntax-check the number

Start by ensuring the number is properly formatted.

For international databases, normalisation into a consistent format such as E.164 also makes later processing easier.

2. Run an HLR lookup

Use HLR to obtain current mobile-network information and identify numbers that appear more or less likely to be usable.

Data Soap's HLR lookup service can be used for individual, bulk and API-driven validation.

3. Run MNP where current network information matters

If your use case depends specifically on understanding the current network after number portability, add MNP validation.

Do not rely solely on the original mobile-number prefix.

4. Apply TPS or CTPS screening where relevant

HLR validation tells you about the mobile number.

It does not tell you whether that number should be contacted for UK direct-marketing purposes.

Where marketing-call compliance is relevant, TPS or CTPS screening may need to form part of the process.

5. Save the validation date and result

Mobile data changes.

Storing the date of the validation alongside the result gives you a better understanding of how fresh the information is.

A number checked yesterday and a number checked three years ago should not necessarily be treated as equally current.

6. Create rules for each result

Decide in advance what happens to:

• positive results

• clearly negative results

• inconclusive results

• syntax failures

• numbers requiring further checks

This allows validation to support operational decisions rather than simply adding another column to a spreadsheet.

How reliable is an HLR lookup?

HLR lookup is more informative than simply examining the syntax or prefix of a mobile number because it uses live mobile-network information.

But it should not be treated as an infallible guarantee.

An HLR result represents information available at or around the point the query is made.

Network conditions, operator restrictions and the way individual mobile networks respond can affect the available result.

That means businesses should think in terms of stronger and weaker data-quality signals, rather than assuming every lookup produces a permanent yes-or-no truth.

For example, a live result today does not guarantee that the same number will remain active indefinitely.

Likewise, an unavailable response should not automatically be treated as proof that the number is invalid.

HLR is therefore most useful when combined with sensible business rules and other forms of data validation where appropriate.

What can't an HLR lookup tell you?

Understanding the limitations of HLR is as important as understanding its benefits.

It cannot tell you who owns the number

HLR validation is not a reverse telephone directory.

It does not return the subscriber's name or prove that a particular person owns the mobile.

It cannot prove somebody controls the number

If you need to establish that a user actually has access to the mobile they entered, you usually need a separate process such as one-time-password verification.

It cannot tell you whether somebody will answer

A mobile can be live without the subscriber answering your call.

HLR checks mobile-network information, not human behaviour.

It cannot guarantee SMS delivery

Successful SMS delivery depends on more than the underlying status of the number.

HLR validation can improve the quality of the numbers you attempt to message, but it does not guarantee every SMS will be delivered.

It does not provide marketing consent

A live mobile number is not automatically a number you have permission to contact for marketing.

Consent, legitimate interests, preference-service screening and other compliance considerations are separate issues.

It does not permanently validate a number

Mobile status can change.

Any HLR result should be treated as a point-in-time data-quality signal rather than a permanent certification.

Common HLR lookup mistakes

Treating every inconclusive result as invalid

No definitive response is not necessarily the same thing as a definitive negative response.

Keep separate categories for invalid, valid/live and inconclusive where your process supports it.

Assuming HLR proves identity

HLR validates mobile-network information.

It does not verify the identity of the person associated with your CRM record.

Assuming HLR provides permission to call

Technical validity and marketing permission are two different things.

TPS, CTPS, PECR, UK GDPR and your lawful basis may still need to be considered depending on the activity.

Using HLR when syntax validation would be enough

Not every telephone-number field requires a live network lookup.

If all you need to know is whether somebody entered a plausibly formatted number, a syntax check may be sufficient.

HLR is most valuable where current network information materially affects the business decision.

Treating the result as permanently valid

Contact data changes.

Consider storing the validation date and deciding when data should be rechecked according to your use case.

Assuming the number prefix reveals the current network

Mobile-number portability means customers can move networks while keeping their number.

Use MNP when determining the current network is specifically important.

Can an HLR lookup tell you who owns a mobile number?

No.

HLR validation should not be treated as a reverse telephone directory.

Its purpose is to validate technical information associated with a mobile service, not to provide the subscriber's name or personal details.

Likewise, an HLR lookup does not prove that the person submitting a number owns or controls it.

If proving possession is important, such as during account registration, you may need a separate verification process such as sending a one-time passcode.

HLR lookup and OTP verification solve different problems.

Does an HLR lookup ring or notify the phone?

No.

The lookup takes place through mobile-network systems rather than by placing a normal telephone call to the subscriber.

The phone does not need to ring.

This makes HLR useful for cleaning an existing database because you can assess mobile-number data before starting the actual customer-contact activity.

Does HLR lookup work with international mobile numbers?

Yes.

HLR validation can be used beyond the UK.

Data Soap supports UK and international mobile validation and can normalise international numbers into a consistent format.

This can be particularly useful for organisations operating across multiple countries because the same validation workflow can be applied to databases containing different country codes and telephone-number formats.

Is an HLR lookup the same as a TPS check?

No.

HLR and TPS answer completely different questions.

An HLR lookup is concerned with the technical status and network information associated with a mobile number.

A Telephone Preference Service check is concerned with whether a telephone number appears on a UK preference register relevant to unsolicited marketing calls.

A live mobile number is not automatically a number that can legally be called for marketing purposes.

Businesses preparing telephone-marketing data may therefore need several checks rather than relying on HLR alone.

Does HLR lookup make your data GDPR compliant?

Not by itself.

This is an important distinction because mobile validation is sometimes described too broadly.

The UK's data-protection accuracy principle requires organisations to take reasonable steps to ensure personal information is not incorrect or misleading and, where necessary for the purpose, to keep it up to date.

HLR validation can form part of a wider data-quality process where accurate mobile information is relevant to the purpose for which the data is being processed.

But an HLR check does not:

• establish your lawful basis for processing

• provide marketing consent

• replace TPS or CTPS screening

• prove that a person owns a telephone number

• make an otherwise unlawful marketing campaign compliant

Think of HLR as a data-quality tool, not a complete compliance solution.

When should you run an HLR lookup?

There is no universal rule stating that every mobile number should be checked after a particular number of months.

The appropriate frequency depends on:

• how the data is being used

• the age of the database

• how regularly customers interact with you

• the cost of failed calls or SMS messages

• how important current contactability is to the process

Useful validation points can include:

• before using an older database

• before a large SMS campaign

• before loading records into a dialler

• when migrating data to a new CRM

• after acquiring or consolidating datasets

• when a number is first submitted

• after repeated contact failures

The aim should be to validate data at the points where accuracy creates genuine operational value rather than applying an arbitrary cleaning schedule.

Bulk HLR lookup or real-time API?

Both approaches use the same basic validation principle but solve different operational problems.

Bulk HLR validation

Bulk validation is useful when you already have an existing file or CRM export containing hundreds, thousands or millions of mobile records.

Typical examples include:

• database-cleaning projects

• pre-campaign preparation

• CRM migrations

• legacy-data reviews

• acquired customer databases

Real-time HLR API

API validation is better when you want mobile numbers checked automatically as they enter or move through your systems.

Typical examples include:

• website forms

• CRM workflows

• customer-registration processes

• lead-generation systems

• internal data-processing platforms

Many organisations use both approaches.

They perform a bulk clean to improve their existing database and then introduce API validation to help reduce the amount of poor-quality data entering the system in future.

Data Soap supports HLR mobile number validation through both bulk processing and real-time API validation.

What should you look for in an HLR lookup provider?

The headline cost per lookup is only one consideration.

You should also look at:

• whether the provider uses live mobile-network queries

• what fields are actually returned

• how inconclusive results are handled

• international coverage

• bulk-processing capacity

• API availability

• documentation quality

• integration options

• data security

• the ability to combine HLR with other validation checks

• how clearly the provider distinguishes between syntax, HLR and MNP

It is particularly important to understand exactly what a provider means by "HLR lookup".

Different services can package mobile validation capabilities differently, and you should avoid assuming every provider returns the same information.

HLR lookup glossary

HLR

Home Location Register. The traditional term for subscriber information maintained within mobile-network infrastructure.

HSS

Home Subscriber Server. A subscriber-management component associated with later mobile-network architecture.

UDM

Unified Data Management. A subscriber-data component used within 5G architecture.

MCC

Mobile Country Code. A code identifying the country associated with a mobile network.

MNC

Mobile Network Code. A code used to identify a mobile network within a country.

MSISDN

A technical term commonly used for a mobile telephone number associated with a subscriber.

MNP

Mobile Number Portability. The ability for a customer to keep their mobile number when moving between networks.

E.164

An international telephone-number formatting standard used to represent numbers consistently with their country code.

HLR lookup frequently asked questions

What does HLR lookup stand for?

HLR stands for Home Location Register.

It is the traditional term associated with subscriber information held within mobile-network infrastructure.

Can an HLR lookup check whether a mobile number is active?

It can obtain live information from the mobile network that provides a stronger indication of current status than examining the number's format alone.

Can I check a mobile number without calling it?

Yes.

An HLR lookup is silent and does not need to place a normal telephone call to the handset.

Can HLR identify the network?

Yes.

An HLR response can include network information such as the network name, MCC and MNC.

Can HLR tell me whether the number has been ported?

Portability is better handled through an MNP lookup.

Data Soap treats HLR and MNP as separate validation checks.

Can I perform HLR lookups in bulk?

Yes.

Mobile numbers can be validated as a list rather than checking every record manually.

Data Soap provides bulk validation as well as API-based validation.

Does HLR lookup work outside the UK?

Yes.

Data Soap supports UK and international mobile-number validation.

Is an HLR result permanent?

No.

Mobile-network status can change, so the result should be treated as a point-in-time validation signal.

Does HLR tell me if I have permission to call somebody?

No.

HLR deals with the technical quality of the mobile number.

Marketing permission and regulatory screening must be considered separately.

Is an inconclusive HLR result the same as an invalid number?

Not necessarily.

An inconclusive result can mean that a definitive live-network answer was not available.

Your process should distinguish inconclusive results from clearly invalid numbers.

Check your mobile numbers with Data Soap

If calls are failing, SMS costs are being wasted or you simply do not know how much of your mobile database is still usable, HLR validation gives you a way to assess the data before you depend on it.

Data Soap's HLR Lookup service supports UK and international mobile validation, with bulk processing and real-time API options.

Use it to identify poor-quality mobile data earlier, improve the quality of the numbers entering your campaigns and give your teams cleaner contact data to work with.