Phone Number Validator

Validate a phone number by country: E.164, international and national formats, line type.

Loza CRM·Updated: October 2, 2026

Quick answer

Paste a number — get validity, country, E.164 format and line type. For local numbers, set the default country. Validation runs entirely in your browser.

How to use

  1. Paste a number — international or local format
  2. For a local number, set the default country (US, BR, IN…)
  3. Read the verdict: valid / invalid / unparseable
  4. Copy the E.164 output — the canonical format for CRM imports and lead APIs

Why you need it

Phone validation matters anywhere leads flow into a CRM: a malformed number is a lost lead or a rejection from the broker's dialer. This tool runs on libphonenumber-js — a port of Google's libphonenumber, the same library that validates numbers on Android. It checks real numbering plans, not just digit count.

The output goes beyond a yes/no. You get the E.164 form (+16502530000 — the only format that survives APIs, dialers and SMS gateways), the international and national representations, the detected country, and the line type where the metadata supports it — mobile, fixed line, toll-free and so on.

For affiliate work the practical scenario is list hygiene. A CSV of sweepstakes leads arrives with a mix of local formats, missing country codes and plain garbage. Running it through a validator before import separates usable leads from ones that will bounce off the broker's form validation — and the E.164 output gives you a single canonical format to store.

Local numbers are supported too: set the default country and the tool parses the number under that country's rules — a US "(650) 253-0000" resolves to +16502530000 without you typing the +1. Everything runs client-side: no number you paste here leaves the browser.

Loza CRM computes these metrics for your campaigns automatically — try it free.

Open Loza CRM

FAQ

What is E.164 format?
The international standard for phone numbers: plus sign, country code and digits with no spaces — +16502530000. It is the only format that works reliably across CRMs, dialers and SMS APIs.
Why does a "looks fine" number fail validation?
The library checks real numbering plans — valid area codes, in-country number length, reserved prefixes — not just digit count. A plausible-looking number in a non-existent range is rejected.
Can it validate local numbers without a country code?
Yes — set the default country and the number is parsed under that country's rules, e.g. a US local number resolves to its +1 E.164 form.
Does the number get sent to a server?
No. Validation runs fully in your browser — the number never leaves the page.
Does it detect mobile vs landline?
Where the metadata supports it, the tool reports the line type — mobile, fixed line, toll-free and others.

Other tools