Key Takeaways:
• What the difference is: a real mobile number and a VoIP number are classified differently in carrier and regulatory records. Whether a given call uses the internet has nothing to do with it.
• Two separate axes: transport is how the audio travels (cell, Wi-Fi, or IP); classification is the administrative line type. A mobile call can travel the internet and stay classified as mobile.
• Why it decides verification: services run a lookup that reads the classification field. A real mobile number passes, and a VoIP-classified number gets refused regardless of transport.
• Quick next step: get a real U.S. mobile number that returns mobile on a lookup at slynumber.com/app/register.
1. What is the difference between mobile and VoIP?
The common definition of a VoIP number is simply "a phone number that uses the internet," but that description is incomplete because it focuses on how communications are transported, not how the number is classified. Today, many traditional mobile calls and text messages also travel over IP networks, so internet transport alone does not distinguish a VoIP number from a mobile number.
The real distinction lies in the number's classification within telecommunications numbering records. In the United States, carrier lookup services determine a phone number's type using industry databases such as the Local Exchange Routing Guide (LERG), Number Portability Administration Center (NPAC), and other carrier records. These databases identify the carrier currently serving the number and classify it as mobile, landline, VoIP, or another line type.
When a bank, financial institution, or online service verifies a phone number, it does not analyze how calls or messages are transmitted. Instead, it performs a carrier lookup and reads the number's classification from these telecommunications records. The question isn't whether the communication travels over the internet—it almost certainly does. The question is whether the number is classified as a mobile line or as a VoIP service, because that classification is what determines whether the number is accepted for verification, authentication, and other security-sensitive applications.
2. Classification and transport are two separate axes
Transport and classification are independent. Treat them as two separate questions and the confusing cases resolve themselves. The regulatory definition supports the split directly.
Transport is the path the audio takes: a cellular voice channel, Wi-Fi Calling, VoLTE, or a VoIP provider's IP link. Classification is the line type on file: mobile, landline, or VoIP. The two don't have to agree in the way people assume. A T-Mobile call placed over Wi-Fi Calling travels as IP packets across the internet, yet the number stays classified as mobile. Its subscriber record never changed. A VoIP number travels over IP too, but its record says VoIP. Same transport, different classification. Even the federal definition of VoIP is a service-registration test rather than a per-call transport test. Regulators treat the two as distinct.
The FCC's definition of "interconnected VoIP service" in 47 CFR 9.3 turns on four service conditions. Those include broadband from the user's location and IP-compatible equipment. The same rules define Commercial Mobile Radio Service as its own separate regulatory category. In regulation, "mobile" and "VoIP" are classifications rather than descriptions of a call's path (accessed July 18, 2026).
What this means for you: the fact that SLYNUMBER delivers over the internet tells you nothing about its classification. The number is filed as a mobile line, so a lookup returns mobile. That's the only field a verifier checks.
3. Where the classification actually lives
The classification lives in administrative databases. It's assigned when numbers are handed out and maintained as they move. Two records matter most, and both are publicly documented.
The first record is set at the numbering level. The North American Numbering Plan (NANP) governs U.S. and Canadian phone numbers. Under it, blocks of numbers are assigned to carriers by company-code category. A wireless carrier requests numbers under a wireless category; an interconnected VoIP provider requests them under a VoIP category. The category travels with the block from the moment it's issued. A number's type is set before anyone ever places a call on it. The second record is the operator's own subscriber database. A number counts as mobile when a live HLR record binds an International Mobile Subscriber Identity to the dialable number. To the network, that binding is what makes the line "mobile." Both records can be queried, and a lookup service ultimately reflects them when it returns a line type. In the U.S., those block assignments are published in the LERG Routing Guide. It pairs each NPA-NXX block with the Operating Company Number holding it, plus a use type. NPAC data then accounts for numbers that have ported away from the carrier the block was issued to.
NANPA's CO Codes and Thousands-Blocks documentation assigns numbering resources by company-code category. The categories explicitly include "Wireless Carriers (WIRE)" and "Internet Provider Enabled Services (IPES), Interconnected VoIP." The category is set at the numbering-resource level (accessed July 18, 2026).
iconectiv's TRA LERG Routing Guide general information section documents the records that carry those assignments. It maps Operating Company Numbers to NPA-NXX blocks and defines the central office code type (COCTYPE) marking each block's use (accessed July 28, 2026). Twilio's Line Type Intelligence coverage note gates Canadian results on Number Portability Administration Center (NPAC) data access. NPAC is the porting layer over those block records (accessed July 28, 2026).
Independent HLR references, including Eseye's Home Location Register documentation, describe the HLR as the operator's subscriber database. It stores the IMSI as its primary key, bound to the MSISDN, the dialable number. The record also holds service entitlements and current location. A live IMSI-to-MSISDN binding is what defines a mobile line (accessed July 18, 2026).
Where SLYNUMBER fits: SLYNUMBER numbers are issued and registered as mobile lines in these carrier records. Both the numbering category and the subscriber record read mobile. For how a lookup traverses those records, see how carrier lookups work.
4. Fixed vs non-fixed VoIP, and why the split proves the point
VoIP covers two categories, and the split has nothing to do with how the audio travels. Fixed and non-fixed VoIP use the same IP transport. What separates them is whether the number is tied to a physical service, an administrative fact. If lookup vendors were tracking transport, this distinction couldn't exist; they track classification, and the fixed/non-fixed split is part of it.
The two subtypes carry different risk to a verifier. A fixed VoIP number is bound to a physical location or device, so it leaves at least a thin identity trail. A non-fixed VoIP number is the kind you obtain online in seconds with no physical anchor. It's the category strict services refuse most often. Neither is "more internet" than the other. Both ride the same protocols. The category is a record of how the number was provisioned. That record is what the lookup returns and the verifier reads.
Twilio Lookup v2 Line Type Intelligence splits VoIP into two values. "fixedVoip" is a virtual number associated with a physical device, such as Comcast or Vonage. "nonFixedVoip" is a virtual number obtained online without a physical device, such as Google Voice. "mobile" stays its own separate type (accessed July 18, 2026).
What this means for you: the same lookup that separates two flavors of VoIP keeps mobile in a category of its own. SLYNUMBER numbers land in that mobile category. The bank reads the type field. Your call's transport never comes up.
5. Mobile vs VoIP compared across both axes
Here's the same set of numbers laid out across both axes, transport and classification. The table also shows the lookup value and the verification outcome.
| Number | Classification on record | Transport it can use | Twilio lookup value | Verification outcome |
|---|
| SLYNUMBER | Mobile (HLR subscriber record) | Internet (TLS/SRTP) to the app | mobile | Passes strict checks |
|---|
| Carrier mobile line | Mobile (HLR subscriber record) | Cellular, VoLTE, or Wi-Fi Calling over IP | mobile | Passes strict checks |
|---|
| Non-fixed VoIP (Google Voice) | VoIP provider number block | Internet (IP/SIP) | nonFixedVoip | Refused by strict checks |
|---|
| Fixed VoIP (home internet phone) | VoIP tied to a physical device | Internet (IP/SIP) | fixedVoip | Often refused |
|---|
Quick recap: read the classification column and the transport column separately. SLYNUMBER and a carrier line both use IP transport for at least some calls, and both are classified mobile, so both pass. The two VoIP rows also use IP transport, but their classification is VoIP, and they fail. Every row shares roughly the same transport. Classification alone decides which rows pass.
6. Where SLYNUMBER sits on both axes
Classified mobile, delivered over the internet
SLYNUMBER provisions real U.S. mobile numbers from the NANP and registers them as mobile lines in carrier databases. On the classification axis, a lookup returns mobile. On the transport axis, delivery of calls and messages to the app runs over the internet. Messages use Transport Layer Security (TLS), the encryption that protects online banking, and voice uses Secure Real-Time Transport Protocol (SRTP). Both facts hold at the same time, and a verifier only ever checks the classification. So the accurate description is a real mobile number, delivered over internet transport, that passes where VoIP-classified numbers fail.
None of this record-keeping is a SLYNUMBER quirk. It's how the whole industry operates. The GSMA maintains a document each operator keeps current with its numbering ranges. That again shows the mapping of numbers to operators is an administrative record rather than a transport fact.
Pricing
Plans start at $4.99 per month billed as $14.99 every three months, with an annual plan at $49.99 per year. Register at slynumber.com/app/register. The same classification logic drives why banks reject VoIP in the first place, covered in why banks block VoIP numbers. It applies to fintech signups like Cash App.
GSMA IR.21 is the reference document each mobile operator keeps current with its numbering ranges in service. It confirms the mapping from numbering ranges to operators is a maintained administrative record (accessed July 18, 2026).
7. Frequently asked questions
Sometimes the lookup is just wrong. Carriers move numbers between blocks, port them, and reassign ranges. Lookup databases don't always catch up, so a genuine mobile number can come back as VoIP. T-Mobile customers have reported this on the carrier's own forum. Your number hasn't changed; the database is behind, and the record can usually be corrected.
No. They're different classifications in carrier and regulatory records. A mobile number is tied to a live subscriber record, an IMSI-to-MSISDN binding in an HLR. A VoIP number is assigned to a VoIP provider's number block. When a service decides whether to send you a code, it reads that classification rather than the audio path.
Yes. Modern mobile calls over VoLTE and Wi-Fi Calling travel the internet as IP packets. The number stays classified as mobile because its administrative record hasn't changed. Classification and transport are recorded separately. SLYNUMBER works the same way: delivery happens over the internet while the number remains a real mobile line.
They run a lookup against administrative records. Nobody listens to a call. Twilio Lookup, for example, returns a type field of mobile, landline, fixedVoip, or nonFixedVoip, sourced from carrier and numbering data. The service branches on that value. Whether your last call used a cell tower or Wi-Fi never enters into it.
SLYNUMBER issues real U.S. mobile numbers registered as mobile lines in carrier databases. A lookup returns mobile and verification-strict services accept them. Delivery to the app travels over the internet using TLS and SRTP, but that's transport; it doesn't change the classification. In the carrier record a service checks, the number is mobile.
