Verisoul Phone Deep Research Glossary
Last updated: May 26, 2025
Overview of Verisoul's Phone Deep Research
This product goes well beyond traditional "lookups" - in real-time we launch 20+ AI agents that scour the dark web, data breaches, social platforms, and online history to determine whether the phone line is legitimate and in-use.
Data We Return & How to Think About Each Field
Carrier & Line Information
Field | Definition | How to Interpret Risk |
phone_number | The queried number in E.164 format ( | Not a signal itself but ensure formatting is correct before testing other fields. |
type | Line classification: | VOIP lines have weaker KYC and are higher risk. Mobile is typical for consumers. Landline is common for businesses. |
status | Real‑time carrier status such as |
deserve extra scrutiny for mismatch with user’s identity. |
country_code | ISO dialling code automatically parsed from the number. | Mismatch with stated user country or proxy geolocation may indicate fraud. |
is_ported | Boolean – number has been ported between carriers. | Porting itself is common; recent porting (if present in carrier meta) can be fraud pattern for OTP hijack. Combine with |
original_network | First carrier that issued the number. | Trusted, large carriers add credibility; small low‑KYC MVNOs may add risk. |
current_network | Carrier currently serving the number. | Same interpretation as above; unexpected switch from high‑KYC to low‑KYC provider can raise flags. |
Validity & Format Checks
Field | Definition | How to Interpret Risk |
is_disposable | True if number is from a known disposable or temporary SMS service. | Strong reject signal – disposable numbers are widely abused. |
is_valid | True if HLR/carrier lookup confirms the line exists and can receive calls/SMS. |
|
is_valid_format | True if the digits match national numbering plan rules. |
|
is_suspicious_format | True if format is rarely seen in legitimate traffic (e.g. improbable prefixes). | Combine with other red flags; useful for catching algorithmically generated numbers. |
Risk Score & Summary Signals
Field | Definition | How to Interpret Risk |
risk_score | Composite risk score (0 – 100 %) derived from weighted model of all other signals. Lower % ⇒ lower risk. | <50 % = low risk / likely legitimate • 50-75 % = review • >75 % = elevated risk. Score is directional—always corroborate with individual flags. |
risk_flags | Array of short codes highlighting negative findings the model considered. | Any flag present should be reviewed; multiple flags or severe codes increase suspicion even if overall score looks moderate. |
trust_signals | Array of positive indicators that add credibility | The more trust signals, the more confidence you can place in the number. They are helpful counter‑weights to mild risk flags. |
Connected Identities
Field | Definition | How to Interpret Risk |
names_list | Distinct first/last names historically linked to the number across carriers, breaches, and social profiles. | Name matching to your user record boosts trust. A mismatch or empty list slightly increases uncertainty but is not by itself a high‑risk flag. |
connected_phones_count | Number of other phone numbers observed sharing this phone’s user cluster. | 0‑2 normal; >5 may indicate shared/abused accounts. |
connected_phones | List of the related numbers (masked for privacy). | Cross‑reference to detect duplicate sign‑ups. |
connected_emails_count | Emails historically linked to the phone. | 1‑3 typical (work, personal); 0 unusual; >10 spam/fraud ring indicator. |
connected_emails | List of those email addresses (masked). | Use for deterministic matching against your user‑supplied email. |
Online Presence & History
Field | Definition | How to Interpret Risk |
online_history_count | Number of distinct public sources (breaches, lead lists, registrations) that reference the phone. | 3‑50 = healthy history. 0 = no footprint → high risk. >200 could mean commodity spam lead—inspect manually. |
online_history_first_seen | Earliest UTC date we observed the number online. | Older dates (years) imply legitimacy; same‑day first‑seen during signup can be suspicious. |
online_history_age_years | Convenient integer/float representation of history length. | <1 yr = young (higher risk); >3 yrs = mature (lower). |
Social & Account Presence
Field | Definition | How to Interpret Risk |
socials_count | Total number of major platforms where the phone is confirmed. | 0 → high risk; 1‑3 moderate; 4+ strong legitimacy |
has_whatsapp | WhatsApp account associated | Presence shows user likely controls the number; absence alone isn’t disqualifying in regions where WhatsApp isn’t dominant. |
has_telegram | Telegram account associated | Same logic as WhatsApp. |
has_instagram | Instagram account associated | Social footprint indicator. |
has_amazon | Verified Amazon customer phone | Strong trust if your product overlaps with e‑commerce users. |
has_google | Google account phone | Positive signal; Google enforces SMS verification. |
has_office365 | Microsoft 365 account phone | Positive signal, especially for B2B. |
has_twitter | X/Twitter account phone | Neutral to slight positive. |
has_skype | Skype account phone | Strong positive - no incentive to defraud. |
has_apple | Apple ID phone | Strong device ecosystem tie; good trust. |
has_facebook | Facebook account phone | Adds trust; absence may be cultural/regional. |
Tip: A diversified social footprint (3+ platforms across different verticals) is a powerful trust indicator.