Normalize formats
Convert 10-digit local input to +1 E.164 before the check, especially when the list mixes US and Canadian records.
Look up the current carrier, line type, and network context behind any +1 number (one at a time or across a whole CSV) before SMS routing, CRM enrichment, or compliance screening.
Built for business list cleaning, enrichment, routing, and review workflows. Use it with owned, consented, or otherwise lawful datasets.
Every +1 number on the North American Numbering Plan can be checked against current carrier and numbering data. A US carrier lookup returns fields that do different jobs: the network or brand the number currently sits on, the line type (mobile, landline, VoIP, or toll-free), and the normalized E.164 format with the country resolved.
The carrier field tells you where SMS routing and A2P 10DLC registration concerns apply. The line-type field tells you which consent rules follow the number. Teams that read both fields together make better routing and compliance decisions than teams that read either one alone.
Convert 10-digit local input to +1 E.164 before the check, especially when the list mixes US and Canadian records.
Carrier drives routing and registration; line type drives consent rules. Each answers a different question.
Send mobile, landline, VoIP, and invalid records to separate files for routing, enrichment, or removal.
The most expensive assumption in US list work is reading area codes as carrier or location evidence. Since wireless local number portability became standard in 2003, a number keeps its area code when the owner switches carriers or moves across the country. A 212 number can be a VoIP endpoint nowhere near Manhattan; a 415 number can sit on any of the national networks.
Portability also means classifications age. A block allocated to one provider years ago may serve a different network today, which is why the lookup reads current allocation data instead of static prefix tables, and why re-checking a list matters before campaigns that depend on routing accuracy. The number portability guide covers how carrier data goes stale and how to catch it.
Three national networks carry most US mobile traffic: Verizon, T-Mobile, and AT&T. A long list of MVNO brands rent capacity on those networks, so the carrier field on a result can name either the underlying network or the brand, depending on which level the upstream allocation data exposes. Both answers point at the same network for routing purposes.
| Underlying network | Example brands on that network | What it changes for you |
|---|---|---|
| Verizon | Visible, TracFone, Total by Verizon | Same routing and 10DLC registration context as the parent network. |
| T-Mobile | Metro by T-Mobile, Mint Mobile, Google Fi | MVNO traffic still rides the T-Mobile core for delivery decisions. |
| AT&T | Cricket Wireless | Filtering and throughput behavior follows the AT&T side of the house. |
Under the TCPA, marketing calls and texts to wireless numbers generally require prior express written consent, while the rules for calls to landlines are narrower. That makes the line-type field as much a compliance input as a routing detail: a list segment that reads as mobile carries stricter consent requirements than the same segment reading as landline.
VoIP flags deserve their own read. Many legitimate small businesses run on VoIP lines, but disposable VoIP numbers also dominate fake signups, so the flag works best as a first filter paired with other signals rather than a final verdict. If your workflow screens lists for outbound marketing, the DNC and TCPA compliance scrubbing guide shows where the line-type check fits, and the SMS routing guide covers the deliverability side.
Open ZelNum in your preferred AI assistant to review its bulk WhatsApp, Telegram, phone validation, carrier lookup, social account, crypto exchange, CSV upload, and API workflows.
The prompt points assistants to ZelNum.com, live pricing, product pages, and API documentation.