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.

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Loading

Advanced

Width

Height

Aspect ratio

:

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Country lookup data connects several identifiers that people often meet separately: country names, ISO codes, calling codes, currency codes, capitals, languages, regions, and map references. The same place can appear under a common name, an official name, a two-letter code, a three-letter code, a numeric code, a top-level domain, or a phone prefix. Reading those signals together helps with form validation, travel planning, data cleanup, localization checks, and support tickets where a short code needs human context.

The hard part is that country records are not only a list of names. Some records describe sovereign states, some describe territories or special areas, and several identifiers are shared across multiple places. A calling code such as +1 can point to more than one country or territory under a shared numbering plan. A currency code such as EUR can match many countries. A map coordinate gives a reference point, not a boundary or street address.

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

Country information also changes over time. Standards bodies update country and currency codes, public datasets revise names and population values, and map links can reflect different naming conventions. A lookup is strongest when it is treated as a current reference snapshot rather than permanent legal, demographic, or political proof.

The practical goal is to identify the likely record, then check the fields that matter for your job. ISO codes are useful for data exchange, currency and calling codes are useful for forms, and region context is useful for comparison. Status and source notes keep those uses from being overread.

How to Use This Tool:

Start with the broad country signal you already have, then narrow only when the first result set is too wide.

Enter a name, ISO code, numeric code, capital, currency, language, calling code, country-code TLD, region, or border code in Country search. Examples such as Japan, JP, JPN, +81, yen, Tokyo, .jp, Asia, and USA match different country signals.
Leave 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 you want that kind of match to rank first.
Use Region filter only when the region is already known. Keep All regions for shared calling codes, currency codes, and short ISO checks because the right record may otherwise be filtered out.
Open Advanced when you need a shorter or longer Match limit, only independent countries, only United Nations members, or a different Scale chart metric for the chart.
Click Lookup. If the page reports that no records matched, clear the region or status filter first, then simplify the search to a country name or exact code.
Read Country Profile for the selected record, then check Match Ledger when the query can match several places. Use Region Context for population, area, density, share, border, and timezone context within the selected region.
Use Source Ledger before copying results into another system. If it shows a fallback catalog instead of the live REST Countries catalog, treat the match as a sample result and do not use it for coverage checks.
Open Country Scale Chart, Reference Map, and JSON only after the profile and source notes look right. The chart and map support interpretation; the country table remains the main record.

The shortcut buttons load common starting points such as Japan, the +1 calling code, and euro-area currency matches. They are useful for testing search behavior without clearing every advanced setting.

Interpreting Results:

Trust exact identifiers first, then check whether the surrounding fields agree. A country name paired with the expected ISO 3166-1, Currency, Calling code, and Region is a stronger match than a single partial name hit. Shared codes need extra care because the first selected record may be only one of several valid matches.

How to interpret country lookup result fields
Result area	What to check	Common mistake
`Country Profile`	Confirm the common name, official name, ISO codes, capital, currency, calling code, language, TLD, and status flags.	Assuming a matching name alone proves the record is the intended legal or administrative entity.
`Match Ledger`	Check other ranked matches when the query is a shared code, short word, currency, region, or language.	Copying the first record from a broad query such as `EUR` or `+1` without reviewing peers.
`Region Context`	Read rank, share, density, border, and timezone rows as comparisons within the loaded region records.	Treating regional rank as a global rank or as a complete political classification.
`Source Ledger`	Verify whether live records or fallback sample records are active, and check current filters.	Using fallback results as if they covered every country and territory.
`Reference Map`	Use coordinates and map links for orientation only.	Reading the marker as a border, capital location, postal location, or official map statement.

High-confidence matching still has limits. An exact ISO code can identify a record, but it does not answer every sovereignty, recognition, border, currency-validity, or phone-number-validity question. Verify sensitive use cases against the relevant standard, government source, telecom authority, or internal master data.

Technical Details:

Country lookup is mostly record matching, classification, and comparison. ISO 3166-1 gives three common country-code forms: alpha-2, alpha-3, and numeric-3. ISO 4217 gives three-letter currency codes, often related to ISO country codes but not unique to one country in every practical use. E.164 calling codes identify international numbering areas, and those areas may cover groups of countries or territories rather than exactly one country record.

Region, subregion, UN membership, independence, and status fields should be read as dataset fields with specific meanings. They help separate country-like records from territories, dependencies, and special areas, but they are not a substitute for a legal opinion or an official recognition check. Population and area are useful for scale context, while map coordinates are only reference geometry.

Lookup Core

Country lookup matching and filtering rules
Stage	Rule	Result effect
Catalog load	The live country catalog is loaded when available. A small fallback catalog is used if the live source cannot be reached.	`Source Ledger` reports whether coverage is live or fallback.
Text normalization	Search text is lowercased, accent marks are reduced, and punctuation outside country-code, phone-code, and TLD patterns is ignored.	Queries such as names, codes, `+81`, and `.jp` can be compared consistently.
Signal selection	The selected search-signal mode decides which fields rank highest, while exact country identifiers remain strong matches.	A currency query, phone prefix, or region name can be made more useful without losing exact ISO-code behavior.
Filtering	Region and status filters reduce the candidate catalog before ranking.	A correct code can disappear if the filter excludes its country or territory.
Ranking	Exact matches outrank prefix matches, and prefix matches outrank contains-style matches. Ties sort by country name.	`Match Ledger` is important for broad inputs because the selected country is only the highest-ranked row.

Derived Metric Core

Population density and regional shares are calculated from the loaded catalog. The same formulas apply to live records and fallback records, but the meaning changes if the fallback catalog is active because the comparison set is incomplete.

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

Ranks are ordered from largest to smallest for population, area, and population density. Region shares use the selected country divided by the loaded records in the same region after the status filter is applied. The Country Scale Chart plots the selected country with nearby regional peers for the chosen metric, so chart comparisons should be read as regional context rather than a world ranking.

Country lookup fields and interpretation limits
Field family	Examples	Interpretation limit
Identity codes	`ISO 3166-1`, numeric code, country-code TLD, border ISO3 codes	Codes identify records and adjacent-code references; they do not prove current diplomatic recognition or border status.
Communications and money	`Calling code`, `Currency`, languages	Calling and currency codes can be shared. They do not validate a full phone number, payment route, or legal tender rule.
Geography	Capital, region, subregion, continent, timezones, coordinates	Coordinates and maps are reference points. Region names are classification aids, not legal boundaries.
Scale metrics	Population, area, density, regional rank, regional share	Values depend on source freshness and loaded coverage. Compare runs only when the source status and filters match.
Status flags	Independent, UN member, source status	Status flags explain the dataset record. They should be checked against official sources for policy-sensitive work.

For repeatable checks, keep the original query, search-signal mode, region filter, status filter, source status, and run time together. Changing any of those can alter the selected record, the number of matches, or the regional comparison set.

Limitations, Privacy, and Accuracy Notes:

This is a networked lookup when the live catalog is available. The browser downloads selected country fields from REST Countries, then search ranking and table generation happen in the browser. Typed searches are applied after the catalog is loaded, while the map panel and external map buttons can contact map providers for the selected coordinates or source map link.

If Source Ledger reports the fallback catalog, the record set is only a small sample and should not be treated as complete country coverage.
The tool may remain unpublished in the catalog while it is being reviewed; source coverage and fallback status are shown inside the result tabs instead of being inferred from catalog state.
Population, area, borders, names, currencies, and membership fields can change or disagree across sources.
The map marker is for orientation. It is not a boundary, a capital-city assertion, or a user-location signal.
Calling-code matches do not validate full phone numbers, carriers, area codes, or subscriber reachability.

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

Worked Examples:

Checking a known country code

Enter Japan or JP, leave Search signals on All country signals, and set Region filter to Asia if you want a narrower result. Country Profile should select Japan and show ISO 3166-1 as JP / JPN / 392, with Capital as Tokyo, Currency as Japanese yen, and Calling code as +81.

Reading a shared calling code

Enter +1 and choose Calling code and currency. With Region filter set to Americas, Match Ledger can include more than one valid record because the numbering plan is shared. Use the ledger rows, not only the selected country, before copying Country, ISO, Capital, Region, Currency, and Calling into another system.

Comparing euro-area matches

Enter EUR, choose Calling code and currency, and set Region filter to Europe. The first selected country is only the top ranked record for the active filters. Match Ledger shows other countries using the euro, while Region Context and Country Scale Chart compare the selected country against loaded European peers by population, area, or density.

Fixing an over-narrow filter

A search such as +81 with Region filter set to Europe can return no country records. Clear the region filter or switch it to Asia, then run the lookup again. If the result still looks incomplete, open Source Ledger and check whether the page is using the fallback catalog.

FAQ:

Can I search by ISO code instead of country name?

Yes. Country search accepts ISO alpha-2, ISO alpha-3, numeric codes, and several other signals. Exact country identifiers remain strong matches even when a narrower search-signal mode is selected.

Why did one calling code return several countries?

Some international calling codes are shared. Use Match Ledger to review all ranked records, then verify the country or territory before using the code in a phone-number workflow.

What does the fallback catalog mean?

It means the live REST Countries catalog was unavailable and the page is using a small fallback sample catalog. The sample keeps the interface usable, but it is not complete enough for data cleanup or coverage checks.

Are the map links authoritative?

No. Reference Map uses the selected record's coordinates or map link for orientation. It does not verify borders, capital locations, disputed areas, or current legal names.

Does UN member mean the same thing as independent?

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

Glossary:

ISO 3166-1: International country-code standard that includes alpha-2, alpha-3, and numeric country codes.
ISO 4217: International 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; it can be shared by more than one country or territory.
Country-code TLD: A top-level domain such as .jp or .my associated with a country or territory code.
UN member: A dataset flag indicating United Nations membership status for the selected record.
Population density: Population divided by area in square kilometers, shown as people per km².
Fallback catalog: A small sample catalog used when the live country source 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, May 1997.
REST Countries API data fields, REST Countries GitLab, updated April 21, 2025.