> For the complete documentation index, see [llms.txt](https://nexvision-lab.gitbook.io/nexvision-lab-documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexvision-lab.gitbook.io/nexvision-lab-documents/getting-started/nexvision-saas/osint-360/mobile-number-search.md). # Mobile Number Search ## Step 1: Access the Dashboard When you log in, you'll see the OSINT360 welcome screen with four quick-launch investigation tiles and the **Investigation Types** sidebar on the right.
## Step 2: Select Mobile Number Search Open the **Investigation Types** panel from the right sidebar. 1. Set **Category** → `Person` 2. Click the **Available Types** dropdown 3. Select **`Mobile Number Search (discovery_mobile)`** The right panel will expand to show **Type Details**: | Field | Value | | ------------------- | --------------------------------------------------------------- | | **Category** | Person | | **Title** | Mobile Number Search | | **Type Value** | `discovery_mobile` | | **Description** | Search for mobile numbers in leaked documents and data breaches | | **Query Parameter** | Mobile Number | The search bar at the bottom will update automatically: ``` Investigate discovery_mobile target: [Enter mobile number...] ``` ## Step 3: Enter the Target Phone Number With the `discovery_mobile` mode active, type the target phone number into the input field.
**Format guidelines:** | Format | Example | Recommended | | --------------------- | ----------------- | ------------------- | | International (E.164) | `+15550343955` | ✅ Best | | With spaces | `+1 555 034 3955` | ✅ Works | | Local format | `5550343955` | ⚠️ May miss results | 💡 **Tip:** Always use the **full international format** including country code (e.g., `+1` for USA, `+44` for UK) to maximize result coverage across global databases. ## Step 4: Initiate the Search Press **Enter** or click the **Send** button (`➤`) to submit your query. The platform displays your query as a chat message and immediately returns a **Discovery Search Started** confirmation card:
The confirmation card shows: | Field | Example Value | | ------------- | -------------------------------- | | **Query** | `+15550343955` | | **Type** | `Mobile` | | **Search ID** | `b7d3f29a` *(unique per search)* | ⏳ The system searches the Discovery database and open web simultaneously. This typically takes **10–30 seconds**. Click **"Check Results"** when prompted to retrieve the latest findings. ## Step 5: Carrier & Number Intelligence Result Once complete, a **Carrier & Number Intelligence** result card is returned:
The result card structure: ``` 🔧 Tools: nexvision_telecommunications_provider, discovery_search ───────────────────────────────────────────────────────────────── 📱 Phone/Mobile Search: +1 555 012 3456 📞 Carrier & Number Intelligence - Carrier: Example Wireless Co. - Line Type: MOBILE - Location: United States - Country Code: +1 - Region: US - Timezone: America/New_York Formats - International: +1 555 012 3456 - National: 555 012 3456 - E.164: +15550123456 Validation: ✅ Valid · ✅ Possible ``` ## Step 6: Platform Registration Result Below the carrier result, a **Platform Registration** section shows which major platforms have an account registered to this number:
``` 📲 Platform Registration - ✅ Instagram ( instagram.com ) - ✅ Amazon ( amazon.com ) ``` A checkmark (✅) indicates the number was found associated with a registered account on that platform. Platforms not listed either returned no match or were not checked in this query. ## Step 7: Person Records from Leaked Data If the number appears in breach or leaked datasets, OSINT360 returns associated identity records:
``` 👥 Person (2) ───────────────────────────────────────────────────────────────── 1. Unknown - Firstname: john - Email: j.doe85@example.com - Phone: +15550123456 - Gender: male - Program: classico - Notes: +08180412345 - Source: US - Mobile Phone - Source Type: leak ───────────────────────────────────────────────────────────────── 2. Unknown - Firstname: jane - Email: jane.sample@example.com - Phone: +15550123456 - Gender: female - Program: attestato professionale - Notes: +08180419876 - Source: US - Mobile Phone - Source Type: leak ``` ⚠️ Multiple records for the same number are common. A number may have been re-issued to a different subscriber, or the same number may appear across multiple independent breach datasets. **Result Fields — Reference** **Carrier & Number Intelligence**
FieldDescription
CarrierMobile network operator name
Line TypeConnection type: MOBILE, LANDLINE, VOIP, TOLL-FREE, etc.
LocationCountry where the number is registered
Country CodeInternational dialling prefix (e.g. +1, +44, +65)
RegionISO 3166-1 alpha-2 country code (e.g. US, SG)
TimezoneIANA timezone string (e.g. America/New_York, Asia/Singapore)
InternationalHuman-readable international format with spaces
NationalLocal format without country code
E.164Standardised compact format for API/database use
ValidNumber passes structural validation rules
PossibleNumber matches a known numbering plan range
#### Platform Registration
FieldDescription
Platform NameName of the platform checked (e.g. Instagram, Amazon)
Platform URLDomain of the platform
Status✅ Found — number is registered on this platform
#### Person Records
FieldDescription
FirstnameFirst name from the breach record
EmailEmail address linked to the number in the breach
PhonePhone number as stored in the breach dataset
GenderGender field from the source dataset (if available)
ProgramLoyalty or membership program from the source (if available)
NotesAdditional reference data from the breach record
SourceBreach or dataset name (e.g. US - Mobile Phone)
Source Typeleak = data breach; public = public record
### Understanding Phone Number Formats | Format | Example | Usage | | ----------------- | ----------------- | ---------------------------------------------------------------- | | **E.164** | `+15550123456` | Standardised format for APIs and databases — no spaces or dashes | | **International** | `+1 555 012 3456` | Human-readable with country code and spaces | | **National** | `555 012 3456` | Local format — omits country code | #### Common Country Code Prefixes | Country | Code | Example | | ---------------------- | ----- | ----------------- | | United States / Canada | `+1` | `+1 555 012 3456` | | United Kingdom | `+44` | `+44 7700 900123` | | Singapore | `+65` | `+65 9123 4567` | | Australia | `+61` | `+61 4 1234 5678` | | Germany | `+49` | `+49 170 1234567` | | India | `+91` | `+91 98765 43210` | **Platform Registration Explained** Platform registration checks query whether the submitted number is associated with an account on major consumer platforms. Results are derived from publicly available signals and breach-correlated datasets.
ResultMeaning
✅ FoundNumber is associated with a registered account on this platform
❌ Not foundNo registration detected for this number on this platform
— Not checkedPlatform was not included in this query scope
📌 Platform registration data reflects findings at the time of investigation. Account status may change if the number is deregistered or transferred. **Privacy & Data Handling** OSINT360's Mobile Number Search module is designed with **privacy-by-design** principles:
What is usedWhat is NOT used
✅ Phone number for carrier lookup❌ Call records or SMS content
✅ Public telecom database query❌ Real-time location data
✅ Breach dataset cross-reference❌ Live network operator data
✅ Platform registration signals❌ Private account content
✅ Number validity and format check❌ Financial or billing information
The module performs **passive lookups** against public carrier databases and breach datasets. It does not interact with live telecom networks or access any real-time subscriber data. **Tips & Best Practices** 📱 **Input Formatting** * Always use full **E.164 international format** including the `+` and country code * Spaces and dashes are stripped automatically — `+1-555-012-3456` and `+1 555 012 3456` both work * For numbers without a known country code, prepend the most likely country code based on your investigation context 🔗 **Cross-Reference Strategy** * Use **Mobile Number Search** to identify the carrier and country of origin * Combine with **Person Search** to link the number to an individual's full profile * Use the **Region** and **Timezone** results to narrow geographic investigation scope * Cross-reference **Platform Registration** findings with **Social Media Scan** for deeper profiling * Combine with **Court Cases** or **Behavior Analysis** for comprehensive person investigations 🔍 **Use Cases** * Verifying the carrier and country of origin for a number used in suspicious communications * Identifying platform accounts linked to an unknown number during fraud investigations * Cross-referencing breach records to surface associated email addresses and identities * Confirming number validity before initiating outreach in due diligence workflows ## Step 7: Continuing the Investigation After results are returned, OSINT360 suggests follow-up modules to deepen the investigation:
``` ✨ Continue Investigation — run additional modules on +1 555 012 3456: [ 🔍 Sanctions Check ] [ 📲 Social Media Profiles ] [ 🌐 Open Web Search FREE ] ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nexvision-lab.gitbook.io/nexvision-lab-documents/getting-started/nexvision-saas/osint-360/mobile-number-search.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.