Non-VoIP Numbers Explained: How Platforms Detect VoIP

A non-VoIP number is a phone number that belongs to a mobile carrier (AT&T, T-Mobile, Verizon, Vodafone, and so on) and is registered in carrier databases as a MOBILE line. A VoIP number is issued by an internet telephony service (Google Voice, TextNow, Twilio, Hushed) and is registered as VOIP. Platforms look up that classification before they send a verification code, which is why codes to VoIP numbers often never arrive.

This is the explainer: what the two types are, how a platform tells them apart, why VoIP fails, and when you actually need a carrier number. If you already know all that and want to pick a provider, go straight to our comparison of non-VoIP SMS verification services. If you want a number now, VoidMob's non-VoIP numbers come as one-time codes, rentals and dedicated monthly numbers.

What "non-VoIP" actually means

The distinction is not "internet vs cellular". It is how the number is registered. Every phone number is assigned by a carrier or a telephony provider, and industry databases (the ones behind Twilio Lookup and Telesign PhoneID) record who owns the range and what kind of line it is: MOBILE, LANDLINE, VOIP, FIXED_VOIP, PREPAID, TOLL_FREE, or UNKNOWN (exact labels vary by vendor).

• A number on a physical SIM or an eSIM from a real mobile carrier is MOBILE. That is a non-VoIP number. Wi-Fi calling on your personal phone is still non-VoIP, because the number is registered to the carrier.
• A number from Google Voice, TextNow, Burner, Hushed, TextMe, Dingtone, or any Twilio/Bandwidth-based app is VOIP. Paying $5/month for a "premium" virtual number does not change the range it comes from, so it stays VOIP.

Non-VoIP verification services like VoidMob sit in the first group: the numbers are carrier lines hosted on real hardware, and you receive the code through a dashboard or API instead of holding the SIM yourself.

VoIP vs non-VoIP at a glance

How platforms tell the difference

When you submit a number, a platform with fraud controls typically runs it through a phone validation API and checks four groups of signals.

Line type and carrier metadata

The line_type field is the decisive one. VOIP halts most flows immediately, UNKNOWN lowers deliverability, MOBILE proceeds. Alongside it: carrier_name (a real carrier vs an aggregator or "generic" label), the MCC/MNC pair, and porting history. Frequent or recent ports raise suspicion.

An illustrative validation response for each type:

// VoIP number
{ "line_type": "VOIP", "carrier_name": "Generic VoIP Provider",
"country_code": "US", "risk": { "reputation": "low_trust", "recent_abuse": true } }

// Carrier number
{ "line_type": "MOBILE", "carrier_name": "AT&T Wireless",
"country_code": "US", "risk": { "reputation": "normal", "recent_abuse": false } }

Routing and delivery patterns

Carrier numbers receive SMS through the carrier's own SMSC. VoIP numbers receive it through internet relays with extra hops. Platforms watch delivery-receipt timing: codes to real mobile lines land in a normal window, codes to cheap VoIP routes stagger or fail, and that pattern feeds back into the number's reputation.

Number tenure and activity

How long the number has been assigned, whether it has normal call and SMS activity, and whether it sits in a range that gets recycled constantly. Brand-new VoIP blocks with no activity get lumped in with automation.

Device and network coherence

Mobile apps can read radio type, SIM presence and carrier from the device, and every request carries an IP with an ASN. If the number says MOBILE but the device shows no SIM and the traffic exits from a datacenter ASN, the mismatch itself is a flag. This is why a US number used from a US mobile IP passes more often than the same number used through a VPN in another country. The mobile proxy pairing exists for that reason: matching number region, IP region and network type.

Why VoIP numbers fail

The platform-side view of virtual-number detection goes deeper on the risk engines; the short version is that, put together, the consequences of a VOIP classification are:

• Silent rejection: the code is never sent, and most platforms show no error explaining why. You just wait.
• Late or dropped codes: even when a platform allows VoIP, multi-hop routing adds 5 to 10 seconds and some OTPs never arrive.
• Burned ranges: once a provider's block is flagged, they rotate to a new pool and your number stops working, taking your logins with it.
• Retroactive action: platforms that accepted a VoIP number at signup can re-check later. Accounts verified with VoIP are a common casualty of routine sweeps months after creation, and everything on the account goes with them.

When VoIP is fine, and when it is not

VoIP still has honest uses: developers testing verification flows, platforms that explicitly accept it (many forums, some games and chat apps), genuinely throwaway signups, and low-stakes newsletters. If the account can vanish tomorrow without cost, use the free option.

Use a carrier number when the account is connected to income (seller accounts, gig platforms, business social profiles), when it is a financial platform (banks, payment processors, exchanges almost universally reject VoIP), when the account has value you cannot rebuild, when time matters, or when you want it to work the first time. Google's account flows are known to weigh whether the number's country matches your apparent location. Consumer WhatsApp SMS verification rejects VoIP numbers (WhatsApp's own help page lists the number types it does not support). Most major financial platforms decline to send codes to numbers classified as VoIP.

Ways to get a non-VoIP number

• Your own SIM or eSIM. Fully yours, tied to your identity, and in most countries requires ID to register.
• One-time verification services. You pay per code (from $0.15 at VoidMob), receive the SMS through a dashboard or API, and the number is released afterward. Right for single verifications.
• Rentals. The same number held for days or weeks on one platform, for flows that send more than one code.
• Dedicated monthly numbers. One carrier number assigned to you, working across every supported platform, kept as long as you pay. This is the option for 2FA on accounts you keep for years, because rentals eventually expire and one-time numbers cannot be reused. VoidMob's dedicated numbers are currently live in the US, UK, Australia, Germany and Hong Kong.

Which providers are actually non-VoIP, and how they compare on price and reliability, is covered in the service comparison. This article stays on the mechanics.

A short practical checklist

1. Confirm the line type before you rely on a number. Run it through a lookup or ask the provider; "SIM-based" and "non-VoIP" are the words you want, not "virtual", "cloud" or "temporary".
2. Match region and network. A US number used from a US mobile IP with a normal device fingerprint gives the highest delivery rate. Mismatches trigger the coherence checks above; the location consistency test shows what a platform sees.
3. Space out requests. Many services throttle repeated OTPs to one number; wait about 60 seconds between attempts.
4. Keep long-term numbers active. Carriers can recycle idle lines. One SMS a month is enough for a dedicated number.
5. One number per account for anything you keep. Shared or dynamic pools are how "number flagged as reused" happens.

Troubleshooting

• Code never arrives. Check the validation result if you can. VOIP or UNKNOWN means switch to a confirmed mobile line. Then check your egress IP with the IP type checker: a datacenter or non-matching country exit lowers deliverability even on a good number.
• Arrives late (over 60 seconds). Route quality or platform throttling. Try a line on a different carrier.
• "We can't verify this number." The platform blocked the line type. A different carrier number with some tenure usually clears it.
• Works on web, fails in the app. The app is reading device signals (SIM presence, radio info). Test from a device that actually hosts the SIM or eSIM.
• Intermittent success. The number's range may be partly burned. Move to a fresh carrier allocation and keep the network identity stable during the OTP flow.

Where this leaves you

Non-VoIP means carrier-registered. Platforms check that registration, plus routing, tenure and device coherence, before they send a code. Nothing you do on the VoIP side changes the classification, so for any account that matters the answer is a real carrier number, matched to a sensible IP and device. For choosing between providers, read the service comparison linked above; for what a dedicated number costs and where it is available, the SMS page has current pricing.

FAQ