IP Hosting Database
Overview
Need to know which hosting provider or data center an IP address belongs to? Our IP to Hosting Database, which is a part of our Security tier, lets you map any IPv4 or IPv6 address to its hosting infrastructure. It helps you pinpoint hosting providers and data centers so you can better understand who’s really behind the traffic hitting your systems.
The database is kept fresh with daily updates, so you’re always working with the latest IP-to-hosting mappings as networks, ranges, and infrastructure change. The files are lightweight and easy to work with, making it simple to plug them into your existing workflows, tools, or pipelines without adding overhead.
In this documentation, you’ll find everything you need: what’s included in the archives, the file structure, how to verify your downloads before importing them, and a few practical examples to help you get started quickly and confidently.
Available Database Formats
CSV Database Documentation
1. Overview
The CSV version 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 IP to Hosting CSV database archive, you'll find the following files (with their types noted):
db-ip-hosting.csv.gzEach start_ip–end_ip link to a hosting_provider name.
- File Size: 35.54 MB
- Entries: 5.9M
- Fields: 3
README.mdDocumentation for dataset contents, schema, usage, and support.
- File Size: 4.55 KB
checksum.txtSHA-256 checksums for verifying file integrity.
- File Size: 163 Bytes
Schema
This section describes the schema of each file included in the IP to Hosting Database archive. For every file, you'll find its purpose, field definitions, and examples to help with integration.
1. db-ip-hosting.csv.gz
This file contains IP address ranges associated with hosting providers. It maps each IP block to a specific hosting provider.
| 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 |
| hosting_provider | string | The name of the hosting service provider associated with the IP range. | Yes | DigitalOcean |
I. Example Records
start_ip,end_ip,hosting_provider
1.14.133.74,1.14.133.74,Shenzhen Tencent Computer Systems Company Limited
2.56.190.149,2.56.190.149,Packethub S.A.
2.57.250.163,2.57.250.255,M247 Europe SRL
2.59.157.187,2.59.157.187,Packethub S.A.
2.137.227.96,2.137.227.96,TELEFONICA DE ESPANA S.A.U.
2.138.250.0,2.138.250.255,TELEFONICA DE ESPANA S.A.U.
2.139.25.0,2.139.25.255,TELEFONICA DE ESPANA S.A.U.
3.1.201.178,3.1.201.178,"Amazon.com, Inc."
3.7.66.155,3.7.66.162,"Amazon.com, Inc."
3.7.97.136,3.7.97.136,"Amazon.com, Inc."
3.8.139.148,3.8.139.163,"Amazon.com, Inc."2. File Relationship Diagram
The diagram below illustrates the relationships between the various files included in the CSV database package and what kind of data file contains.
File Format & Encoding
All IP to Hosting 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
MMDB version of the database consists of three files: one MMDB file containing IP Hosting data, a README file, and a checksum file, all compressed together in a ZIP file for easy delivery.
2. Archive Content
After downloading and extracting the IP to Hosting MMDB database archive, you'll find the following files (with their types noted):
db-ip-hosting.mmdbContains a list of hosting provider IP addresses. It includes their hosting provider.
- File Size: 5.24 MB
- Entries: 5.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: 161 Bytes
Response Schema
This section describes the structure of the data returned from the IP to Hosting 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-hosting.mmdb
This file contains a comprehensive list of cloud provider IP addresses. It includes their hosting provider names.
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.
I. Example Records
{
"hosting_provider": "Shenzhen Tencent Computer Systems Company Limited"
}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 IP to Hosting 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-ip-hosting.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 IP to Hosting 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 IP to Hosting 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.
