Phone Number Validator: US State, Time Zone & Line Type

Validate, clean and enrich phone numbers in bulk. Paste numbers in any format, such as (512) 474-5171, 512.474.5171, +1 212 736 5000 ext. 12 or +44 20 7946 0958, and get back the E.164 format, national and international formats, line type (mobile, landline, toll-free, premium-rate…), and, for US and Canadian numbers, the state/province, city, time zone, the recipient's current local time and a TCPA calling-hours check.

Works offline with Google's libphonenumber metadata: no API key, no per-lookup fees, thousands of numbers per second.

Why this phone validator?

• ☎️ Any input format: parentheses, dots, dashes, spaces, 1- prefixes, tel: links and extensions (ext. 12, x12)
• 🌐 E.164, national, international and RFC 3966 (tel:) formats, ready for CRMs, dialers, Twilio and SMS tools
• ✅ Valid / invalid with a reason: wrong_length, invalid_for_region, fictional_555_number, not_a_phone_number
• 🇺🇸 US & Canada enrichment: area code, city-level location ("Austin, TX"), state code and name, IANA time zone
• ⏰ TCPA-friendly calling window: recipient's local time and isWithinCallingHours (8 am–9 pm by default, configurable)
• 📞 Line type: toll-free, premium-rate, personal numbers, and mobile vs. landline outside the US (US numbers share ranges, so they are reported as landline_or_mobile)
• 🧹 Deduplication on the normalized number (duplicates are free) and an "only valid" mode
• 🔗 Chains with other actors: validate the phone field of any Apify dataset by its ID
• 🌍 International support: every country's numbering plan, with a configurable default country

Use cases

• Sales & call centers: route leads to reps by time zone and only dial inside legal calling hours
• CRM & marketing ops: normalize every number to E.164 before importing into HubSpot, Salesforce, Twilio or SMS platforms
• Lead generation pipelines: clean phones from scraped leads (e.g. our FMCSA trucking leads or SEC Form D funding leads)
• Data quality & forms: catch fake, fictional (555) and malformed numbers
• Territory analysis: count leads by state or time zone

How to use it

1. Click Try for free. Sample numbers are prefilled, so the first run works in one click.
2. Paste your numbers (one per line), or pick an Input dataset (e.g. a lead scraper's output) and set the Phone field.
3. Click Start and export CSV, Excel or JSON, or call it through the Apify API, Zapier, Make or n8n.

Input example

{
    "phoneNumbers": ["(512) 474-5171", "212.736.5000", "1-800-275-2273", "+44 20 7946 0958"],
    "defaultCountry": "US",
    "callingHoursStart": 8,
    "callingHoursEnd": 21,
    "dedupe": true,
    "onlyValid": false
}

Output example

{
    "input": "(512) 474-5171",
    "isValid": true,
    "isPossible": true,
    "reason": null,
    "e164": "+15124745171",
    "nationalFormat": "(512) 474-5171",
    "internationalFormat": "+1 512 474 5171",
    "rfc3966": "tel:+15124745171",
    "extension": null,
    "countryCode": "US",
    "countryCallingCode": "+1",
    "areaCode": "512",
    "lineType": "landline_or_mobile",
    "isTollFree": false,
    "isMobileCapable": true,
    "location": "Austin, TX",
    "city": "Austin",
    "state": "TX",
    "stateName": "Texas",
    "timeZones": ["America/Chicago"],
    "timeZone": "America/Chicago",
    "localTime": "Thu 11:00",
    "utcOffset": "UTC-5",
    "isWithinCallingHours": true
}

Pricing

Pay-per-event: a tiny start fee plus a fixed price per number saved, currently about $0.72 per 1,000 numbers (see the Pricing tab). There is no compute charge on top. Duplicates are removed for free, and with Output only valid numbers you pay only for valid ones. Cap any run with maxItems.

FAQ

Does it tell me if a US number is a cell phone? In North America, mobile and landline numbers share the same number ranges, and numbers can be ported between carriers. No offline database can tell them apart, so US/Canada numbers are reported as landline_or_mobile (isMobileCapable: true). Toll-free, premium-rate and personal (5XX) numbers are identified exactly. For other countries mobile vs. landline is reported.

Does it check if the number is in service? No. There are no network lookups (HLR/CNAM). The actor validates against the official numbering plan, which catches wrong lengths, unassigned area codes, fictional 555 numbers and junk.

Where do location and time zones come from? From Google's open-source libphonenumber geocoding and time-zone data (Apache 2.0), matched on the area code plus exchange (up to 7 digits) for city-level accuracy. Area codes spanning several time zones return all of them in timeZones.

Is isWithinCallingHours legal advice? No. It is a convenience flag based on the recipient's local time. Always follow the TCPA, state laws and Do-Not-Call rules.

Questions or bugs? Use the Issues tab. The actor is monitored daily.

Related actors by WAAGS

• Bulk Email Validator: syntax, MX, disposable, role and typo checks
• FMCSA Trucking Carrier Leads · SEC Form D Funding Leads · SAM.gov Contract Opportunities

Location and time-zone data © Google, from libphonenumber, Apache License 2.0.