If you have ever tried to verify a WhatsApp, Instagram, or Google account with a Google Voice or TextNow number and been rejected, you have experienced the VoIP vs non-VoIP distinction firsthand. Understanding this difference is crucial for anyone who uses virtual phone numbers for SMS verification, because it is the primary technical factor that determines whether your verification attempt succeeds or fails.
#VoIP vs Non-VoIP: The Technical Difference
VoIP (Voice over Internet Protocol) numbers are phone numbers that route calls and SMS over the internet rather than through traditional cellular networks. Services like Google Voice, Skype, TextNow, and Vonage use VoIP technology. These numbers are issued through internet telephony providers and do not have a physical SIM card or cellular radio connection.
Non-VoIP (Real Carrier / Real SIM) numbers are phone numbers issued by traditional mobile carriers (like AT&T, Verizon, T-Mobile, Vodafone, etc.) that route through cellular networks using SS7 signaling. These numbers are associated with physical SIM cards (or eSIMs) and are connected to the carrier's cellular infrastructure. Shadow SMS provides non-VoIP numbers — real carrier numbers from legitimate telecom operators.
The key distinction is at the carrier registration level. Every phone number in the world is registered in telecom databases (like the LERG in the US or the Number Portability Database) with a carrier classification. VoIP numbers are registered under internet telephony carriers, while real SIM numbers are registered under mobile carriers. This classification is what platforms check during verification.
#How Platforms Detect VoIP Numbers
Platforms use specialized telecom intelligence APIs to check phone number types before accepting them for verification. Here is how the detection pipeline works:
You Enter a Phone Number
When you enter a phone number on a platform's registration form, the platform sends a lookup query to a telecom intelligence provider.
Carrier Lookup Query
The telecom intelligence provider (e.g., Twilio Lookup, Telesign, Plivo, Nexmo) queries carrier databases to determine the number's line type. The response includes: carrier name, line type (mobile, landline, VoIP, toll-free), country, and sometimes the original carrier (if the number has been ported).
Risk Scoring
The platform applies its own risk scoring algorithm. Numbers with a 'VoIP' line type receive a high risk score. Numbers with a 'mobile' line type from a recognized carrier receive a low risk score.
Accept or Reject
Based on the risk score, the platform either accepts the number and sends an SMS code, or rejects it with an error message like 'This phone number is not supported' or 'Please use a valid mobile number.'
#Why Platforms Block VoIP Numbers
- Low acquisition cost. VoIP numbers can be obtained for free or near-free (Google Voice is free, TextNow is free with ads). This means spammers and bot operators can create thousands of VoIP numbers at zero cost.
- Easy automation. VoIP services typically have APIs that allow programmatic number creation and SMS reception. This makes it trivial to automate mass account creation.
- No identity verification. Most VoIP services do not require government ID or identity verification to obtain a number. This makes them attractive for fraudulent activity.
- Historical abuse data. Platforms have years of data showing that accounts created with VoIP numbers are disproportionately involved in spam, fraud, and policy violations.
#How Non-VoIP Virtual Number Providers Work
Non-VoIP virtual number services like Shadow SMS work by partnering with (or operating as) licensed telecom operators. They own or lease blocks of real phone numbers that are registered as mobile carrier numbers in telecom databases. When you request a number, the service assigns one of these real carrier numbers to your session and routes incoming SMS from the cellular network to your online dashboard.
From a technical perspective, the SMS delivery path looks like this: Platform sends SMS → SMS gateway → SS7 network → Carrier receives SMS on SIM → Carrier forwards to virtual number service's infrastructure → You see the message in your dashboard. At every step in this chain, the number behaves identically to a personal mobile number because it is a real mobile number — the only difference is the endpoint.
#Carrier Lookup Databases: What Platforms See
When a platform performs a carrier lookup on different types of numbers, here is what the response looks like:
| Number Type | Carrier Name | Line Type | Platform Action |
|---|---|---|---|
| Personal AT&T SIM | AT&T Mobility | Mobile | Accept |
| Shadow SMS (US) | T-Mobile / AT&T (varies) | Mobile | Accept |
| Google Voice | Google (Grand Central) | VoIP | Reject |
| TextNow | TextNow / Bandwidth | VoIP | Reject |
| Skype Number | Microsoft (Skype) | VoIP | Reject |
| Hushed App | Bandwidth.com | VoIP | Reject (usually) |
Key Takeaway
The only reliable way to pass phone verification on major platforms is to use a number that returns 'Mobile' as the line type in carrier lookup databases. Shadow SMS numbers consistently return 'Mobile' because they are sourced from real carriers.
#Frequently Asked Questions
Jane Parkins
AuthorPrivacy & Telecom Analyst specializing in privacy engineering, telecom infrastructure, anti-bot protocols, and identity security.
Need a Virtual Number Right Now?
Get an instant OTP verification number across 50+ countries. Only pay for successful activations.