What the phone checker looks at
A phone number can look correct and still be useless. It may have the wrong length for its country, belong to a range that was never allocated, or sit on a virtual line that anyone can create in minutes. This tool checks the number against numbering-plan rules and phone data, then returns a structured result you can read at a glance. It is built on the same checks as the Phone Validate API.
Enter the number with its country code (for example +44 or +1), or select a country and enter it in national format. Local formats without a country are the most common cause of false "invalid" results.
Result fields explained
Each field answers a different question. Some fields depend on the country and on what data exists for that number range, so a blank field means "not available", not "bad number".
| Field | What it tells you | How to use it |
|---|---|---|
| Validity | Whether the number is possible and plausible for its country's numbering plan. | Reject or ask for correction at the form, before storing the number. |
| Country | The country or region the number belongs to. | Compare with the customer's stated country or IP location and flag mismatches. |
| Line type | Mobile, landline or VoIP, where it can be determined. | Route SMS only to mobiles; treat VoIP as a risk signal, not an automatic block. |
| Carrier | The network operator associated with the number, where data is available. | Useful context for review; do not treat it as proof of identity. |
| Formats | The number normalised into international (E.164), international display and national formats. | Store one canonical format so duplicates and lookups match. |
Why line type matters for fraud and SMS delivery
Line type is the field most teams underuse. It affects two separate problems.
Delivery
One-time passcodes and notifications are normally sent by SMS. A landline cannot receive a standard text, so a user who enters one will never get the code. Catching that at the form saves a failed send and a support ticket.
Fraud
VoIP numbers are cheap to obtain in volume, which makes them attractive for creating many accounts, claiming promotions repeatedly or avoiding a link to a real SIM. That does not make every VoIP user a fraudster: plenty of legitimate people use virtual numbers for privacy or work. The practical approach is to treat VoIP as one input. Allow it for low-risk actions, and step up verification when it appears alongside other warning signs such as a new device, a mismatched country or a disposable email address (see the free email validator for that side of the check).
Porting and SIM-swap risk
Number porting and SIM swaps matter because a phone number is often used as a second factor. If a fraudster takes control of a number, SMS codes go to them. Whether recent-port or SIM-change information is available depends on the country and the data source, so this tool does not assume it. Check the Phone Validate product page for the data currently returned, and do not rely on a phone check alone to protect high-value actions such as account recovery or payouts. Our guide to account takeover fraud covers the wider controls.
Limits of a phone check
- Valid is not owned. A valid, active-looking number does not show that the person submitting it controls it or that it belongs to them. Only an OTP or a similar possession check does that.
- Line type and carrier can be incomplete. Coverage varies by country and number range, and the data reflects the source at the time of the lookup.
- Virtual and mobile lines blur. Some services issue numbers that behave like mobiles, so line type is a signal, not a verdict.
- It is not identity verification. To tie a person to a document or biometric check, use identity verification.
Combining phone, email and other signals into one decision is a separate topic. It is covered in Email and Phone Risk Scoring Explained and, at the policy level, in risk decisioning.
Validate numbers at sign-up with the API
The web tool is for spot checks. To check every number as it is entered, call the Phone Validate API from your sign-up or checkout flow, then act on the response: correct the format, block impossible numbers, send OTPs only to suitable line types and route risky combinations to review. You can sign up on ScreenlyyID to get started, and see pricing for plans.
Below is an illustrative response. Field names are simplified for explanation; the product page and API documentation show the exact schema.
{
"valid": true,
"country": "GB",
"line_type": "mobile",
"carrier": "Example Mobile",
"formats": {
"e164": "+447700900123",
"national": "07700 900123"
}
}
Phone checks sit within the wider fraud detection toolkit, alongside email validation and IP and device intelligence. The fraud detection and compliance product brings these together.
Phone data is personal data in most jurisdictions. Check the rules that apply to your business, such as consent and retention, with your regulator or legal counsel. This page is information, not legal advice.
Frequently asked questions
What does a phone number validator show?
It shows whether a number is valid for its country, the country it belongs to, the line type (mobile, landline or VoIP) and the carrier where data is available. It also returns the number in standard formats such as E.164. Fields can be blank when no data exists for that number range.
Is this phone checker free?
Yes, the web tool on this page is free to use for checking individual numbers. If you want to check numbers automatically inside your own sign-up or checkout flow, you use the Phone Validate API after creating an account. See the pricing page for current plans.
Can it tell mobile from VoIP?
Where line type data is available for the number, yes. It reports mobile, landline or VoIP. Treat the result as a signal rather than a verdict, because coverage varies by country and some services issue numbers that behave like mobiles.
Does it call or text the number?
No. The check uses numbering-plan rules and phone data, so the number is not rung and no message is sent. That also means it cannot prove the user controls the number. For that you need a one-time passcode or similar possession check.
Can I validate numbers in bulk or by API?
Yes, the Phone Validate API is designed for checking numbers programmatically, for example at sign-up or checkout, and it has a self-serve sign-up. For large existing lists or high volumes, contact the ScreenlyyID team to discuss the best approach.