IP Location Database (Advance)
Overview
Our Advanced Tier IP to Geolocation Database provides you with precise city level geolocation data for both IPv4 and IPv6 addresses. Compared to our Standard Tier IP to Geolocation Database, it adds extra fields such as accuracy radius, confidence score, and DMA codes (DMA codes are available in the USA only) to give you the pinpoint accuracy you need to make tighter decisions.
Every IP range is linked to countries, states, districts, and cities, with multilingual place names resolved through reference tables for consistency. This structure makes it easy to join datasets and work with standardized metadata across different regions and languages. We update our databases every single day, and it's available in CSV, MMDB, or custom formats to fit your needs.
Below, you'll find full documentation of the archive contents, schema definitions, file specifications, and integration notes to help you get up and running quickly.
Available Database Formats
CSV Database Documentation
1.Overview
The CSV version of our Advance IP to Location Database is delivered as a ZIP archive that includes Gzip-compressed files with IP ranges, location details, and multilingual place names. It’s well-suited for bulk imports and easy integration into relational databases.
2.Archive Content
After downloading and extracting the Advance IP to Location CSV database archive, you’ll find the following files (with their types noted):
db-country.csv.gzStandardized country and continent metadata with codes, currency, calling codes, TLDs, and languages.
db-place.csv.gzMultilingual place names for cities, districts, states, countries, and continents.
db-ip-location.csv.gzIP ranges mapped to locations with place IDs (for multilingual responses), ZIP codes, coordinates, time zone, and connection type.
README.mdDocumentation for dataset contents, schema, usage, and support.
db-ip-location.md5Always verify downloaded files with the provided checksum before importing.
On Linux, if sha256sum is not installed, first run:
sudo apt-get install coreutilsThen check the archive files against the checksum file with:
sha256sum -c checksum.txtExample output:
db-country.csv.gz: OK
db-place.csv.gz: OK
db-ip-location.csv.gz: OK
README.md: OK
db-ip-location.md5: OKIf a file’s checksum does not match, FAILED will be shown instead of OK . If verification fails, first confirm that the download completed correctly; if the issue persists, please contact our support team.
Schema
This section describes the schema of each file included in the Advance IP to Location Database archive. For every file, you’ll find its purpose, field definitions, and examples to help with integration.
1.db-ip-location.csv.gz
This file provides geolocation data for IPv4 and IPv6 ranges, mapped down to the city level. Each record links an IP block to country, state, district, and city (through place IDs for multilingual response), geographic coordinates, time zone, GeoNames ID, and connection type. It also includes accuracy radius, confidence level, and DMA codes (U.S. only) for finer and more granular details.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| start_ip | string | The starting IP address of the range in IPv4 or IPv6 format. | No | 192.168.0.1 |
| end_ip | string | The ending IP address of the range in IPv4 or IPv6 format. | No | 192.168.0.255 |
| country_id | number | The unique identifier for the country associated with the IP range. | No | 192 |
| state_place_id | number | The unique identifier for the state or province associated with the IP range. | Yes | 5332921 |
| state_code | string | The two-letter code representing the state or province with country-code, following ISO 3166-2 standards. | Yes | CA |
| district_place_id | number | The unique identifier for the district associated with the IP range. | Yes | 5332923 |
| city_place_id | number | The unique identifier for the city associated with the IP range. | Yes | 5375480 |
| accuracy_radius | number | The accuracy radius in kilometers for the location associated with the IP range. | No | 20 |
| confidence | number | The confidence level (0-100) of the location data associated with the IP range. | No | 95 |
| dma_code | number | The Designated Market Area (DMA) code for the location associated with the IP range. | Yes | 807 |
| zip_code | string | The postal code for the location associated with the IP range. | Yes | 94043 |
| latitude | number | The latitude coordinate of the location associated with the IP range. | No | 37.3861 |
| longitude | number | The longitude coordinate of the location associated with the IP range. | No | -122.0838 |
| geo_name_id | number | The GeoNames ID for the location associated with the IP range. | Yes | 5375480 |
| time_zone_name | string | The time zone name for the location associated with the IP range. | No | America/Los_Angeles |
| connection_type | string | The type of internet connection associated with the IP range (e.g., dialup, cable, DSL, fiber, etc.). | Yes | cable |
The country_id field links to db-country.id , which provides standardized country metadata such as different names, codes, currency, and language information. Similarly, the *_place_id fields (e.g., state_place_id, district_place_id, city_place_id) link to db-place.id . These joins let you query multilingual names for countries, states, districts, and cities, ensuring consistency across different languages and regions.
Example Records
2.db-place.csv.gz
This file contains multilingual names for countries, continents, states, districts, and cities worldwide. It serves as the reference dictionary for the IP Location Database, allowing you to resolve place IDs into multilingual responses across different regions and languages.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| id | number | The unique identifier for the place. | No | 5375480 |
| place_english | string | The name of the place in English. | No | Mountain View |
| place_german | string | The name of the place in German. | Yes | Mountain View |
| place_russian | string | The name of the place in Russian. | Yes | Маунтин-Вью |
| place_korean | string | The name of the place in Korean. | Yes | 마운틴 뷰 |
| place_portuguese | string | The name of the place in Portuguese. | Yes | Mountain View |
| place_japanese | string | The name of the place in Japanese. | Yes | マウンテンビュー |
| place_persian | string | The name of the place in Farsi. | Yes | ماونتین ویو |
| place_french | string | The name of the place in French. | Yes | Mountain View |
| place_chinese | string | The name of the place in Chinese. | Yes | 山景城 |
| place_spanish | string | The name of the place in Spanish. | Yes | Mountain View |
| place_czech | string | The name of the place in Czech. | Yes | Mountain View |
| place_italian | string | The name of the place in Italian. | Yes | Mountain View |
The id field in db-place.csv.gz is used as a reference key to resolve place names. It joins with the placeid fields in db-ip-location.csv.gz (such as state_place_id, district_place_id, and city_place_id) and also with placeid fields in db-country.csv.gz (such as country_name_place_id and country_capital_place_id). These joins ensure that every IP range or country record can be enriched with multilingual place names from the reference table, making it possible to deliver consistent, localized responses across different regions and languages.
Example Records
3.db-country.csv.gz
This file contains standardized country metadata for the IP Location Database. It includes continent codes and names, ISO-2/ISO-3/IOC country codes, country and official names (as place IDs), capital (place ID), currency (code, name, symbol), international calling codes, top-level domains (TLDs), and supported language tags.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| id | number | The unique identifier for the country. | No | 192 |
| continent_code | string | The continent code associated with the country. | No | NA |
| continent_name_place_id | number | The unique identifier for the continent place. | No | 6255148 |
| country_code2 | string | The ISO 3166-1 alpha-2 code of the country. | No | US |
| country_code3 | string | The ISO 3166-1 alpha-3 code of the country. | No | USA |
| country_code_ioc | string | The IOC country code. | No | USA |
| country_name_place_id | number | The unique identifier for the country place. | No | 6252001 |
| country_name_official_place_id | number | The unique identifier for the official country place. | No | 6252001 |
| country_capital_place_id | number | The unique identifier for the capital place. | No | 5375480 |
| currency_code | string | The ISO 4217 currency code of the country. | No | USD |
| currency_name | string | The name of the currency used in the country. | No | United States Dollar |
| currency_symbol | string | The symbol of the currency used in the country. | No | $ |
| calling_code | string | The international calling code of the country. | No | +1 |
| tld | string | The top-level domain (TLD) of the country. | No | .us |
| languages | string | The official languages spoken in the country, represented as a comma-separated list of ISO 639-1 codes. | No | en,es |
The id field in db-country.csv.gz serves as the reference key for country metadata. It is used by the country_id field in db-ip-location.csv.gz to link each IP range to standardized country details such as ISO codes, continent, capital, currency, calling codes, and languages. In addition, *_place_id fields within db-country.csv.gz (e.g., country_name_place_id, country_capital_place_id) join to db-place.csv.gz to resolve multilingual names for countries and capitals. Together, these joins ensure that country-level information can be consistently linked, enriched, and localized.
Example Records
4.File Relationship Diagram
File Format & Encoding
All Advance IP to Location CSV datasets are provided in UTF-8 encoding, comma-separated, and compressed with Gzip (.csv.gz). Each file includes a header row listing the field names for clarity and consistency.
Field values are unquoted by default, with quotes applied only in the following cases:
- Line breaks within text fields.
- Commas inside a value (e.g., addresses).
- Lists of values (e.g., languages).
- Spaces that may be auto-quoted by export tools.
MMDB Database Documentation
1.Overview
The MMDB version of our Advance IP to Location is delivered as a ZIP archive that includes a single MMDB file with all geolocation data (including multilingual place fields), a README file, and a checksum file. It’s optimized for fast lookups in applications and services, making it ideal for real-time queries and direct integration into your systems.
2.Archive Content
After downloading and extracting the Advance IP to Location MMDB database archive, you’ll find the following files (with their types noted):
db-ip-location.mmdbREADME.mdDocumentation for dataset contents, schema, usage, and support.
db-ip-location.md5Always verify downloaded files with the provided checksum before importing.
On Linux, if sha256sum is not installed, first run:
sudo apt-get install coreutilsThen check the archive files against the checksum file with:
sha256sum -c checksum.txtExample output:
db-ip-location.mmdb: OK
README.md: OK
db-ip-location.md5: OKIf a file’s checksum does not match, FAILED will be shown instead of OK . If verification fails, first confirm that the download completed correctly; if the issue persists, please contact our support team.
Response Schema
This section describes the structure of the data returned from the Advance IP to Location MMDB file. Each field is detailed with its type, meaning, and example values to help you interpret responses and integrate them into your applications.
1.db-ip-geolocation.mmdb
This file provides geolocation data for IPv4 and IPv6 ranges at the city level. Each response includes multilingual country, state, district, and city details, geographic coordinates, time zone, GeoNames ID, and connection type. It also includes accuracy radius, confidence level, and U.S.-only DMA codes for finer, more granular detail.
2.Field Reference
The following reference lists all fields available in the MMDB response. Each entry includes the field path, its description, data type, and example value to help you understand how to parse and integrate the data.
Example Records
Data Format & Constraints
- All fields defined in the schema are always present in the Advance IP to Location MMDB response.
- Fields may contain empty strings (""), but never null, so null checks are not required.
- Place names such as countries, states, districts, and cities are available in multiple translations.
- All text values are encoded in UTF-8.
- Field names and response structure remain stable across updates for backward compatibility.
Database Updates & Delivery
When you subscribe to our Advance IP to Location database, we’ll send you static download links for the archive in your chosen formats. These links never change, so you can use them both for your initial download and for all future updates.
Our databases are refreshed daily and weekly, ensuring you always have access to the most current data. Each time your subscribed dataset is updated, you’ll also receive an email notification so you don’t miss a release.
For automated workflows, you can check our status endpoint to see the last update timestamp. When the date changes, simply re-fetch the archive using your static download URL to pull the latest version into your system.
