Free tool
Free HLR Lookup
Check phone number format, country, E.164 representation and supported line information with a free HLR lookup-style tool.
To be exact about it: this tool does the numbering work locally. No HLR or carrier data source is wired into it, so it does not report network or line status — what a real HLR lookup would ask a carrier for.
numbering metadata · local · no account
Enter a number
International form, or local with a country.
Check Number
Parsed locally against numbering metadata.
Read the result
Status, country, calling code and formats.
The check runs locally against numbering metadata — no request, no account, no credits. It is not a live HLR/network query.
What is an HLR lookup?
HLR stands for Home Location Register — the register a mobile network uses to track the subscribers it serves. An HLR lookup is a query against network data of that kind: it asks a carrier or an HLR data source about a mobile number rather than reading the number’s formatting.
That distinction is the whole reason this page is explicit about its scope. Numbering metadata can tell you which country a number belongs to and how it should be written; it cannot tell you which network the number is on right now, whether it is in service, or who holds it. Those answers come from carrier data, and this free tool has no such data source.
What does an HLR lookup check?
It depends on the provider and the network. A real HLR lookup queries a data source that holds network information, and what comes back varies by provider, by operator and by country.
Where a provider supports it, a result can carry network or operator information, and in some cases a line status or portability signal. Where it does not, fields are simply absent — a missing field is not a negative answer. This page does none of that: it performs the local numbering check and stops there, with the fields listed further down.
How does HLR lookup work?
Five steps in principle. Step three is the one that needs a data source — and the one this free tool does not perform.
Phone number
A number is supplied, in international form or in local form with a country so the digits can be read against the right plan.
Number normalization
The digits are parsed and normalized against numbering metadata: country, calling code, national number and the formats that follow from them.
Network / HLR data query
This is the step that needs a carrier or HLR data source. It is a separate query to a provider that holds network data — not something a numbering plan can answer.
Carrier or line information
When a provider answers, the result can carry network or operator information, and where supported a line status. Coverage and fields vary by operator and country.
Lookup result
The result is read back against the provider's own documentation. Nothing is inferred from the number's formatting alone.
Steps one, two and five are what this page does. Without a carrier or HLR source there is no step three to run, and inventing its output would be worse than leaving it out.
HLR lookup vs. phone number lookup.
What this free tool returns, beside what a real HLR lookup is for. The two columns are not the same job.
| Information | This free tool | A real HLR lookup |
|---|---|---|
| Number format | Yes | Usually |
| Country | Yes, when determinable | Usually |
| Country calling code | Yes | Usually |
| E.164 representation | Yes, when the number parses | Usually |
| Number type | Where the metadata supports it | Provider dependent |
| Carrier / network | No | Where the provider supports it |
| Network or line status | No | Provider dependent |
| Portability | No | Provider dependent |
| Subscriber identity | No | No |
| Exact location | No | No |
The middle column is this page. The right column describes what an HLR lookup is generally for — and not every provider returns every field in it either.
HLR lookup vs. phone validation.
Three different questions, and it is worth keeping them apart.
- Phone number formatting
- How a number is written: national, international, E.164. It describes representation, nothing about the line.
- Phone validation
- Whether the number follows supported numbering rules, returning a verdict and a reason. Still a statement about the digits.
- HLR / network lookup
- Carrier or network information obtained from an HLR or network data source. A different source, and a different kind of answer.
A formatted number does not automatically mean an active one, and a valid number is not a network status. For a verdict and a reason per number, the phone validation pipeline is the closer answer.
What information can this phone lookup provide?
The honest list for this page: what the numbering tooling in this project can actually derive from a number, and what it cannot.
| Information | Available here |
|---|---|
| Number format validity | Yes |
| Country / region | When determinable |
| Country calling code | Yes |
| International format | When the number parses |
| E.164 format | When the number parses |
| National format | When the number parses |
| National number | When the number parses |
| Number type | When the metadata supports it |
| Carrier / network | No — no such data source is wired up |
| Network or line status | No — a real HLR query would be needed |
| Portability (ported / not ported) | No |
| Subscriber identity | No |
| Exact or GPS location | No |
use cases
Why use an HLR lookup?
Where a network answer is genuinely useful — and, on this page, where the numbering answer has to do instead.
Contact-data cleanup
Normalize and sanity-check the numbers in a dataset before they are used downstream.
Phone-number normalization
Rewrite local numbers into E.164 so a column has one shape rather than many.
Number-type analysis
See where the metadata distinguishes mobile from fixed line, and where it declines to.
Telecom workflows
Route numbers by country and type where a network check is not available or not needed.
Messaging preparation
Get numbers into a consistent form before an SMS workflow — without assuming anything about delivery.
Onboarding checks
Catch malformed or ambiguous numbers at the point someone enters them.
None of this promises that an SMS will be delivered or a call will connect. Those depend on the network, the device and the moment.
Can it show the owner?
No.
An HLR lookup concerns a line and its operator, not a person. Ownership is subscriber data held by the operator, and this tool queries no subscriber records. It is not a reverse-phone-owner database, and it never returns a name.
Can it show a phone’s location?
No.
There is no GPS or precise location data in numbering metadata, and this tool has no network data source either. Nothing here knows where a handset is — only, at most, which country a number belongs to.
HLR lookup limitations.
The edges of HLR data in general, and of this free tool in particular.
- Carrier coverage varies. Network data is not uniformly available across operators, countries or number ranges.
- Network data may not be available for every number, and when a provider has nothing for a number, the answer is often simply missing rather than negative.
- Results depend on the provider and the network involved, so two sources can disagree about the same number.
- A valid number does not necessarily mean an active subscriber. Validity is a statement about the digits.
- Network and line status can change at any time — a number can be disconnected, reassigned or ported after any lookup.
- HLR data does not prove ownership. It describes a line and its operator, not a person.
- HLR data does not provide GPS or exact physical location, and it should not be read as one.
- An HLR lookup does not guarantee SMS or call delivery; delivery depends on the network, the device and the moment.
- Free local parsing is not equivalent to a live HLR query. This tool does the former and says so.
Need a verdict and a reason for a number? Phone Validation runs that pipeline, and its data comes from a provider rather than from the number’s formatting.
Runs in your browser.
This free check parses the number locally against numbering metadata that ships with the page, so no request is made when you press Check Number, nothing is dialled and nothing is sent. That claim is scoped to this tool: the rest of MultiValidator keeps a verification history for dashboard and API use, as the privacy policy describes.
The other phone tools work the same way, and each says so: phone lookup, reverse phone lookup and phone number formats.
HLR lookup FAQ.
What an HLR lookup is, what this free tool actually does, and what neither can tell you.
An HLR lookup queries mobile-network data. HLR stands for Home Location Register — the register a mobile network uses to keep track of the subscribers it serves. A real lookup asks a carrier or HLR data source about a number, and what comes back depends on that source and on the network involved.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.