Routing and CPaaS teams
Use carrier and MCC/MNC data to decide which aggregator should handle a message, detect ported numbers, and keep network-specific routing rules current.
Carrier Intelligence
Carrier metadata for routing, fraud, and customer verification
Carrier intelligence identifies the network behind a phone number and turns that signal into operational context. Carrier Reveal combines carrier lookup, line type detection, number portability awareness, caller name, SIM pumping risk, and Identity Match into one tokenized flow. Teams can preview format for free, pay only when they need full metadata, and reuse unlocked hashes without storing the raw number.
What is carrier intelligence?
Carrier intelligence is the set of live and derived phone-number signals that explain where a number can be reached, what kind of line it is, and whether it carries risk. It is different from simple formatting because it answers questions such as which network owns this number now, whether the number can receive SMS, and whether a line type should trigger a fraud or compliance rule.
What data can an unlock include?
The exact payload depends on country support and provider availability, but the workflow is designed to keep carrier, line type, risk, and identity context together instead of forcing teams through separate tools.
Current carrier and network operator
Line type such as mobile, landline, VoIP, or toll-free
Mobile country code and mobile network code
Mobile number portability context
Caller name and caller type when available
SIM pumping risk score and blocking signals
Identity Match attempts for supported countries
Normalized E.164 format for clean exports
How the lookup workflow stays clean
Validate the number
Carrier Reveal first normalizes the input with country-aware parsing. Invalid formats stop at preview, so teams can clean CRM data without creating a paid unlock.
Create a lookup token
The service hashes normalized numbers and passes lookup tokens through checkout. Payment sessions never need to expose raw numbers to Stripe or PayPal metadata.
Reveal the carrier payload
After payment, the unlocked result returns carrier data, risk context, and supported identity fields. The hashed unlock stays reusable in a signed cookie for 90 days.
Where teams use carrier metadata
A carrier lookup is most useful when it feeds a decision: route the message, block the risky signup, clean the CRM record, or help a support agent understand why verification failed.
Fraud and trust teams
Combine VoIP detection, SIM pumping risk, line type, and identity match evidence before approving signups, payouts, password resets, or high-risk checkout events.
Revenue and CX teams
Prioritize reachable mobile contacts, avoid sending SMS to landlines, and give support agents enough carrier context to resolve verification issues quickly.
Privacy model
Carrier Reveal treats phone numbers as sensitive input. The lookup flow normalizes numbers, hashes them, and stores unlock state in signed cookies. Payment providers receive lookup tokens rather than raw digits, and successful payment consumes the session token so the same unlock cannot be replayed.
Review security detailsWhen to unlock
Use the free preview for data entry, country selection, and formatting checks. Unlock when the carrier result will change an operational decision: whether to send SMS, whether to allow a payout, whether a line should be routed through a specific provider, or whether a customer-support case needs more context.
Learn how to identify carrier by numberUse the home page for lookup. Use this page for the details.
The main screen stays focused on the lookup tool. This guide carries the deeper carrier intelligence explanation, so buyers, search engines, and answer engines can still find the context without crowding the product workflow.