IP Company Database
Overview
Our IP to Company Database enables you to accurately map IP addresses to the organizations behind them, including ISPs, enterprises, and hosting providers. Each record contains verified company names, domains, and network associations, making it an essential resource for B2B targeting, fraud prevention, cybersecurity, and infrastructure analysis. Updated daily and available in flexible formats (CSV, MMDB, or custom exports), this dataset helps you identify, analyze, and act on company-level IP intelligence with confidence.
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 is a set of Gzip-compressed CSV files containing IP ranges and their company details. Designed for bulk imports and integration into relational databases.
2.Archive Content
After downloading and extracting the IP to Company CSV database archive, you'll find the following files (with their types noted):
db-company-details.csv.gzGzip-compressed CSV linking unique company IDs to names, types, and domains.
- File Size: 43.31 MB
- Entries: 3.7M
- Fields: 4
db-ip-company.csv.gzEach start_ip, end_ip link to the company details ID that is related to the company-details file.
- File Size: 204.69 MB
- Entries: 30.2M
- 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: 255 Bytes
Schema
This section describes the schema of each file included in the IP to Company Database archive. For every file, you'll find its purpose, field definitions, and examples to help with integration.
1.db-ip-company.csv.gz
This file contains IP address ranges linked to company details. It maps each IP block to a unique company_details_id , which in turn corresponds to the company's name, type, and domain.
| 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 |
| id | number | The unique identifier for the company. | No | 1 |
company_details_id joins to db-company-details.id to get company details for IP.I.Example Records
start_ip,end_ip,company_details_id
64.121.162.182,64.121.162.182,2497747
67.204.52.72,67.204.53.55,3167968
170.203.199.128,170.203.199.128,2822385
58.21.203.200,58.21.203.200,600578
94.98.35.20,94.98.35.20,2640444
59.93.36.66,59.93.36.66,379246
149.51.51.0,149.51.51.255,2474726
2a02:29e0:1:135:101a:aaa0:a965:0,2a02:29e0:1:135:101a:aaa0:a965:ffff,2674100
61.3.147.197,61.3.147.197,379246
135.125.148.112,135.125.148.127,22876662.db-company-details.csv.gz
This file contains a list of companies with their corresponding names, types, and domains. Each company is assigned a unique ID for identification.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| id | number | The unique identifier for the company. | No | 1 |
| name | string | The name of the company. | No | Example Corp |
| type | string | The type of the company. | Yes | ISP |
| domain | string | The domain name of the company. | Yes | example.com |
id in the db-company-details.csv.gz file joins to the company_details_id field in db-ip-company.csv.gzI.Example Records
id,name,domain,type
2822385,"SpaceX Services, Inc.",spacex.com,ISP
2287666,OVH Hosting LDA,ovh.net,hosting
2474726,"Rackdog, LLC",rackdog.com,business
2640444,Saudi Telecom Company JSC,stc.com.sa,ISP
2674100,Seflow s.r.l.,seflow.net,ISP
2497747,RCN Corporation,rcn.com,ISP
379246,Bharat Sanchar Nigam Ltd,bsnl.co.in,Business
600578,China Unicom,chinaunicom.com,ISP
3167968,"Unwired Broadband, LLC",getunwired.com,ISP3.File Relationship Diagram
The diagram below illustrates the relationships between the various files included in the CSV database package. It shows how the main CSV file connects to reference tables through key fields, helping you understand the data structure and relationships at a glance.
File Format & Encoding
All IP to Company 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 all the 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 Company MMDB database archive, you'll find the following files (with their types noted):
db-ip-company.mmdbProvides all company details for IP addresses: name, type, and registered domain.
- File Size: 240.32 MB
- Entries: 30.2M
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 Company 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-security.mmdb
This file contains company mappings for both IPv4 and IPv6 address ranges. Below is an example of the structure you will encounter in the response.
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
{
"company": {
"domain": "rcn.com",
"name": {
"en": "RCN Corporation"
},
"type": "ISP"
}
}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 Company 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-company-details.csv.gz: OK
db-ip-company.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 Company 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 Company 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.
