IP Location Database (Standard)
Overview
Our Standard Tier IP to Geolocation Database provides you with accurate city-level geolocation data for both IPv4 and IPv6 addresses. It includes standard geolocation data such as country, state, district, city, ZIP code, geographic coordinates, time zone, GeoNames ID, and connection type. If your use case is more critical and you need more granular details on location, please check out our advanced ip to location database.
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 Standard 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 Standard 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: 338.7K
- Fields: 13
IP ranges mapped to locations with place IDs (for multilingual responses), ZIP codes, coordinates, time zone, and connection type.
- File Size: 320.30 MB
- Entries: 29.3M
- Fields: 12
Documentation for dataset contents, schema, usage, and support.
- File Size: 9.11 KB
SHA-256 checksums for verifying file integrity.
- File Size: 330 Bytes
Schema
This section describes the schema of each file included in the Standard 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.
| 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 |
| 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 |
I. Example Records
start_ip,end_ip,country_id,state_place_id,state_code,district_place_id,city_place_id,zip_code,latitude,longitude,geo_name_id,time_zone_name
2404:7c80:14:5:d100:8b0f:8097:f124,2404:7c80:14:5:d100:8b0f:8097:f124,76,331,IN-PB,8843,8843,141001,30.90725,75.84919,11857537,Asia/Kolkata
122.170.110.124,122.170.110.124,76,291,IN-MH,3720,3729,400003,18.95819,72.83207,10118382,Asia/Kolkata
67.227.182.138,67.227.182.207,172,373,US-TX,4556,4330,75201,32.77822,-96.79512,4684902,America/Chicago
206.221.176.169,206.221.176.169,172,297,US-NJ,4509,31781,07094,40.78834,-74.05502,5099438,America/New_York
188.141.18.59,188.141.18.59,74,850,IE-M,90201,2071,T12,51.89851,-8.4756,10281767,Europe/Dublin
189.225.115.160,189.225.115.160,117,66,MX-MEX,202803,130706,53000,19.47371,-99.23367,11561574,America/Mexico_City
184.146.159.47,184.146.159.47,29,597,CA-ON,8747,8943,N2G,43.45164,-80.49253,6472999,America/Toronto
175.114.66.58,175.114.66.58,193,283,KR-11,151541,283,04524,37.56521,126.97735,10113796,Asia/Seoul
160.3.91.140,160.3.91.140,172,373,US-TX,6342,888,79762,31.96263,-102.38076,5528929,America/Chicago
134.170.96.0,134.170.103.255,124,355,NL-NH,24093,24093,1053,52.37018,4.87324,10292266,Europe/Amsterdam2. 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 |
I. 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
4509,Hudson,Hudson,Гудзон,,Condado de Hudson,ハドソン,شهرستان هادسون، نیوجرسی,Hudson,哈德森,Hudsona,Hudsona,Hudson
8747,Waterloo Regional Municipality,Waterloo (Regionalverwaltung),Регионал муниципалитет Ватерлоо,,,ウォータールー地域,,Municipalité régionale de Waterloo,滑鐵盧區,Waterloo,Waterloo,Municipality Regional de Waterloo
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
373,Texas,Texas,Техас,텍사스 주,,テキサス州,تگزاس,Texas,德克萨斯州,Texas,Texas,Texas
291,Maharashtra,Maharashtra,Махараштра,Maarastra,Maarastra,マハーラーシュトラ州,مهاراشترا,Maharashtra,马哈拉施特拉邦,Maharastra,Maháráštra,Maharashtra
90201,County Cork,County Cork,Графство Корк,,,コーク州,,Comté de Cork,科克郡,Графство Корк,Cork,Contea di Cork
3720,Mumbai Suburban,Mumbai,Мумбаи,,,ムンバイ郊外,,Mumbai Suburban,孟买郊区,Bombaj,Bombaj,Suburban di Mumbai
3723,New Delhi,Neu-Delhi,Нью-Дели,Nova Deli,,ニューデリー,,New Delhi,新德里,Nueva Delhi,New Delhi,Nuova Delhi
15,India,Indien,Индия,Índia,Índia,インド,هند,Inde,印度,India,Indie,India
240018,United States of America,,,,,,,,,,,
240019,"Washington, D.C.",,,,,,,,,,,
24,South Korea,"Korea, Republik (Südkorea)",Республика Корея,대한민국,Coreia do Sul,大韓民国,کرهٔ جنوبی,"Corée, République de",韩国,Jižní Korea,Jižní Korea,Corea del Sud
850,Munster,Münster,Манстер,먼스터,,マンスター,مونستر,Munster,芒斯特省,Munster,Munster,- Sgranocchiati
283,Seoul,Seoul,Сеул,서울특별시,,ソウル特別市,,Séoul,首尔特别市,Soul,Soul,Seul
28,United States,USA,США,Estados Unidos,Estados Unidos,アメリカ合衆国,ایالات متحدهٔ امریکا,États-Unis,美国,Estados Unidos,Spojené státy americké,Stati Uniti d'America
24093,Amsterdam,Amsterdam,Амстердам,암스테르담,Amesterdão,アムステルダム,آمستردام,Amsterdam,阿姆斯特丹,Amsterdam,Amsterdam,Amsterdam
32,Netherlands,Niederlande,Нидерланды,Holanda,Holanda,オランダ王国,هلند,Pays-Bas,荷兰,Holanda,Nizozemsko,Olanda
6342,Ector County,Ector,Эктор,,Condado de Ector,エクター郡,شهرستان اکتور، تگزاس,Comté dEctor,厄克托縣,Эктор,Ector,Contea di Ector
240035,Republic of Korea,,,,,,,,,,,
202803,Naucalpan de Juárez,Naucalpan de Juárez,Наукальпан-де-Хуарес,,,ナウカルパンデフアレス,,Naucalpan de Juárez,诺卡尔潘德华雷斯,Naucalpan de Juárez,Naucalpan de Juárez,Naucalpan de Juárez
2071,Cork,Cork,Корк,Cork,,コーク,,Cork,科克,Cork,Cork,Sughero
4556,Dallas County,Dallas,Даллас,,Condado de Dallas,ダラス郡,شهرستان دالاس، تگزاس,Comté de Dallas,達拉斯縣,Даллас,Dallasu,Contea di Dallas
66,Mexico,Mexiko,Мексика,México,México,メキシコ合衆国,مکزیک,Mexique,墨西哥,México,Mexiko,Messico
4330,Dallas,Dallas,Даллас,,Condado de Dallas,ダラス郡,شهرستان دالاس، تگزاس,Comté de Dallas,達拉斯縣,Z Dallasu,Z Dallasu,Dallas
297,New Jersey,New Jersey,Нью-Джерси,Nova Jérsia,Nova Jérsia,ニュージャージー州,نیو جرسی,New Jersey,新泽西州,Nueva Jersey,New Jersey,New Jersey
151541,Yongsan,Yongsan,Ёнсан,,,龍山,,Yongsan,龙山,Yongsan,Yongsan,Yongsan
239935,Republic of India,,,,,,,,,,,
64,Ireland,Irland,Ирландия,Irlanda,Irlanda,アイルランド,ایرلند,Irlande,爱尔兰,Irlanda,Irsko,Irlanda
65,Canada,Kanada,Канада,Canadá,Canadá,カナダ,کانادا,Canada,加拿大,Canadá,Kanada,Canada
66,Mexico,Mexiko,Мексика,México,México,メキシコ合衆国,مکزیک,Mexique,墨西哥,México,Mexiko,Messico
355,North Holland,Nordholland,Северная Голландия,Holanda do Norte,Holanda do Norte,ノールトホラント,,Hollande-Septentrionale,北荷蘭省,Holanda Septentrional,Severní Holandsko,Olanda Settentrionale
8943,Waterloo,Waterloo,Ватерлоо,,,ウォータールー,,Waterloo,滑铁卢,Waterloo,Waterloo,Waterloo
840,Dublin,Dublin,Дублин,,,ダブリン,,Dublin,都柏林,Dublin,Dublin,Dublino
3729,Mumbai,Mumbai,Мумбаи,Mumbai,,ムンバイ,,Bombay,孟买,Bombay,Bombaj,Mumbai
888,Odessa,Odessa,Одесса,,Oblast de Odesa,オデッサ,,Oblast d'Odessa,敖德萨州,Oděsa,Oděsa,Odessa
130706,Naucalpan de Juarez,Naucalpan de Juarez,Наукальпан-де-Хуарес,,,ナウカルパン,,Naucalpan de Juarez,诺卡尔潘德华雷斯,Naucalpan de Juarez,Naucalpan de Juarez,Naucalpan de Juarez
603,Mexico City,Mexiko-Stadt,Мехико,,,メキシコシティ,,Ville de Mexico,墨西哥城,Ciudad de México,Mexiko,Città del Messico
597,Ontario,Ontario,Онтарио,Ontário,Ontário,オンタリオ州,انتاریو,Ontario,安大略,V Ontariu,V Ontariu,Ontario
239970,United Mexican States (Mexico),,,,,,,,,,,
239976,Kingdom of the Netherlands,,,,,,,,,,,
4588,Ottawa,Ottawa,Оттава,Otava,Condado de Ottawa,オタワ,شهرستان اتاوا، اکلاهما,Ottawa,渥太華縣,Ottawa,Ottawa,Ottawa
31781,Secaucus,Secaucus,Секакус,,,セコーカス,سیکوکس، نیوجرسی,Secaucus,赛考克斯,Secaucus,Secaucus,Secaucus
283,Seoul,Seoul,Сеул,서울특별시,,ソウル特別市,,Séoul,首尔特别市,Soul,Soul,Seul
331,Punjab,Punjab,Пенджаб,펀자브 주,,パンジャーブ州,پنجاب,Penjab,旁遮普邦,Paňdžáb,Paňdžáb,Punjab
8843,Ludhiana,Ludhiana,Лудхияна,Ludhiana,,ルディアーナ,,Ludhiana,盧迪亞納縣,Ludhiana,Ludhiana,Ludhiana
24093,Amsterdam,Amsterdam,Амстердам,암스테르담,Amesterdão,アムステルダム,آمستردام,Amsterdam,阿姆斯特丹,Amsterdam,Amsterdam,Amsterdam3. 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 |
I. 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
117,NA,6,MX,MEX,MEX,66,239970,603,MXN,Mexican Peso,Mex$,+52,.mx,es-MX
193,AS,5,KR,KOR,KOR,24,240035,283,KRW,Won,₩,+82,.kr,"ko-KR,en"
74,EU,7,IE,IRL,IRL,64,64,840,EUR,Euro,€,+353,.ie,"en-IE,ga-IE"
172,NA,6,US,USA,USA,28,240018,240019,USD,US Dollar,$,+1,.us,"en-US,es-US,haw,fr"
29,NA,6,CA,CAN,CAN,65,65,4588,CAD,Canadian Dollar,C$,+1,.ca,"en-CA,fr-CA,iu"
76,AS,5,IN,IND,IND,15,239935,3723,INR,Indian Rupee,₹,+91,.in,"en-IN,hi,bn,te,mr,ta,ur,gu,kn,ml,or,pa,as,bh,sat,ks,ne,sd,kok,doi,mni,sit,sa,fr,lus,inc"
124,EU,7,NL,NLD,NED,32,239976,24093,EUR,Euro,€,+31,.nl,"nl-NL,fy-NL"4. File Relationship Diagram
File Format & Encoding
All Standard 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 Standard 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 Standard IP to Location MMDB database archive, you'll find the following files (with their types noted):
- File Size: 1.36 GB
- Entries: 29.3M
Documentation for dataset contents, schema, usage, and support.
- File Size: 12.11 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 Standard 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 city-level geolocation data for IPv4 and IPv6 ranges. Each response includes multilingual details for country, state, district, and city, along with geographic coordinates, time zone, GeoNames ID, connection type, and supporting metadata such as codes, currency, and language tags.
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
{
"location": {
"city": {
"name": {
"cs": "Ludhiana",
"de": "Ludhiana",
"en": "Ludhiana",
"es": "Ludhiana",
"fa": "",
"fr": "Ludhiana",
"it": "Ludhiana",
"ja": "ルディアーナ",
"ko": "Ludhiana",
"pt": "",
"ru": "Лудхияна",
"zh": "盧迪亞納縣"
}
},
"coordinates": {
"latitude": "30.90725",
"longitude": "75.84919"
},
"country": {
"capital": {
"cs": "New Delhi",
"de": "Neu-Delhi",
"en": "New Delhi",
"es": "Nueva Delhi",
"fa": "",
"fr": "New Delhi",
"it": "Nuova Delhi",
"ja": "ニューデリー",
"ko": "Nova Deli",
"pt": "",
"ru": "Нью-Дели",
"zh": "新德里"
},
"code2": "IN",
"code3": "IND",
"code_ioc": "IND",
"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": "INR",
"name": {
"en": "Indian Rupee"
},
"symbol": "₹"
},
"metadata": {
"calling_code": "+91",
"languages": "en-IN,hi,bn,te,mr,ta,ur,gu,kn,ml,or,pa,as,bh,sat,ks,ne,sd,kok,doi,mni,sit,sa,fr,lus,inc",
"tld": ".in"
},
"name": {
"cs": "Indie",
"de": "Indien",
"en": "India",
"es": "India",
"fa": "هند",
"fr": "Inde",
"it": "India",
"ja": "インド",
"ko": "Índia",
"pt": "Índia",
"ru": "Индия",
"zh": "印度"
},
"name_official": {
"cs": "",
"de": "",
"en": "Republic of India",
"es": "",
"fa": "",
"fr": "",
"it": "",
"ja": "",
"ko": "",
"pt": "",
"ru": "",
"zh": ""
}
},
"district": {
"name": {
"cs": "Ludhiana",
"de": "Ludhiana",
"en": "Ludhiana",
"es": "Ludhiana",
"fa": "",
"fr": "Ludhiana",
"it": "Ludhiana",
"ja": "ルディアーナ",
"ko": "Ludhiana",
"pt": "",
"ru": "Лудхияна",
"zh": "盧迪亞納縣"
}
},
"geoname_id": "11857537",
"state": {
"code": "IN-PB",
"name": {
"cs": "Paňdžáb",
"de": "Punjab",
"en": "Punjab",
"es": "Paňdžáb",
"fa": "پنجاب",
"fr": "Penjab",
"it": "Punjab",
"ja": "パンジャーブ州",
"ko": "펀자브 주",
"pt": "",
"ru": "Пенджаб",
"zh": "旁遮普邦"
}
},
"zipcode": "141001"
},
"time_zone": "Asia/Kolkata"
}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 Standard 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 Standard 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 Standard 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 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.