The tool normalizes pasted phone numbers, handles common international dialing prefixes and extensions, and parses them with Google libphonenumber metadata. When parsing succeeds it shows region, country code, number type, and E.164, international, national, and RFC 3966 formats.
Use the recommended international format when sharing a number across countries, E.164 for storage and APIs, national format for local display, and RFC 3966 for tel links. Passing validation only means the number is structurally plausible; it does not prove assignment, ownership, consent, carrier status, or reachability. The entered number stays out of the page URL.
Common questions and answers about this topic.
A valid result means the length and number pattern are structurally plausible for the detected region according to Google libphonenumber metadata. It is a formatting and numbering-rule check, not a live verification of the line.
Select the country or region whose numbering rules should apply. If the number includes an international calling code such as +886 or +34, libphonenumber also resolves that code and reports the detected region so you can spot a mismatch.
E.164 is the compact +country-code form used for storage and APIs. International and national formats are human-readable dialing styles, while RFC 3966 produces a tel: URI suitable for links and structured data.
Yes. The parser normalizes common prefixes such as +, 00, and 011, and recognizes common extension forms including ext, x,
Select the number's country or region and enter the local number. The recommended international result adds the correct calling code and spacing for people to read; choose E.164 in the technical details when you need a compact value for storage or an API.
No. It does not call the number, send an OTP, query carrier status, or identify an owner. Passing the check cannot prove assignment, reachability, ownership, or consent; confirm those facts with the carrier or recipient before use.