whose-number-is-this

Investigate phone numbers via E.164 normalization, carrier lookup, VoIP detection, and reverse search.

38|2|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/UseOSINT/Skills --skill whose-number-is-this-useosint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: whose-number-is-this
Source: https://github.com/UseOSINT/Skills/tree/main/skills/whose-number-is-this
Command: npx skills add https://github.com/UseOSINT/Skills --skill whose-number-is-this-useosint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Identifying who owns a phone number is harder than it looks: carrier data goes stale after number porting, VoIP and burner numbers masquerade as real mobiles, and search engines fail to match the dozen different ways the same number gets written. This Skill provides a structured, legally-aware workflow for attributing a phone number with confidence grading instead of guesswork. ## Core Features & Use Cases - Normalization and Classification: Parses numbers to E.164 with libphonenumber and phoneinfoga, extracting country, national destination code, and line type (mobile, fixed, VoIP, toll-free). - Carrier and VoIP Analysis: Distinguishes live HLR lookups from stale prefix-table results, flags ported numbers, and detects virtual or burner numbers that are weak identity anchors. - Exhaustive String Search: Searches every written permutation of the number across multiple engines, breach corpora, and archived pages, with caller-ID aggregator results treated as unverified leads. - Use Case: A fraud analyst verifying a supplier before a payment runs the number, discovers it is a VoIP line whose reverse-lookup name traces to a single echoed source, but finds it in a cached trade directory under a company with a mismatched address — the discrepancy becomes the reportable finding. ## Quick Start Investigate the phone number +44 7700 900123 and tell me who it likely belongs to, its line type, and whether it appears on WhatsApp or Telegram.

Frequently Asked Questions about whose-number-is-this

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out who owns a phone number?▼

Normalize the number to E.164 with libphonenumber, then search every written format quoted across multiple search engines, breach corpora, and archived pages. Treat caller-ID and reverse-lookup names as unverified leads, since their data comes from other users' address books.

How to detect a VoIP or burner phone number?▼

Check the line type from libphonenumber or phoneinfoga, then examine the allocated operator: wholesale number-hosting or communications-API providers indicate a virtual number. An area code unrelated to any other location evidence and numbers bought in adjacent blocks are additional signals.

Why does a carrier lookup show the wrong network for a number?▼

Number portability lets subscribers keep their number while changing networks, so prefix-to-carrier tables only show the original allocation. Only a live HLR query returns the network the number is currently homed on; always record which lookup method produced the answer.

Can I check if a number is registered on WhatsApp or Telegram?▼

Yes, via contact discovery, but it is an interactive check that queries the platform from an account and may expose your own contact list. It requires explicit authorization, a clean device and account, and one number at a time, since bulk lookup violates platform terms.

Why does searching a phone number return no results?▼

Search engines match literal strings, and numbers appear in dozens of formats with different country codes, separators, groupings, and trunk prefixes. Generate the full permutation set including obfuscated forms like spelled-out digits, and search each variant quoted across more than one engine.