Open Source Intelligence Techniques

OSINT Techniques: Chapter 11 - Telephone Numbers

An exhaustive breakdown of Chapter 11 of Michael Bazzell's 'Open Source Intelligence Techniques', analyzing E.164 telecom standards, HLR carrier routing, VoIP detection, Truecaller reverse queries, and PhoneInfoga automation.

8 min read
views
visits
OSINT Techniques Chapter 11 Summary - Telephone Numbers
OSINT Techniques Chapter 11 Summary - Telephone Numbers

Welcome to our eleventh chapter analysis covering “Open Source Intelligence Techniques: Resources for Searching and Analyzing Online Information” (Sixth Edition) by Michael Bazzell.

A telephone number is one of the most strictly regulated, technologically consistent personal identifiers in the world. Unlike social media usernames or email addresses, telephone numbers are managed by international telecommunications authorities (ITU), bound to physical SIM cards, mapped across cellular towers, and tied directly to two-factor authentication (2FA) ecosystems.

In Chapter 11: Telephone Numbers, Bazzell details the mechanics of telecommunications reconnaissance. A phone number is not merely 10 digits; it is an entry point into carrier routing records, Home Location Register (HLR) switches, Caller ID name databases (CNAM), messaging profile caches (WhatsApp, Telegram, Signal), and automated reverse lookup engines. In this comprehensive guide, we dissect the E.164 standard, HLR lookup mechanics, VoIP identification, Truecaller scraping, and automated CLI workflows.


Key Takeaways

  • The International E.164 Standard: Every phone number must be normalized into standard international format (+[Country Code][Subscriber Number]) to prevent query errors across global telecommunication databases.
  • HLR (Home Location Register) Lookups: Querying HLR switches reveals whether a number is currently active, identifies the original serving network vs the ported network, and exposes the Mobile Country Code (MCC) and Mobile Network Code (MNC).
  • VoIP vs Mobile Carrier Discrimination: Identifying whether a number belongs to a traditional mobile provider (AT&T, Vodafone, Orange) versus a Virtual VoIP provider (Twilio, Google Voice, Bandwidth.com) dictates the likelihood of burner usage or digital spoofing.
  • Caller ID & CNAM Repositories: Line Information Databases (LIDB) return the true legal subscriber name configured by the billing carrier, bypassing whatever custom display name the caller chooses to transmit.
  • App-Based Reverse Directory Crowdsourcing: Services like Truecaller, Eyecon, and Sync.ME function by scraping the address books of hundreds of millions of mobile users, creating massive crowdsourced reverse directories that map unknown numbers to real names.

Architectural & Investigative Workflow

The following flowchart outlines the telecommunications intelligence extraction methodology:

flowchart TD
    subgraph Number_Normalization["Phase 1: E.164 Normalization & Telecom Metadata"]
        RawNumber["Raw Phone Number Input (e.g., (555) 019-2834)"] --> E164["Normalize to E.164 Format (+15550192834)"]
        E164 --> HLR["Execute HLR / LRN (Location Routing Number) Lookup"]
        HLR --> Carrier["Extract Carrier (MCC/MNC) & Line Type (Mobile / Landline / VoIP)"]
    end
    subgraph Directory_Harvesting["Phase 2: Reverse Caller ID & Crowdsourced Directories"]
        E164 --> CNAM["Query Official CNAM / LIDB Registry"]
        E164 --> Crowdsource["Query Truecaller / Eyecon / Sync.ME APIs"]
        CNAM --> LegalName["Subscriber Billing Name & Tagged Identity"]
        Crowdsource --> LegalName
    end
    subgraph Messaging_Enumeration["Phase 3: Messaging Ecosystem Discovery"]
        E164 --> Sync["Address Book Sync (WhatsApp, Telegram, Signal)"]
        Sync --> UserMedia["Exfiltrate Profile Photo, Bio, Last Seen Timestamp"]
    end
    subgraph Fusion["Phase 4: Target Dossier Fusion"]
        Carrier --> Dossier["Complete Subscriber Dossier"]
        LegalName --> Dossier
        UserMedia --> Dossier
    end

Technical Breakdown & Investigative Mechanics

1. The E.164 Standard & Carrier Identification

Before executing investigative queries, numbers must be validated using telecommunication parsing libraries like Google’s libphonenumber:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
#!/usr/bin/env python3
# telecom_normalizer.py - E.164 Parsing & Carrier Metadata Extraction
import phonenumbers
from phonenumbers import geocoder, carrier

raw_input_number = "+1 202-456-1111"

# Parse and normalize
parsed = phonenumbers.parse(raw_input_number, None)

if phonenumbers.is_valid_number(parsed):
    e164_format = phonenumbers.format_number(parsed, phonenumbers.PhoneNumberFormat.E164)
    region = geocoder.description_for_number(parsed, "en")
    operator = carrier.name_for_number(parsed, "en")
    
    print(f"[+] Normalized E.164: {e164_format}")
    print(f"[+] Geographic Region: {region}")
    print(f"[+] Original Carrier: {operator if operator else 'Unknown / Landline'}")
else:
    print("[-] Invalid Phone Number!")

2. HLR (Home Location Register) Lookups & VoIP Detection

An HLR Lookup sends a live SS7/Diameter network interrogation signal to the core mobile switching network to verify the status of the subscriber identity module (SIM) without ringing the phone:

Critical Data Points Returned by an HLR Query:

  • Live Status: Active (connected to a tower), Inactive / Suspended, Disconnected.
  • Ported Status: Has the number moved from its original carrier (e.g., ported from Verizon to a VoIP provider like Twilio)?
  • IMSI MCC/MNC: Reveals the exact cellular network operator currently routing the SIM card.
1
2
# Example Twilio Lookup API query using curl to inspect line type intelligence
curl -X GET "https://lookups.twilio.com/v1/PhoneNumbers/+15550192834?Type=carrier&Type=caller-name"     -u "ACxxxxYOUR_ACCOUNT_SID:your_auth_token" | jq .

Sample API Response:

1
2
3
4
5
6
7
8
9
10
11
12
13
{
  "caller_name": {
    "caller_name": "DOE, JANE",
    "caller_type": "CONSUMER"
  },
  "carrier": {
    "mobile_country_code": "310",
    "mobile_network_code": "410",
    "name": "AT&T Mobility LLC",
    "type": "mobile"
  },
  "phone_number": "+15550192834"
}

3. Automated Scanning via PhoneInfoga

PhoneInfoga is an advanced open-source CLI intelligence scanner designed specifically for telephone number footprinting:

1
2
3
# Installing and launching PhoneInfoga
curl -sSL https://raw.githubusercontent.com/sundowndev/phoneinfoga/master/support/scripts/install | bash
./phoneinfoga scan -n +15550192834

What PhoneInfoga Performs:

  1. Validates standard international format and checks ITU allocation tables.
  2. Identifies carrier, country of origin, and line type (Fixed, Mobile, VoIP).
  3. Executes automated search engine dorks targeting public directories, classified ads (Craigslist, eBay), and leaked paste sites.

4. Messaging Platform Address Book Syncing

One of the most effective techniques for de-anonymizing an unknown burner number is syncing it with mobile messaging applications:

graph LR
    A["Investigator Adds Target Phone to Isolated Burner Device Address Book"] --> B["Open WhatsApp / Telegram / Signal"]
    B --> C["Refresh Application Contact List"]
    C --> D["Target Account Automatically Surfaces in Contacts"]
    D --> E["Extract Uncompressed Profile Avatar, Display Name, About Status"]

OpSec Warning for Address Book Syncing:

  • Never conduct address book syncing from a personal phone. WhatsApp and Telegram notify contacts when mutuals join or update, and your own phone number may be revealed to the target.
  • Always conduct address book syncing from a dedicated, hardware-isolated burner smartphone running on a cellular proxy.

Real-World Case Scenario

Case Study: Unmasking a BEC (Business Email Compromise) Scammer

A CFO received a text message purporting to be from the company CEO: “In an urgent board meeting. Wire $85,000 to this vendor account immediately.”

An internal security analyst initiated immediate phone reconnaissance:

  1. The message originated from +1 (646) 555-0182.
  2. Normalizing the number and querying an HLR carrier API revealed the line type was VoIP, hosted on Bandwidth.com (a common provider used by Google Voice and burner apps).
  3. The analyst added the number to an isolated burner phone and checked WhatsApp: the account had a live profile picture showing an individual standing in front of an apartment complex in Lagos, Nigeria.
  4. Reverse image searching the profile picture on Yandex identified the individual’s personal Facebook profile, confirming the communication was an unauthorized impersonation attempt.

Defensive Countermeasures & OpSec Recommendations

For executives, journalists, and security practitioners:

  1. Protect Against SIM Swapping via Carrier PINs: Place an explicit verbal port-freeze password and high-security PIN on your cellular account to prevent social engineering attacks against carrier store clerks.
  2. Never Use SMS as a Primary Two-Factor Authentication (2FA) Mechanism: Transition all sensitive accounts (email, cloud, banking) from SMS-based 2FA to hardware security keys (YubiKey) or time-based authenticator apps (TOTP).
  3. Scrub Numbers from Crowdsourced Directories: Visit Truecaller’s unlisting portal (truecaller.com/unlisting) to demand the removal of your phone number from their crowdsourced database.

Conclusion & Next Steps

Chapter 11 proves that telephone numbers bridge the gap between virtual identities and physical telecom infrastructure. By leveraging E.164 normalization, HLR carrier routing, and messaging address book synchronization, an investigator can identify the human behind the number.

In Chapter 12: Online Maps & GEOINT, we enter the world of geospatial intelligence: solar azimuth calculations, shadow triangulation, multi-provider satellite analysis, and architectural landmark mapping.


Practical Telephony Forensics & Carrier Resolution Cheat-Sheet

Analytical Phase Tool / Command Syntax Investigative Output
PhoneInfoga Deep Recon phoneinfoga scan -n +1234567890 Extracts international country code, telecom provider, line type, and Google footprints
Authoritative Carrier Lookup curl -X GET 'https://lookups.twilio.com/v1/PhoneNumbers/<NUM>?Type=carrier' -u ACxxx:auth Returns true carrier Type Allocation Code (TAC) and distinguishes Mobile from VoIP
Crowdsourced Caller ID sync.me | truecaller.com web search Identifies crowdsourced contact names, spam reports, and profile pictures
NPA-NXX Geographic Mapping nanpa.com (NPA / central-office code reports) Maps telephone area code and central exchange prefix to original switchboard rate center
Reverse Whitepages Search site:whitepages.com/phone/<NUM> Retrieves historical landline subscriber billing records and street addresses

Authoritative References & Verified Investigative Sources


Author: Abdulrahman M. Fathi (0x3bdo) • Cyber Security Engineer & Penetration Tester

Open Research & Community Labs
صدقة جارية • Ongoing Charity

Empowering the Cybersecurity Community

All research, lab walkthroughs, and technical series on this platform remain 100% free. You can support server hosting, research environments, and lab infrastructure.

Support & Wall of Honor
اللهم اجعل هذا العمل علمًا نافعًا وصدقةً جارية، واكتب لي به الأجر والقبول، وانفع به كل من قرأه أو تعلّمه.
اللهم احفظ لي والديّ وأهلي، وبارك في أعمارهم وصحتهم، وأدم عليهم نعمة الصحة والعافية، ولا تريني فيهم بأسًا يبكيني.
Dedicated as ongoing charity and beneficial knowledge. May Allah bless my parents and family, protect them, and grant them lasting health and happiness.