Skip to content
Free single-number lookup

Phone Number Validator
Check Any Phone Number Free

Check a mobile, fixed-line, or VoIP number and view available carrier, country, location, formatting, and timezone metadata. Need caller-name data instead? Explore the Caller ID service.

No signup
For the free checker
GET + POST
For API integrations
1 credit
Per successful API check
A clear JSON result
Validation status plus available metadata
{
  "status": "VALID_CONFIRMED",
  "linetype": "Mobile",
  "carrier": "Example Carrier",
  "countrycode": "US",
  "timezone": ["America/Los_Angeles"]
}

Enter a phone number to check

Choose the country, enter one number, and review the validation result—no account required.

9 free checks per IP daily
No signup for this tool
Mobile, fixed-line & VoIP
One number per check
What you can check

Useful phone metadata, without the guesswork

Use the free checker for an occasional lookup or add the same validation workflow to your product with the REST API.

Validation Status

Receive a clear VALID_CONFIRMED or INVALID result and standardized formatting when available.

Line Type

Classify the number as Mobile, Fixed Line, VoIP, Toll-Free, Premium Rate, Pager, or another supported type.

Carrier Metadata

See the carrier or telecom operator value returned for the number when that enrichment data is available.

Location & Timezone

Review available country, location, country-code, national-format, international-format, and timezone fields.

REST API

Send GET or POST requests and integrate with JavaScript, Python, PHP, cURL, or any HTTP-capable platform.

WordPress Option

Add ProWebLook-powered phone validation to WordPress without building the complete integration from scratch.

Choose your workflow

One service, two straightforward ways to use it

Start with a manual check, then move to the API when validation becomes part of your product.

Free single-number checker

Best for quick checks when you do not need to automate the process.

  1. Select the number's country and enter the phone number.
  2. Submit the check without creating an account.
  3. Review the returned status and available metadata.
Use the free checker

Phone Validation API

Best for sign-up forms, CRM cleanup, lead workflows, and server-side validation.

  1. Create an account and use your ProWebLook API key.
  2. Send a full international number or a local number with a country hint.
  3. Use the status, metadata, and rate-limit fields in your application.
See API examples

Prefer WordPress?

Install the ProWebLook Phone Validator plugin and connect phone validation to your WordPress workflow.

View WordPress Plugin
Read the result correctly

What “valid” means—and what it does not

Validation is telecom metadata. It is not the same as contacting the number or verifying its owner.

VALID_CONFIRMED

The provider recognized the number as valid

The result can include formatting and enrichment such as line type, carrier, location, country, and timezone.

INVALID

The provider did not validate the number

Use this result to flag a number for correction or review. It is a completed validation result, not an API error.

Important limit

Neither status proves reachability or ownership

The checker does not place a call, send an OTP, detect spoofing, or prove that a person controls the number.

Line-type guide

Understand the number behind the format

Line type describes the telecom service category. It can guide routing or form rules, but it should not be used as a standalone risk decision.

Mobile

A cellular number typically associated with a mobile service.

Fixed Line

A traditional landline associated with fixed telephone service.

VoIP

A number delivered through internet-based voice infrastructure.

Toll-Free

A service number where the receiving organization usually pays call charges.

Premium Rate

A service category that can carry higher-than-standard calling charges.

Unknown

The number may validate while a more specific line category is unavailable.

More API values: Fixed Line or Mobile, Shared Cost, Personal Number, Pager, Universal Access Number, and Voicemail can also be returned.
Phone validation pricing

Choose credits for your validation volume

The calculator below uses the current product catalogue, so you can compare available phone-validation options without relying on hard-coded plan claims.

Flexible & Competitive Plans

Choose how you pay, pick your credit tier, and checkout with live Stripe or PayPal links.

Phone validator FAQ

Answers before you build

Clear guidance on results, line types, API usage, international numbers, and the limits of validation.

It checks the submitted number against supported numbering metadata and returns VALID_CONFIRMED or INVALID. When available, the result can also include the formatted number, line type, carrier, location, country, and timezone.
Yes. The public checker allows up to 9 single-number checks per IP address each day, with no account required. API usage is credit based; current options are shown in the pricing section.
Line type describes the telecom category assigned to a number, such as Mobile, Fixed Line, VoIP, Toll-Free, or Premium Rate. It is infrastructure metadata, not a trust or fraud score.
Yes. VoIP is one of the line-type values the API can return. Other possible values include Fixed Line, Mobile, Toll-Free, Pager, Voicemail, and Unknown.
An INVALID result is a useful signal that the provider could not validate the number. It can help catch formatting mistakes or unsupported number ranges, but it should not be treated as definitive proof of fraud.
No. VALID_CONFIRMED does not prove that a device is switched on, that a call or message will connect, or that the person who submitted the number currently controls it.
Phone validation focuses on number metadata, not ownership. If you need caller-name information, use the ProWebLook Caller ID service and review its available result fields separately.
The API can return a carrier value when that metadata is available. Carrier information may be empty for some results and should not be assumed to identify the subscriber.
Yes. Send a full international number, preferably in E.164 format, or send a local number with a two-letter ISO country hint such as IN, US, or GB.
There is no dedicated bulk-upload endpoint on this page. For a list of numbers, call the Phone Validation API once per number from your application and observe the rate-limit fields returned by the API.
Yes. The endpoint accepts both GET and POST requests at https://lookup.proweblook.com/api/v1/phonevalidation. Each successful validation uses one phone validation credit.
Results depend on the numbering and carrier metadata available for the submitted number. Coverage and enrichment fields can vary, so validation should be one signal in your workflow rather than a guarantee of reachability or ownership.
Validation checks number structure and available telecom metadata. Verification usually proves control by sending an OTP or placing a call. This validator does not send an OTP and does not verify the owner.
Yes. Submit the full international form, such as +1... or +44..., or use a national number together with the country hint US or GB.
No. Number validation checks the number you submit; it does not inspect a live call and cannot determine whether caller ID information was spoofed.
Yes. The public single-number checker works without an account, subject to the 9-check daily IP limit. An account and API key are required for programmatic API access.
Developer reference

Phone Number Validation API

Use the same validation service in your application with GET or POST requests and a simple JSON response.

API Quick Reference

EndpointGET / POST https://lookup.proweblook.com/api/v1/phonevalidation
AuthenticationGET: send api_key in the query string. POST: send api_key in a JSON or form body.
Phone numberphone_number is required. Without country_code, send a full international number containing the country calling code, preferably E.164 (for example, +14155552671). URL-encode the leading + as %2B in GET URLs.
Country hintcountry_code is optional. A local or national number requires a two-letter ISO 3166-1 alpha-2 hint, for example phone_number=9876543210&country_code=IN. This parameter is IN, not the numeric calling prefix +91. Omission or none enables detection from a full international number.
ResultJSON with status: VALID_CONFIRMED or status: INVALID. An invalid number is a completed validation result, not an API error.
Cost1 phone validation credit from your phone credit pool per successful validation.
# Full international number; no country_code needed
curl "https://lookup.proweblook.com/api/v1/phonevalidation?api_key=YOUR_API_KEY&phone_number=%2B14155552671"

# Local/national number; country_code is required
curl "https://lookup.proweblook.com/api/v1/phonevalidation?api_key=YOUR_API_KEY&phone_number=9876543210&country_code=IN"

Response fields

Only status is guaranteed for every completed validation. Enrichment fields can be absent when status is INVALID.

FieldTypeDescription
statusstringVALID_CONFIRMED or INVALID
formatted_numberstringInternationally formatted phone number
linetypestringMobile, Fixed Line, Fixed Line or Mobile, Toll-Free, Premium Rate, Shared Cost, VoIP, Personal Number, Pager, Universal Access Number, Voicemail, or Unknown
carrierstringCarrier/operator name when available; it may be empty
locationstringCity, region, or country description
countrycodenumintegerNumeric country calling code, such as 1, 44, or 91
countrycodestringISO 3166-1 alpha-2 country code
countrynamestringFull country name
formatnationalstringNational display format
formatinternationalstringInternational display format
timezonearrayApplicable IANA timezone strings
ratelimit_remainintegerCalls remaining in the current rate-limit window
ratelimit_secondsintegerSeconds until the rate-limit window resets

Valid and invalid results

{
  "status": "VALID_CONFIRMED",
  "formatted_number": "+1 415 555 2671",
  "linetype": "Mobile",
  "carrier": "T-Mobile",
  "location": "California",
  "countrycodenum": 1,
  "countrycode": "US",
  "countryname": "United States",
  "formatnational": "(415) 555-2671",
  "formatinternational": "+1 415 555 2671",
  "timezone": ["America/Los_Angeles"],
  "ratelimit_remain": 100,
  "ratelimit_seconds": 100
}

{
  "status": "INVALID"
}

API errors

HTTPMeaning
400Required parameter missing or invalid
401API key missing or invalid
402Insufficient phone credits
500Unexpected server error

Error responses contain an error string, for example {"error":"Invalid API key."}

Read the official API reference

Ready to add phone validation to your workflow?

Create an account for API access, or review the endpoint details before you start building.