Country Information Lookup

{{ summaryTitle }}

{{ summaryDetail }}

{{ selectedIsoPair }} {{ selectedRegionBadge }} {{ matchCountBadge }} {{ dataSourceBadge }}

{{ selectedFlag }}

{{ selectedRegionShort }} {{ selectedIsoPair }} {{ selectedCallingDisplay }}

{{ sourceError }}

{{ error }}

Country search:

Examples: Japan, JP, JPN, +81, yen, Tokyo, .jp, Asia, or USA.

{{ sampleHint }}

Search signals:

Use All signals for normal lookup; narrow the scan when checking codes, currency, phone, or geography.

Region filter:

Choose All regions when you are validating a country code or dialing prefix.

Match limit: {{ matchLimitLabel }}

Accepted range: 3 to 50 match rows.

rows

Status filter:

Leave on All records when checking territories, dependencies, or non-sovereign ISO entries.

Scale chart metric:

Compare selected country context by population, area, or population density.

Field	Value	Copy
{{ row.label }}	{{ row.value }}

Country	ISO	Capital	Region	Currency	Calling	Copy
{{ row.country }}	{{ row.iso }}	{{ row.capital }}	{{ row.region }}	{{ row.currency }}	{{ row.calling }}
No country records matched the current search and filters.

Context	Value	Note	Copy
{{ row.label }}	{{ row.value }}	{{ row.note }}

Signal	Value	Note	Copy
{{ row.label }}	{{ row.value }}	{{ row.note }}

Open OSM OSM Open Google Google

No coordinates are available for the selected country record.

Embed:

Customize

Include current inputs

Size

Loading

Advanced

Width

Height

Aspect ratio

:

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Country information turns ordinary place names into the identifiers that other systems expect. Travel forms, shipping rules, map datasets, payment records, phone-number fields, localization tables, school assignments, and compliance checks often need more than a familiar country name. A record may need a two-letter ISO code, a three-letter ISO code, a numeric code, a calling prefix, a currency code, a capital, a regional grouping, a timezone, or a map reference before it can be compared safely.

Several correct-looking signals can point to different things. Common names are readable, official names can be long, ISO codes are stable for data exchange, country-code top-level domains serve internet naming, and telephone country codes follow numbering plans rather than borders. A short code is easy to mistype, a currency may be shared across many countries, and a calling prefix such as +1 covers a wider numbering area than a single country.

ISO 3166-1: Country and area identifiers in alpha-2, alpha-3, and numeric forms, used in data exchange, domains, passports, shipping, and many business systems.
ISO 4217: Currency identifiers, usually three letters, that are useful for payments and reporting but do not always identify one country by themselves.
E.164 calling code: International telephone numbering prefix. It identifies a numbering area, not a complete phone number or a guaranteed single country.
UN M49 region: A statistical grouping for countries and areas. It is useful for comparison, but it is not a statement about borders, recognition, or sovereignty.

Country lookup path from a search signal to country identity fields, regional context, and source notes — A reliable lookup keeps the matched country record, regional comparison, and source status close together.

Public country datasets are snapshots, not final authorities. Names, population figures, area values, currencies, borders, membership flags, and public map links can change or disagree between sources. The right record for a classroom exercise may not be enough for a government filing, telecom route, payment rule, sanctions check, or shipping restriction.

Use exact country codes when you need a stable machine-readable identifier.
Check peer records when the signal is shared, such as EUR or +1.
Read reference coordinates as orientation aids, not borders or capital-city proof.
Keep the data source and filters with the result when copying facts into another system.

The useful answer is rarely a single field. Confidence comes from the name, official name, ISO codes, currency, calling code, region, status flags, and source notes agreeing closely enough for the job at hand.

How to Use This Tool:

Start broad, verify the selected country, then narrow the search only when the match list is too wide.

Enter a country signal in Country search. Accepted signals include a common or official name, ISO alpha-2, ISO alpha-3, numeric code, capital, currency, language, calling code, country-code TLD, region, timezone, or border ISO3 code.
Keep Search signals on All country signals for normal lookup. Switch to Names and demonyms, ISO, numeric, TLD, and border codes, Calling code and currency, or Capital, language, timezone, and region when that signal should rank higher.
Use Region filter only when the region is already known. Open Advanced for the Status filter, the 3 to 50 row Match limit, or the Scale chart metric.
Leave Status filter on all records when checking territories, dependencies, or non-sovereign ISO entries.
Click Lookup. If the result moves to Match Ledger with no records, clear the region or status filter first, then try an exact country name or code.
A valid code can disappear when Region filter or Status filter excludes the matching record.
Read the summary, Country Profile, and source badge together. Confirm the common name, official name, ISO 3166-1, capital, currency, calling code, and status flags before copying country facts.
Open Match Ledger when the query can match many records, such as a shared currency, phone code, language, or region. Open Region Context to compare the selected country with loaded peers in the same region.
Check Source Ledger before using the result for coverage work. Country Scale Chart, Reference Map, and JSON are useful after the profile and source status look right.

The shortcut buttons load Japan, +1, and EUR examples. They are useful for checking exact-code, shared-calling-code, and shared-currency behavior without rebuilding the search by hand.

Interpreting Results:

Exact identifiers deserve the most weight. A result is stronger when the name, official name, ISO codes, currency, calling code, region, and status flags all point to the same country record. Broad signals need more review because the selected record is only the highest-ranked match for the current filters.

How to interpret country lookup result areas
Result area	What to trust first	What not to overread
`Country Profile`	Common name, official name, ISO codes, capital, currency, language, calling code, TLD, and status flags for the selected record.	A matching name alone does not settle sovereignty, recognition, border, tax, shipping, or payment rules.
`Match Ledger`	Other ranked records that share or partially match the current query.	The first row from `EUR`, `+1`, a language, or a region query may not be the record you intended.
`Region Context`	Population, area, density, share, border, timezone, and rank comparisons within the selected region records.	Regional rank is not a world rank and can change when the status filter changes.
`Source Ledger`	Whether the active catalog is REST Countries v3.1 or a small fallback sample, plus the current filters.	Fallback results keep the lookup usable, but they are not complete country coverage.
`Reference Map`	Reference coordinates and map links for orientation.	The marker is not a border, postal address, capital assertion, or official map decision.

A high-confidence match still needs outside verification for policy-sensitive work. Use the lookup to find and compare the likely record, then check the controlling standard, government source, telecom authority, payment rule, or internal master data before making a binding decision.

Technical Details:

Country lookup combines several public identifier systems. ISO 3166-1 supplies alpha-2, alpha-3, and numeric country or area codes. ISO 4217 supplies currency codes whose first two letters often follow ISO 3166, although currency use is not one-to-one with countries. E.164 defines the international public telephone numbering plan, where the country calling code can cover a numbering area rather than exactly one sovereign state. UN M49 supplies statistical region and country or area groupings.

Those systems answer different questions. ISO codes help software and institutions identify records consistently across languages. Currency and calling codes help with payment, pricing, and contact forms, but they require peer review when shared. Region, subregion, independence, United Nations membership, and source status fields explain the loaded dataset record; they should not be treated as legal classification by themselves.

Lookup Core

Country lookup matching and filtering rules
Stage	Rule	Result effect
Catalog source	REST Countries v3.1 records are loaded when reachable. A small fallback sample is used when the live catalog cannot be loaded.	`Source Ledger` shows the active source and whether the result set is complete enough for coverage checks.
Text cleanup	Search text is compared in a lowercase, accent-reduced form while preserving useful code, phone-prefix, and TLD characters.	Inputs such as `Japan`, `JP`, `+81`, and `.jp` can be compared against different field families.
Candidate filters	Region and status filters reduce the country catalog before ranking.	An otherwise correct record can disappear if the filter excludes its region, independence status, or United Nations membership status.
Signal mode	The selected search-signal mode decides which fields get the strongest ranking weight, while exact country identifiers remain strong matches.	A phone, currency, place, code, or name search can be tuned without losing exact ISO-code behavior.
Ranking	Exact matches rank above prefix matches, prefix matches rank above contains-style matches, and tied rows sort by country name.	`Match Ledger` matters for shared signals because the selected country is only the first ranked record.

Formula Core

Population density and regional shares are derived from the loaded catalog. The equations are simple, but the comparison set matters because status filters and fallback data can change the denominator.

population density = \frac{population}{area in square kilometers} region population share = \frac{selected country population}{sum of population for loaded records in the same region} \times 100 region area share = \frac{selected country area}{sum of area for loaded records in the same region} \times 100

For example, a country with 123,000,000 people and 378,000 km² has a population density of about 325.4 people/km². If its loaded region has 4,200,000,000 people, its regional population share is about 2.93%. The displayed rank for population, area, or density is ordered from largest to smallest within the loaded regional records after the status filter is applied.

Country lookup field families and interpretation limits
Field family	Examples	Interpretation limit
Identity	`ISO 3166-1`, numeric code, country-code TLD, official name, alternate spellings	Identifiers locate records. They do not prove current recognition, borders, sanctions treatment, or jurisdiction-specific rules.
Communications and currency	`Calling code`, currency code, language names	Shared codes need peer review. They do not validate a full phone number, carrier route, legal tender status, or payment availability.
Geography	Capital, region, subregion, continent, timezone, coordinates, border ISO3 codes	Coordinates are reference points. Region names are statistical classifications, not legal boundary statements.
Scale	Population, area, density, regional rank, regional share, scale chart rows	Comparisons depend on source freshness, loaded records, and active filters. Keep those consistent when comparing runs.
Status	Independent, United Nations member, source status	Status flags describe the dataset record and should be checked against official sources for sensitive decisions.

Repeatable country checks should keep the original query, search-signal mode, region filter, status filter, source status, and run time together. Changing any one of those can change the selected record, the number of ranked matches, or the regional comparison values.

Limitations, Privacy, and Accuracy Notes:

The live lookup loads public REST Countries v3.1 fields in the browser, then applies search ranking, filtering, table generation, JSON display, and chart preparation locally. The country search text is not sent as a separate public-data lookup during matching. Viewing the map or opening external map links can contact map providers and may include ordinary browser referrer data.

If Source Ledger shows the fallback sample, use the result only as a sample lookup until the live catalog is available again.
Public datasets can lag or disagree on names, population, area, borders, currencies, capitals, languages, and status fields.
Calling-code matches do not validate subscriber numbers, national dialing rules, carriers, or reachability.
Currency matches do not prove legal tender status, payment acceptance, exchange availability, or tax treatment.
Map coordinates and embedded maps are orientation aids, not official boundary, postal, or jurisdiction references.

Use the lookup as a practical reference and comparison aid. For government filings, sanctions screening, telecom routing, payments, shipping restrictions, or legal classification, verify the final record against the authority that controls that use case.

Worked Examples:

Checking a known country code

Enter JP or Japan, keep Search signals on All country signals, and use Region filter set to Asia only if you want to narrow the match list. Country Profile should identify Japan and show ISO 3166-1 as JP / JPN / 392, with Capital as Tokyo, Currency as Japanese yen, and Calling code as +81.

Reviewing a shared calling code

Enter +1, choose Calling code and currency, and set Region filter to Americas. Match Ledger may show several valid records because the numbering plan is shared. Review the Country, ISO, Capital, Region, Currency, and Calling columns before using one row in a contact or telecom workflow.

Comparing countries that use the euro

Enter EUR, keep Search signals on Calling code and currency, and set Region filter to Europe. The selected country is only the top-ranked record for the active filters. Use Match Ledger to review other euro users, then use Region Context and Country Scale Chart to compare population, area, or density among loaded regional peers.

Fixing an over-narrow search

A search for +81 with Region filter set to Europe can return no country records. Clear the region filter or change it to Asia, then run Lookup again. If the profile still looks incomplete, open Source Ledger and check whether the active catalog is the fallback sample.

FAQ:

Can I search by ISO code instead of country name?

Yes. Country search accepts ISO alpha-2, ISO alpha-3, and numeric country codes. Exact identifiers stay strong matches even when another Search signals mode is selected.

Why did one calling code or currency return several countries?

Calling codes and currencies can be shared. Use Match Ledger to compare the ranked rows, then verify the exact country or territory before copying a code into another workflow.

What does the fallback catalog mean?

It means the live REST Countries v3.1 catalog could not be loaded and the page is using a small fallback sample. The sample keeps the lookup usable, but it is not complete enough for coverage checks.

Does United Nations membership mean the same thing as independence?

No. Status flags can show independent status, United Nations membership, and source status separately. Check the specific flag you need and verify sensitive work against official sources.

Are the map coordinates exact?

No. Reference Map uses coordinates or source map links for orientation. It does not validate borders, capital locations, disputed areas, postal addresses, or legal names.

Does every search contact the public data source?

No. The browser loads the country catalog first, then matching happens locally against the loaded records. Map views and external map links can still contact map providers when you open them.

Glossary:

ISO 3166-1: Country and area code standard that includes alpha-2, alpha-3, and numeric identifiers.
ISO 4217: Currency code standard that commonly represents currencies with three-letter codes such as USD, EUR, and JPY.
E.164 calling code: International telephone numbering prefix used before the national number.
Country-code TLD: A top-level domain associated with a country or territory code, such as .jp or .my.
UN M49 region: United Nations statistical grouping for countries and areas.
Population density: Population divided by area in square kilometers, shown as people per km².
Fallback sample: A small fallback country catalog used when the live REST Countries catalog is unavailable.

References:

ISO 3166 Country Codes, International Organization for Standardization.
ISO 4217 Currency Codes, International Organization for Standardization.
Standard country or area codes for statistical use (M49), United Nations Statistics Division.
ITU-T Recommendation E.164, International Telecommunication Union, updated August 22, 2024.
REST Countries API documentation, REST Countries.