Calling code is not always a country
Some calling codes are shared. +1 covers the North American Numbering Plan, and +7 is shared by Russia and Kazakhstan. A prefix match can identify a calling plan without proving one country.
International reference
Country calling code lookup
Enter a calling code or full international number to find its supported calling plan, or browse by country.
Look up a code or country
Country or calling plan
Calling code
National pattern
Typical national length
E.164 example
How to dial internationally
Replace the domestic international-access prefix with +, add the country calling code, and normally remove the domestic trunk prefix. Exact rules vary by country and service.
Do not remove every leading zero
A domestic trunk zero is commonly removed before an international code, but the rule is not universal. Italian geographic numbers are a well-known reason to parse with country metadata instead of a global string replacement.
Use current sources
Country guides link to regulators, numbering administrators or ITU references. Check those sources or a maintained library before enforcing rules in production because allocations and lengths can change.
Example lookup workflow
- Keep the leading
+or convert an international access prefix such as00. - Match the longest supported calling code, not only the first digit.
- Use the remaining national digits and selected country context to resolve shared plans.
- Format for display only after storing one canonical representation.
When lookup results are ambiguous
A calling-code lookup can identify a supported numbering plan, but it should not pretend to know more than the digits reveal. Shared plans are the common trap. +1 covers the United States, Canada and several Caribbean countries or territories. +7 is also shared. A product that needs a billing country, tax country or compliance region must use verified account data or explicit user selection instead of treating a calling code as legal identity.
The same caution applies to area and mobile prefixes. A prefix may suggest a region or service type, but number portability, reassignment and plan updates can weaken that signal. Use prefix lookup for formatting help and QA fixtures; use authoritative provider or regulator data for decisions that affect delivery, billing or access.
How to use this reference in documentation
For API docs, show the country calling code, one national display example and one E.164 example together. For support articles, explain whether users should enter the domestic trunk prefix or the international + form. For QA specs, link to the exact country guide so a future reviewer can see the source note and the fixture safety label instead of copying an example with no context.
If you maintain a design system, keep the country selector, calling-code display and validation messages aligned. A user should never see one country in the dropdown, another calling code in the placeholder and a third interpretation in the saved profile.
Maintenance notes for calling-code data
Calling codes are relatively stable, but national patterns, mobile prefixes and regulator links can change. Treat this lookup as a maintained reference, not a permanent legal source. When a country guide is updated, check the dataset record, the widget output and the examples used in documentation together. That keeps users from seeing an old example in one place and a newer E.164 fixture somewhere else on the site.
For product documentation, add the date of your last review beside any copied example. For automated tests, keep the fixture source in version control. A future change in a regulator table or library metadata should be reviewed as a data update, not as a mysterious bug in the calling-code lookup itself.
If a support workflow depends on the result, cite the country guide rather than copying only the code. That gives reviewers a source, a safety label and the exact fixture context.
For user-facing forms, show both country name and calling code together. A calling code displayed alone is easy to misread and may be shared across multiple regions.