Country Information Lookup
Find country or territory facts from names and common identifiers, then review ranked matches and source freshness from a frozen dataset.{{ summaryTitle }}
{{ summaryLine }}
{{ summaryAnnouncement }}
| Field | Value | Source | Copy |
|---|---|---|---|
| {{ row.label }} | {{ row.value }}{{ row.value }} | {{ row.source }} |
| Rank | Country | ISO | Matched by | Score | Copy |
|---|---|---|---|---|---|
| {{ row.rank }} | {{ row.country }} | {{ row.iso }} | {{ row.matched_by }} | {{ row.score }} |
| Evidence | Value | Limitation | Copy |
|---|---|---|---|
| {{ row.label }} | {{ row.value }} | {{ row.note }} |
Country names are only one way to identify a place. Travel forms, shipping systems, phone numbers, currencies, web addresses, and datasets often use shorter identifiers that are easier for machines to compare but easier for people to confuse.
- ISO 3166-1 codes
- Two-letter, three-letter, and three-digit identifiers for countries, dependencies, and other areas represented in the standard.
- Calling codes
- Telephone prefixes that can be shared. Country code +1, for example, covers the North American Numbering Plan rather than one country alone.
- Currency codes
- Three-letter identifiers such as EUR or JPY. A currency can belong to several countries or territories.
- Country-code top-level domains
- Web suffixes such as
.jpor.my. They are useful identifiers, but domain use does not always reveal the registrant's location.
A reference record can bring these identifiers together with capitals, regions, languages, time zones, borders, population, area, and map coordinates. That is useful for checking a code or preparing a comparison, but the fields do not all have the same authority or update speed.
Population figures age quickly, political status can be disputed or change, and a coordinate is usually a broad reference point rather than a national boundary. Territories and dependencies also need care: filtering to independent countries or United Nations members deliberately removes valid assigned records from the result set.
Use the stable identifier that fits the task, then verify fast-changing facts separately when a booking, compliance decision, publication, or operational handoff depends on them.
How to Use This Tool:
Enter one clue and keep all search signals enabled unless you are checking a specific identifier family.
- Enter a country name, ISO code, numeric code, calling code, currency, capital, language, country-code domain, or region.
- Leave Search signals on All country signals for ordinary lookup. Narrow it to names, codes, telecom and currency, or places when the kind of match matters.
- Use Region filter and Status filter only when those exclusions are intentional. A narrow filter can remove the correct country or territory before ranking begins.
- Read the Country profile and its source, then check Matched by in the Match ledger when several records share the clue.
Interpreting Results:
The first result has the highest text-match score after region and status filters. The score is a ranking weight, not a probability that the country is correct. Shared calling codes, currencies, languages, and regions can produce several equally valid matches.
- Prefer an exact ISO code or exact country name when identity must be unambiguous.
- Read Matched by before accepting a result from a broad clue such as
EUR,+1, orAsia. - Treat population, political status, and membership flags as snapshot facts, not live declarations.
- The Regional scale compares the selected country with up to seven large peers from the same region. It is context, not a complete regional ranking.
Technical Details:
The bundled corpus is a projection of REST Countries v3.1 data frozen on June 16, 2026. It contains countries, territories, dependencies, and other assigned records. Search text is trimmed, compared without case or diacritics, and ranked after filters are applied.
Lookup Core:
Exact values lead partial text matches. Canonical identifiers remain strong even when a narrower search-signal group is selected, which helps prevent a precise ISO or calling code from being buried by a mode choice.
| Match | Score | Examples |
|---|---|---|
| Exact canonical identifier | 120 | Common or official name, ISO code, numeric code, country-code domain, calling code, or currency code |
| Exact value in selected signals | 100 | Capital, language, demonym, region, or another selected field |
| Prefix in selected signals | 72 | The field begins with the query |
| Contained text in selected signals | 42 | The query appears later in the field |
| Exact, prefix, or contained match outside selected signals | 36, 24, or 12 | A weaker fallback when the chosen signal group misses a relevant field |
Ties are ordered by country name. The visible ledger contains 3–50 rows, but that limit does not alter the highest-ranked record. Region, independence, and UN-membership filters remove records before scoring.
Formula Core:
Population density is derived from the snapshot's population and land-area values. It is shown to one decimal place.
D is population density in people per square kilometre, P is the snapshot population count, and A is area in square kilometres. Density is unavailable when area is zero or missing.
For the regional chart, the selected record is combined with up to seven other records from the same region that have the largest positive value for population, area, or density. The chart order is then arranged from smaller to larger values for reading.
Accuracy and Privacy Notes:
Searches use the bundled snapshot in the browser and do not send the country clue to the data provider. The frozen dataset does not update between site releases.
- Verify population, political status, UN membership, and other time-sensitive facts before consequential use.
- Map coordinates are reference points and do not represent borders, jurisdiction, or a precise address.
- A high ranking score shows text-match strength only; it does not resolve shared codes or disputed identity by itself.
Worked Examples:
Shared calling code
Search +1 with Calling codes and currencies. Several North American Numbering Plan records can receive the same exact-match score, so use the match ledger's ISO and country names to choose the intended place rather than treating the first row as uniquely correct.
References:
- REST Countries v3.1 country dataset snapshot, REST Countries, June 16, 2026.
- ISO 3166 country codes, International Organization for Standardization.