A
MODULE_DEPLOYED // NUMINT-PHONE-BASICS

NUMINT: START WITH THE DIGITS, NOT THE DRAMA

Parse a phone number offline with libphonenumber, learn what presence checks are (and why this lesson never runs them), and keep phone OSINT on the safe side of the line.

BEGINNER

EST_TIME: 35 MIN

PHASES: 5

SYNC_PROGRESS0 / 5 PHASES COMPLETED (0%)
MISSION_PHASES
1
WHAT NUMINT DOESDURATION: 8 min
2
WALKTHROUGH ON YOUR OWN NUMBERDURATION: 12 min
3
LIMITS AND FALSE POSITIVESDURATION: 7 min
4
ETHICS AND LEGAL LIMITSDURATION: 5 min
5
QUIZDURATION: 3 min
OPERATIONAL_DATA
EXTRACT_RESOURCES
PHASE_001 // CURRENT_OBJECTIVE
WHAT NUMINT DOES
NODE: 1 / 5

Most phone "lookups" start by reading the number itself

A phone number already contains a lot of public information before you ask any website anything: country, possible region, line type (mobile, landline, VoIP), and standard formats. Google's libphonenumber library does that offline. Numint wraps it, then optionally adds:

  1. **Offline parse** (always available, no network): valid or not, type, formats, country, region, carrier name where the library knows it, time zones.
  2. **API providers** (optional keys): freemium carrier/spam-risk services.
  3. **Presence checks** (exist in the tool; **not used in this lesson**): whether the number is registered on a few platforms via login-style endpoints. Same risk family as Holehe; can SMS the number owner. Numint gates them behind --presence --yes-authorized. We leave that flag alone.
  4. **Search links**: ready-made Google/Bing queries and reverse-lookup URLs. Listing the links is fine; opening them en masse is a separate choice.
  5. **Optional AI summary**: only if you give it a key. Skip it for this lesson.
If your first move with a phone number is to blast it at social platforms, you're skipping the free part of the work — and this course will not ask you to do that.