Phone Number Validator — bulk E.164 formatter with carrier, line type and location

Validate and clean phone numbers in bulk: any format to E.164, validity per country, line type (mobile, landline, VoIP, toll-free), carrier, city/region, time zone and duplicate removal. Runs offline on Google's libphonenumber data — no login, no API key, no proxies, results in seconds. Export as JSON, CSV or Excel.

How to use in 3 steps

1. Paste your numbers — one per line, any format ((415) 555-2671, +44 20 7946 0958, tel:+81-3-1234-5678, 0033 1 42 68 53 00, ... ext. 12).
2. Set a default country (e.g. US, GB, JP) for numbers written without a + prefix.
3. Run and export — every number gets a status (valid, risky, invalid), a plain-English reason and clean formats.

What you get

• Format normalisation to E.164 (+442079460958), international, national and RFC 3966 (tel:) forms. Labels like Tel: and a leading 00 are handled.
• Validity per country from libphonenumber's numbering plans (not just a length check). risky means the length fits but the number is not in an allocated range — usually a typo.
• Line type: mobile, fixed_line, fixed_line_or_mobile, toll_free, premium_rate, voip, shared_cost and more — split mobile numbers for SMS from landlines.
• Location and carrier (original carrier of the number range; names in your chosen language) and time zones.
• Smart de-duplication — (650) 253-0000 and +1 650 253 0000 count as the same number.
• Fast — nothing is fetched over the network, 100,000 numbers take seconds.

Output

Field	Example
input	090-1234-5678
status	valid / risky / invalid
reason	Valid number for its region
isValid, isPossible	true, true
e164, international, national, rfc3966	+819012345678, +81 90 1234 5678, 090-1234-5678, tel:+81-90-1234-5678
countryCode, regionCode, country	81, JP, Japan
location, carrier	Tokyo, KDDI Japan (null when unknown)
lineType	mobile
timezones	["Asia/Tokyo"]
extension	12 or null

{
  "input": "090-1234-5678",
  "status": "valid",
  "reason": "Valid number for its region",
  "isValid": true,
  "isPossible": true,
  "e164": "+819012345678",
  "international": "+81 90 1234 5678",
  "national": "090-1234-5678",
  "rfc3966": "tel:+81-90-1234-5678",
  "countryCode": 81,
  "regionCode": "JP",
  "country": "Japan",
  "location": null,
  "carrier": "KDDI Japan",
  "lineType": "mobile",
  "timezones": ["Asia/Tokyo"],
  "extension": null
}

e164 and the other formats are null for numbers that cannot be formatted (invalid). lineType, carrier, location and timezones are filled only for valid numbers. Carrier data is the range's original allocation: it does not reflect number porting, and the Actor does not check whether a line is currently active or reachable.

Input examples

Check a US list:

{ "phoneNumbers": ["(415) 555-2671", "+1 650 253 0000", "12345"], "defaultCountry": "US" }

Get only the clean mobile-ready numbers, with Japanese place names:

{ "phoneNumbers": ["090-1234-5678", "03-3581-4111"], "defaultCountry": "JP", "outputFilter": "valid", "language": "ja" }

Get only the numbers to clean out:

{ "phoneNumbers": ["+44 20 7946 0958", "+44 20 7946", "abc"], "outputFilter": "problems" }

Use cases

• Clean a CRM or lead export before an SMS or call campaign.
• Convert mixed local formats to E.164 for Twilio, WhatsApp or dialer imports.
• Split mobile from landline and toll-free numbers.
• Pair with an email check: see Email List Validator from the same publisher.

FAQ

Does it call the number or check if it is active? No. It validates against numbering plans offline; it cannot tell whether a line is connected.

Why is the carrier empty? Carrier names exist only for some countries (e.g. Japan, UK, India), and show the original carrier, not the current one after porting.

What does a number without + need? Set Default country. Numbers starting with + or 00 ignore it.

Where does the data come from? The open-source libphonenumber metadata (Apache License 2.0) via the Python port phonenumbers, updated with each Actor build.

Limits

Up to 200,000 numbers per run. Results depend on the libphonenumber release in the build; new number ranges can lag by weeks.

Pricing

Free to use — you only pay Apify's standard platform usage.