IP Location Database (Advance)
Overview
Our Geo Advance IP to Geolocation Database provides you with precise city level geolocation data for both IPv4 and IPv6 addresses. Compared to our Geo Standard 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. Our collection pipelines run nonstop, around the clock, with database updates delivered on a daily or weekly cadence depending on your subscription plan. The dataset is available in CSV and MMDB, with JSON, Parquet, or any custom format on request at no extra cost, all backed by stable schemas and changelogs.
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):
Standardized country and continent metadata with codes, currency, calling codes, TLDs, and languages.
- File Size: 9.67 KB
- Entries: 254
- Fields: 15
Multilingual place names for cities, districts, states, countries, and continents.
- File Size: 13.02 MB
- Entries: 337.4K
- Fields: 13
IP ranges mapped to locations with place IDs (for multilingual responses), ZIP codes, coordinates, time zone, and connection type.
- File Size: 480.94 MB
- Entries: 32.8M
- Fields: 16
Documentation for dataset contents, schema, usage, and support.
- File Size: 9.79 KB
SHA-256 checksums for verifying file integrity.
- File Size: 330 Bytes
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 |
1. Example Records
start_ip,end_ip,country_id,state_place_id,state_code,district_place_id,city_place_id,accuracy_radius,confidence,dma_code,zip_code,latitude,longitude,geo_name_id,time_zone_name,connection_type
60.68.68.117,60.68.68.117,83,271,JP-13,3699,271,6.7,high,,160-8484,35.688414,139.688442,6498350,Asia/Tokyo,Fixed Broadband
77.131.193.0,77.131.193.255,56,350,FR-PAC,240077,54947,9.617,high,,06510,43.7668,7.19176,12072002,Europe/Paris,DSL
86.64.61.72,86.64.61.75,56,316,FR-IDF,3630,3630,3.603,high,,75001,48.85717,2.3414,6452939,Europe/Paris,Leased Line
124.105.48.237,124.105.48.237,133,1825,PH-41,240078,240079,8.327,high,,4900,13.39413,121.87903,1728612,Asia/Manila,DSL
71.232.160.26,71.232.160.26,172,384,US-MA,6637,28495,5.553,high,521,02703,41.94431,-71.28139,9687767,America/New_York,Cable
176.113.74.47,176.113.74.47,29,598,CA-QC,4373,4373,12.517,medium,,H2L,45.5124,-73.55469,6137421,America/Toronto,DSL
24.189.57.25,24.189.57.25,172,394,US-NY,4387,35862,5.0,high,501,11720,40.85843,-73.09955,5112035,America/New_York,Cable
109.79.36.5,109.79.36.5,74,831,IE-C,87459,240080,9.094,high,,H91,53.274,-9.05127,10282244,Europe/Dublin,DSL
136.142.159.2,136.142.159.2,172,381,US-PA,5761,28317,5.242,high,508,15219,40.43866,-79.99724,7183531,America/New_York,Fixed Wireless
93.11.239.0,93.11.239.69,56,316,FR-IDF,240081,84810,4.124,high,,94450,48.74619,2.49215,6452023,Europe/Paris,DSL2. 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 |
2. Example Records
id,place_english,place_german,place_russian,place_korean,place_portuguese,place_japanese,place_persian,place_french,place_chinese,place_spanish,place_czech,place_italian
5,Asia,Asien,Азия,Ásia,Ásia,アジア, آسیا,Asie,亚洲,Asia,Asie,Asia
6,North America,Nordamerika,Северная Америка,América do Norte,América Do Norte,北アメリカ, امریکای شمالی,Amérique du Nord,北美洲,Norteamérica,Severní Amerika,America del Nord
7,Europe,Europa,Европа,Europa,Europa,ヨーロッパ, اروپا,Europe,欧洲,Europa,Evropa,Europa
13,Japan,Japan,Япония,Japão,Japão,日本,ژاپن,Japon,日本,Japón,Japonsko,Giappone
5761,Allegheny County,Allegheny,Аллегейни,앨러게니 군,Condado de Allegheny,アレゲニー郡,شهرستان الیگنی، پنسیلوانیا,Comté dAllegheny,阿利根尼縣,Аллегейни,Allegheny,Contea di Allegheny
271,Tokyo,Tokio,Токио,도쿄 도,,東京,,Tokyo,东京,Tokio,Tokio,Tokyo
240018,United States of America,,,,,,,,,,,
394,New York,New York,Нью-Йорк,Nova Iorque,Nova Iorque,ニューヨーク州,ایالت نیویورک,New York,纽约州,Nueva York,New York (stát),New York
240019,"Washington, D.C.",,,,,,,,,,,
240078,Province of Marinduque,,,,,,,,,,,
28,United States,USA,США,Estados Unidos,Estados Unidos,アメリカ合衆国,ایالات متحدهٔ امریکا,États-Unis,美国,Estados Unidos,Spojené státy americké,Stati Uniti d'America
29,Philippines,Philippinen,Филиппины,Filipinas,Filipinas,フィリピン共和国,فیلیپین,Philippines,菲律宾,Filipinas,Filipíny,Filippine
3699,Shinjuku,Shinjuku,Синдзюку,,,新宿,,Shinjuku,新宿,Šinjuku,Šinjuku,Shinjuku
31,France,Frankreich,Франция,França,França,フランス共和国,فرانسه,France,法国,Francia,Francie,Francia
381,Pennsylvania,Pennsylvania,Пенсильвания,Pensilvânia,Pensilvânia,ペンシルベニア州,پنسیلوانیا,Pennsylvanie,宾夕法尼亚州,Pensilvania,Pensylvánie,Pennsylvania
598,Quebec,Quebec,Квебек,Quebeque,Quebeque,ケベック州,,Québec,魁北克省,Quebec,Quebec,Quebec
28495,Attleboro,Attleboro,Атлеборо,,,アトルボロ,اتلبارو، ماساچوست,Attleboro,艾特伯罗,Attleboro,Attleboro,Attleboro
3630,Paris,Paris,Париж,,,パリだ,,Paris,巴黎,París,Paříž,Parigi
239920,Republic of France,,,,,,,,,,,
240079,Masiga,,,,,,,,,,,
316,Ile-de-France,Ile-de-France,Иль-де-Франс,,,イル = ド = フランス,,Ile-de-France,法兰西岛,Isla de Francia,Ile-de-France,Ile-de-France
240077,Maritime Alps,,,,,,,,,,,
240080,Gaillimh,,,,,,,,,,,
28317,Pittsburgh,Pittsburgh,Питтсбург,Pitsburgo,Pitsburgo,ピッツバーグ,پیتسبرگ، پنسیلوانیا,Pittsburgh,匹兹堡,Pittsburgh,Pittsburghu,Pittsburgh
54947,Carros,Carros,Карро,,,カロス,,Carros,卡尔罗,Carros,Carros,Carros
4373,Montreal,Montreal,Монреаль,Montreal,,モントリオール,,Montréal,蒙特利尔,Montreal,Do Montrealu,Montréal
64,Ireland,Irland,Ирландия,Irlanda,Irlanda,アイルランド,ایرلند,Irlande,爱尔兰,Irlanda,Irsko,Irlanda
3630,Paris,Paris,Париж,,,パリだ,,Paris,巴黎,París,Paříž,Parigi
65,Canada,Kanada,Канада,Canadá,Canadá,カナダ,کانادا,Canada,加拿大,Canadá,Kanada,Canada
840,Dublin,Dublin,Дублин,,,ダブリン,,Dublin,都柏林,Dublin,Dublin,Dublino
350,Provence-Alpes-Cote d'Azur,Provence-Alpes-Côte d 'Azur,Прованс-Альпы-Лазурный Шорс,,,プロヴァンス = アルプ = コート・ダジュール地域圏,,Provence-Alpes-Côte d'Azur,普罗旺斯-阿尔卑斯-蓝色海岸,Provenza-Alpes-Costa Azul,Provence-Alpes-Azur,Provenza-Alpi-Costa Azzurra
240081,Departement du Val-de-Marne,,,,,,,,,,,
4387,Suffolk County,Suffolk,Саффолк,,Condado de Suffolk,サフォーク郡,شهرستان سافک، ماساچوست,Comté de Suffolk,沙福克縣,Саффолк,Suffolk,Contea di Suffolk
271,Tokyo,Tokio,Токио,도쿄 도,,東京,,Tokyo,东京,Tokio,Tokio,Tokyo
384,Massachusetts,Massachusetts,Массачусетс,매사추세츠 주,,マサチューセッツ州,ماساچوست,Massachusetts,麻薩諸塞州,Massachusetts,Massachusetts,Massachusetts
831,Connaught,Connaught,Коннот,,,コノートだ,,Connacht,康诺特,Connaught,Connaught,Connaught
87459,County Galway,County Galway,Графство Голуэй,,,ゴールウェイ州,,Comté de Galway,戈尔韦县,Графство Голуэй,Galway,Contea di Galway
84810,Limeil-Brevannes,Limeil-Brevannes,Лаймел-Бреваннес,,,ブレヴァンヌ,,Limeile-Brevannes,利梅布勒瓦纳,Limeil-Brevannes,Limeil-Brevannes,Limeil-Brevannes
4588,Ottawa,Ottawa,Оттава,Otava,Condado de Ottawa,オタワ,شهرستان اتاوا، اکلاهما,Ottawa,渥太華縣,Ottawa,Ottawa,Ottawa
3054,Manila,Manila,Манила,,,マニラ,,Manille,马尼拉,Manila,Manila,Manila
239984,Republic of the Philippines,,,,,,,,,,,
35862,Centereach,Centereach,Центохват,,,センタリーチ,,Centereach,中心位置,Centereach,Centereach,Al centro
6637,Bristol County,Bristol,Бристол,,Condado de Bristol,ブリストル郡,شهرستان بریستول، ماساچوست,Comté de Bristol,布里斯托縣,Бристол,Bristol County (Texas),Contea di Bristol
1825,Mimaropa,Mimaropa,Мимаропа,,,ミマロパだ,,Mimaropa,米玛罗巴人,Mimaropa,Mimaropa,Mimaropa3. 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 |
3. Example Records
id,continent_code,continent_name_place_id,country_code2,country_code3,country_code_ioc,country_name_place_id,country_name_official_place_id,country_capital_place_id,currency_code,currency_name,currency_symbol,calling_code,tld,languages
133,AS,5,PH,PHL,PHI,29,239984,3054,PHP,Philippine Piso,₱,+63,.ph,"tl,en-PH,fil"
172,NA,6,US,USA,USA,28,240018,240019,USD,US Dollar,$,+1,.us,"en-US,es-US,haw,fr"
74,EU,7,IE,IRL,IRL,64,64,840,EUR,Euro,€,+353,.ie,"en-IE,ga-IE"
83,AS,5,JP,JPN,JPN,13,13,271,JPY,Yen,¥,+81,.jp,ja
56,EU,7,FR,FRA,FRA,31,239920,3630,EUR,Euro,€,+33,.fr,"fr-FR,frp,br,co,ca,eu,oc"
29,NA,6,CA,CAN,CAN,65,65,4588,CAD,Canadian Dollar,C$,+1,.ca,"en-CA,fr-CA,iu"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):
- File Size: 2.97 GB
- Entries: 32.8M
Documentation for dataset contents, schema, usage, and support.
- File Size: 11.10 KB
SHA-256 checksums for verifying file integrity.
- File Size: 162 Bytes
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.
2. Example Records
{
"connection_type": "Fixed Broadband",
"location": {
"accuracy_radius": "6.7",
"city": {
"name": {
"cs": "Tokio",
"de": "Tokio",
"en": "Tokyo",
"es": "Tokio",
"fa": "",
"fr": "Tokyo",
"it": "Tokyo",
"ja": "東京",
"ko": "도쿄 도",
"pt": "",
"ru": "Токио",
"zh": "东京"
}
},
"confidence": "high",
"coordinates": {
"latitude": "35.688414",
"longitude": "139.688442"
},
"country": {
"capital": {
"cs": "Tokio",
"de": "Tokio",
"en": "Tokyo",
"es": "Tokio",
"fa": "",
"fr": "Tokyo",
"it": "Tokyo",
"ja": "東京",
"ko": "도쿄 도",
"pt": "",
"ru": "Токио",
"zh": "东京"
},
"code2": "JP",
"code3": "JPN",
"code_ioc": "JPN",
"continent": {
"code": "AS",
"name": {
"cs": "Asie",
"de": "Asien",
"en": "Asia",
"es": "Asia",
"fa": " آسیا",
"fr": "Asie",
"it": "Asia",
"ja": "アジア",
"ko": "Ásia",
"pt": "Ásia",
"ru": "Азия",
"zh": "亚洲"
}
},
"currency": {
"code": "JPY",
"name": {
"en": "Yen"
},
"symbol": "¥"
},
"metadata": {
"calling_code": "+81",
"languages": "ja",
"tld": ".jp"
},
"name": {
"cs": "Japonsko",
"de": "Japan",
"en": "Japan",
"es": "Japón",
"fa": "ژاپن",
"fr": "Japon",
"it": "Giappone",
"ja": "日本",
"ko": "Japão",
"pt": "Japão",
"ru": "Япония",
"zh": "日本"
},
"name_official": {
"cs": "Japonsko",
"de": "Japan",
"en": "Japan",
"es": "Japón",
"fa": "ژاپن",
"fr": "Japon",
"it": "Giappone",
"ja": "日本",
"ko": "Japão",
"pt": "Japão",
"ru": "Япония",
"zh": "日本"
}
},
"district": {
"name": {
"cs": "Šinjuku",
"de": "Shinjuku",
"en": "Shinjuku",
"es": "Šinjuku",
"fa": "",
"fr": "Shinjuku",
"it": "Shinjuku",
"ja": "新宿",
"ko": "",
"pt": "",
"ru": "Синдзюку",
"zh": "新宿"
}
},
"dma_code": "",
"geoname_id": "6498350",
"state": {
"code": "JP-13",
"name": {
"cs": "Tokio",
"de": "Tokio",
"en": "Tokyo",
"es": "Tokio",
"fa": "",
"fr": "Tokyo",
"it": "Tokyo",
"ja": "東京",
"ko": "도쿄 도",
"pt": "",
"ru": "Токио",
"zh": "东京"
}
},
"zipcode": "160-8484"
},
"time_zone": "Asia/Tokyo"
}Database Integrity & Authenticity Verification
There are two methods of verifying the integrity and authenticity of our Database:
1. Using the Signature File (Recommended)
IPGeolocation.io signs every database release to ensure its authenticity and integrity. This allows customers to verify that a downloaded Advance IP to Location database file originates directly from IPGeolocation.io and has not been altered, corrupted, or tampered with during transfer or storage.
Each database update includes a corresponding signature file, generated using our private signing key. Customers can validate the database using the provided public verification key. To verify a database file, you need:
- Database file (the downloaded archive)
- Signature file (the matching signature for that archive)
- Public key (public-key.pem)
These files are available via official IPGeolocation.io download endpoints and are also shared in database update notifications.
2. Using the Checksum File (Legacy)
Each database archive includes a checksum.txt file containing the SHA-256 checksums for the files packaged in the archive. You can use this file to validate that the extracted contents are complete and unchanged.
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. These links never change, so you can use them both for your initial download and for all future updates. You will receive:
- Database Archive URL : downloads the latest release of your subscribed database (CSV, MMDB or requested formats).
- Signature File URL : downloads the matching signature file for the latest release (used for authenticity verification).
- Public Key URL : downloads the public verification key (used with the signature file).
- Status Endpoint URL : returns the database's most recent update timestamp.
Our databases are updated continuously and shipped on a daily or weekly cycle depending on your plan, 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.