Number Lookup separates free basic analysis from the optional paid HLR action. Start with the intended number, review the quoted charge and confirm only when the available network information answers your question. An HLR result is not identity verification or a delivery guarantee.
These instructions follow the Android app version 1.0.46, build 272. Available actions depend on your account permissions and current service state. Other installed versions may present different controls.
1. Analyze the intended number
- Open Number Lookup and enter a complete number with its country code.
- Run the free analysis and read the normalized number and available metadata.
- Correct an invalid or ambiguous input deliberately.
- Confirm that the displayed result still belongs to the number you entered.
Static formatting, country and number-type information does not prove that a handset is currently reachable. Do not guess a country code to make an incomplete number pass validation. Process only numbers you are authorized to review.
2. Open the offered HLR action
Use the HLR action for the current analyzed result. The app prepares the lookup and shows the intended number with its quoted charge. In this reviewed mobile flow, you confirm that prepared request; the separate API’s optional lookup flags are not presented here as a set of mobile switches.
Read the number in the confirmation dialog, not just the text still visible behind it. Check the amount in euros and decide whether the lookup is needed. Choose Not now to leave the paid action unconfirmed.
3. Confirm once
- Confirm only while the displayed number and analysis remain the intended ones.
- Wait while the paid lookup is processed.
- Avoid navigating to another number and returning merely to submit the same lookup again.
- Read the result or the exact error when the operation finishes.
The confirmation context is tied to the current input and analysis generation. Changing the input invalidates the earlier context. Do not interpret a quote prepared for one number as authorization to look up another number at the same price.
4. Handle an uncertain result
If a timeout or temporary error leaves the result unclear, retain the current lookup context and inspect the displayed state. The app can retain its confirmation token for supported retryable outcomes. Follow the offered retry for that same operation rather than starting a fresh lookup repeatedly.
This is not a guarantee that every repeated lookup is free or that a pending token survives every app restart. If you cannot establish the prior outcome, contact Support with the time and sanitized error before deliberately buying another lookup. Do not clear app storage as a first troubleshooting step.
5. Interpret only the fields returned
- Read the available number, network, portability or status information.
- Check any displayed information timestamp and source.
- Compare the billed amount where shown with the request you confirmed.
- Leave missing optional information unknown instead of labeling the number inactive.
Cached information is different from a repeated request response, and a new screen load is not necessarily a new network observation. Porting dates and deeper activity details are not available for every destination or number type. Use the returned evidence within those limits.
6. Keep later communication decisions separate
A lookup does not establish consent, prove ownership or guarantee SMS or call delivery. Before any later contact, check the actual customer preference, permitted sender and destination policy. If Support is needed, send the lookup time, number reference, displayed charge and result/error wording privately; avoid sharing unrelated contacts or account credentials.
Related guides
- Check a phone number with Number Lookup
- Check phone numbers with the IllyVoIP Lookup API and optional HLR
Reviewed 13 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.