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.
- File Size: 9.67 KB
- Entries: 254
- Fields: 15
db-place.csv.gzMultilingual place names for cities, districts, states, countries, and continents.
- File Size: 13.17 MB
- Entries: 354.1K
- Fields: 13
db-ip-location.csv.gzIP ranges mapped to locations with place IDs (for multilingual responses), ZIP codes, coordinates, time zone, and connection type.
- File Size: 448.91 MB
- Entries: 29.9M
- Fields: 16
README.mdDocumentation for dataset contents, schema, usage, and support.
- File Size: 4.55 KB
checksum.txtSHA-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 |
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.
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
202.83.50.21,202.83.50.21,76,736,IN-KL,4783,240077,8.415,high,,682005,9.93123,76.2673,10177040,Asia/Kolkata,Cable
182.177.150.75,182.177.150.75,134,1292,PK-KP,10590,10590,5.013,medium,,21300,34.33126,73.198,1170951,Asia/Karachi,Leased Line
205.250.74.37,205.250.74.37,29,611,CA-BC,8687,38898,3.708,high,,V1C,49.51297,-115.7694,6507873,America/Edmonton,Fiber
191.255.84.0,191.255.84.72,23,379,BR-SP,379,379,8.531,high,,01325,-23.55577,-46.63956,12377012,America/Sao_Paulo,DSL
99.139.209.19,99.139.209.19,172,592,US-WI,6801,33763,7.268,medium,658,54911,44.26193,-88.41538,5244080,America/Chicago,DSL
66.117.238.222,66.117.238.222,172,588,US-KY,4544,6516,5.093,high,515,45202,39.10312,-84.51202,9863146,America/New_York,Leased Line
208.98.142.243,208.98.142.243,172,606,US-ID,8185,37760,5.961,high,757,83619,44.00766,-116.91655,5593708,America/Boise,DSL
36.161.58.204,36.161.58.204,35,1335,CN-AH,240078,124504,5.827,medium,,244000,30.9342,117.8153,9072900,Asia/Shanghai,Mobile
1.178.130.23,1.178.130.23,198,803,PS-WB,23303,23303,6.332,high,,1570,32.22267,35.26215,8072891,Asia/Hebron,Fiber
71.173.198.83,71.173.198.83,172,381,US-PA,3959,31930,3.396,high,566,17055,40.2132,-77.00834,6498436,America/New_York,Fiber2.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.
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
611,British Columbia,British Columbia,Британская Колумбия,Colúmbia Britânica,Colúmbia Britânica,ブリティッシュコロンビア州,بریتیش کلمبیا,Colombie-Britannique,不列颠哥伦比亚,Columbia Británica,Britská Kolumbie,Columbia Britannica
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
240077,Cochin,,,,,,,,,,,
8,South America,Südamerika,Южная Америка,América do Sul,América Do Sul,南アメリカ,امریکای جنوبی,Amérique du Sud,南美洲,Sudamérica,Jižní Amerika,America del Sud
4783,Ernakulam,Ernakulam,Эрнакулам,,,エルナクラム,,Ernakulam,埃尔纳库兰,Ernakulam,Ernakulam,Ernakulam
3723,New Delhi,Neu-Delhi,Нью-Дели,Nova Deli,,ニューデリー,,New Delhi,新德里,Nueva Delhi,New Delhi,Nuova Delhi
12,China,China,Китай,China,China,中国,چین,Chine,中国,China,Čína,Cina
15,India,Indien,Индия,Índia,Índia,インド,هند,Inde,印度,India,Indie,India
240018,United States of America,,,,,,,,,,,
240019,"Washington, D.C.",,,,,,,,,,,
275,Beijing,Peking,Пекин,,,北京,,Municipalité de Pékin,北京,Peking,Peking,Pechino
239894,Federative Republic of Brazil,,,,,,,,,,,
803,West Bank,Westbank,Западный Шорс,,,ヨルダン川西岸,,Cisjordanie,西岸,Západní břeh,Západní břeh,Cisgiordania
381,Pennsylvania,Pennsylvania,Пенсильвания,Pensilvânia,Pensilvânia,ペンシルベニア州,پنسیلوانیا,Pennsylvanie,宾夕法尼亚州,Pensilvania,Pensylvánie,Pennsylvania
606,Idaho,Idaho,Айдахо,아이다호 주,,アイダホ州,آیداهو,Idaho,爱达荷州,Idaho,Idaho,Idaho
28,United States,USA,США,Estados Unidos,Estados Unidos,アメリカ合衆国,ایالات متحدهٔ امریکا,États-Unis,美国,Estados Unidos,Spojené státy americké,Stati Uniti d'America
239901,People’s Republic of China,,,,,,,,,,,
240039,State of Palestine,,,,,,,,,,,
588,Kentucky,Kentucky,Кентукки,켄터키 주,,ケンタッキー州,کنتاکی,Kentucky,肯塔基州,Kentucky,Kentucky,Kentucky
736,Kerala,Kerala,Керала,케랄라 주,,ケーララ州,کرالا,Kerala,喀拉拉邦,Kérala,Kérala,Kerala
23303,Nablus,Sichem,Наблус,,,ナーブルス,,Naplouse,纳布卢斯,Siquem,Nablus,Nablus
10590,Mansehra,Mansehra,Мансехра,,,マンセラ,,Mansehra,曼瑟拉,Mansehra,Mansehra,Mansehra
45,Brazil,Brasilien,Бразилия,Brasil,Brasil,ブラジル連邦共和国,برزیل,Brésil,巴西,Brasil,Brazílie,Brasile
5163,Brasilia,Brasilia,Бразилиа,,,ブラジリア,,Brasilia,巴西利亚,Brasilia,Brasília,Brasilia
3959,Cumberland,Cumberland,Камберленд,,Condado de Cumberland,カンバーランド郡,شهرستان کامبرلند، پنسیلوانیا,Comté de Cumberland,坎伯蘭縣,Cumberland,Cumberland,Cumberland
6516,Covington,Covington,Ковингтон,,Condado de Covington,コビントン郡,شهرستان کاوینگتون، آلاباما,Comté de Covington,卡温顿县,Covington,Covington,Covington
240078,Tongguan,,,,,,,,,,,
239935,Republic of India,,,,,,,,,,,
65,Canada,Kanada,Канада,Canadá,Canadá,カナダ,کانادا,Canada,加拿大,Canadá,Kanada,Canada
31930,Mechanicsburg,Mechanicsburg,Механиксбург,,,メカニクスバーグ,,Mechanicsburg,机械师斯堡,Mechanicsburg,Mechanicsburg,Mechanicsburg
8687,East Kootenay,Ost-Kootenay,Восточный Кутеней,,,イーストクートニー,,Kootenay Est,科特奈,Kootenay,Kootenay,Kootenay orientale
37760,Fruitland,Fruitland,Фруитленд,,,フルーツランド,فروتلند، آیداهو,Fruitland,弗鲁兰德,Ovocná půda,Ovocná půda,Fruitland
6801,Outagamie County,Outagamie,Аутагейми,,Condado de Outagamie,アウタガミ郡,شهرستان اوتاگامی، ویسکانسین,Comté dOutagamie,奥塔加米縣,Аутагейми,Okres Outagamie,Contea di Outagamie
8185,Payette County,Payette,Пейетт,,Condado de Payette,ペイエット郡,شهرستان پایت، آیداهو,Comté de Payette,佩埃特縣,Пейетт,Okres Payette,Contea di Payette
124504,Tongling,Tongling,Тунглинг,,,トンリング,,Tongler,铜陵,Tongling,Tongling,- Sbagliante
90,Pakistan,Pakistan,Пакистан,Paquistão,Paquistão,パキスタン・イスラム共和国,پاکستان,Pakistan,巴基斯坦,Pakistán,Pákistán,Pakistan
93,Palestinian Territory,Staat Palästina,Палестина,팔레스타인,Território da Palestina,パレスチナ領土,فلسطین,État de Palestine,巴勒斯坦,palestinské,palestinské,Territorio Palestinese
1335,Anhui,Anhui,Аньхой,,,安徽省,,Province d'Anhui,安徽,Anhui,Anhui,Anhui
379,Sao Paulo,São Paulo,Сан-Паулу,São Paulo,São Paulo,サンパウロ市,,Sao Paulo,圣保罗,São Paulo,São Paulo,San Paolo
740,Islamabad,Islamabad,Исламабад,Islamabade,,イスラマバード,,Islamabad,伊斯兰堡,Islamabad,Islámábádu,Islamabad
4588,Ottawa,Ottawa,Оттава,Otava,Condado de Ottawa,オタワ,شهرستان اتاوا، اکلاهما,Ottawa,渥太華縣,Ottawa,Ottawa,Ottawa
1292,Khyber Pakhtunkhwa,Khyber Pakhtunkhwa,Хайбер Пахтунхва,,,カイバルパクトゥンクワ州,,Khyber Pakhtunkhwa,开伯尔·普赫图赫瓦,Pakhtunchwa,Pakhtunchwa,Khyber Pakhtunkhwa
33763,Appleton,Appleton,Аплтон,애플턴,,アップルトン,اپلتون، ویسکانسین,Appleton,阿普尔顿,Appleton,Appleton,Appleton
239985,Islamic Republic of Pakistan,,,,,,,,,,,
592,Wisconsin,Wisconsin,Висконсин,위스콘신 주,,ウィスコンシン州,ویسکانسین,Wisconsin,威斯康辛州,Wisconsin,Wisconsin,Wisconsin
4544,Kenton County,Kenton,Кентон,,Condado de Kenton,ケントン郡,شهرستان کنتون، کنتاکی,Comté de Kenton,肯頓縣,Кентон,Kenton,Contea di Kenton
136185,East Jerusalem,Ost-Jerusalem,Восточный Иерусалим,,,東エルサレム,,Jérusalem-Est,东耶路撒冷,Východní Jeruzalém,Východní Jeruzalém,Gerusalemme Est
38898,Cranbrook,Cranbrook,Кранбрук,,,クランブルック,کرنبروک,Cranbrook,克兰布鲁克,Cranbrook,Cranbrook,Cranbrook3.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.
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
134,AS,5,PK,PAK,PAK,90,239985,740,PKR,Pakistan Rupee,₨,+92,.pk,"ur-PK,en-PK,pa,sd,ps,brh"
198,AS,5,PS,PSE,PLE,93,240039,136185,ILS,New Israeli Sheqel,₪,+970,.ps,ar-PS
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"
172,NA,6,US,USA,USA,28,240018,240019,USD,US Dollar,$,+1,.us,"en-US,es-US,haw,fr"
35,AS,5,CN,CHN,CHN,12,239901,275,CNY,Yuan Renminbi,¥,+86,.cn,"zh-CN,yue,wuu,dta,ug,za"
29,NA,6,CA,CAN,CAN,65,65,4588,CAD,Canadian Dollar,C$,+1,.ca,"en-CA,fr-CA,iu"
23,SA,8,BR,BRA,BRA,45,239894,5163,BRL,Brazilian Real,R$,+55,.br,"pt-BR,es,en,fr"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.mmdb- File Size: 2.57 GB
- Entries: 29.9M
README.mdDocumentation for dataset contents, schema, usage, and support.
- File Size: 4.55 KB
checksum.txtSHA-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": "Cable",
"location": {
"accuracy_radius": "8.415",
"city": {
"name": {
"cs": "",
"de": "",
"en": "Cochin",
"es": "",
"fa": "",
"fr": "",
"it": "",
"ja": "",
"ko": "",
"pt": "",
"ru": "",
"zh": ""
}
},
"confidence": "high",
"coordinates": {
"latitude": "9.93123",
"longitude": "76.2673"
},
"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": "Ernakulam",
"de": "Ernakulam",
"en": "Ernakulam",
"es": "Ernakulam",
"fa": "",
"fr": "Ernakulam",
"it": "Ernakulam",
"ja": "エルナクラム",
"ko": "",
"pt": "",
"ru": "Эрнакулам",
"zh": "埃尔纳库兰"
}
},
"dma_code": "",
"geoname_id": "10177040",
"state": {
"code": "IN-KL",
"name": {
"cs": "Kérala",
"de": "Kerala",
"en": "Kerala",
"es": "Kérala",
"fa": "کرالا",
"fr": "Kerala",
"it": "Kerala",
"ja": "ケーララ州",
"ko": "케랄라 주",
"pt": "",
"ru": "Керала",
"zh": "喀拉拉邦"
}
},
"zipcode": "682005"
},
"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 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.
The public key may be provided as PEM-encoded text. Save it to a file named public-key.pem
Ensure OpenSSL is installed on your system. If not, install it using the following commands
On Linux, if openssl is not installed
sudo apt install opensslVerify OpenSSL installation:
openssl versionTo verify the database file, run the following command, replacing the placeholders with your actual file paths:
openssl dgst -sha256 -verify <path-to-public-key.pem> -signature <path-to-signature-file.sig> <path-to-database-file.zip>Example output:
Verified OKif verification FAILED do not use the file, re-download the database and signature from official IPGeolocation endpoints. If the issue persists, please contact our support team.
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.
Always 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*your output may differ depending on the specific database archive you downloaded.
If 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.
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 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.
