IP Whois Database
Overview
Our IP WHOIS Database delivers clean, consistently parsed ownership data for any IPv4/IPv6 range, so you can verify who controls an address block, identify the right contacts, and act with confidence. Use it to harden security, speed up network troubleshooting, validate IP ownership during onboarding or investigations, and enrich tooling with reliable WHOIS insights across the global internet.
Raw WHOIS text is preserved for auditability. Available in CSV, JSON and MMDB formats. 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 detailed IP WHOIS information. These files are designed for bulk imports and integration into relational databases.
2.Archive Content
After downloading and extracting the IP Whois CSV database archive, you’ll find the following files (with their types noted):
db-ip-whois.csv.gzIP range links to WHOIS details: name, country, domain, RIR, and raw WHOIS record.
db-org-details.csv.gzLinks an organization ID to its handle, name, type, and contact details.
db-handles-details.csv.gzLinks the network handle ID to its name, country, address, and contact details.
README.mdDocumentation for dataset contents, schema, usage, and support.
db-ip-whois.md5Always 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-whois.csv.gz: OK
db-org-details.csv.gz: OK
db-handles-details.csv.gz: OK
README.md: OK
db-ip-whois.md5: OKIf 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.
Schema
This section describes the schema of each file included in the IP Whois Database archive. For every file, you’ll find its purpose, field definitions, and examples to help with integration.
1.db-ip-whois.csv.gz
This file contains detailed WHOIS information for IP address ranges. It maps each IP block to the name, country, domain, and RIR, as well as various contact handle IDs and the full raw_whois record.
| 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 |
| name | string | The name associated with the IP range in the WHOIS record. | Yes | Example Network |
| country | string | The country code associated with the IP range in the WHOIS record. | Yes | US |
| domain | string | The domain name associated with the IP range in the WHOIS record. | Yes | example.com |
| rir | string | The Regional Internet Registry (RIR) that manages the IP range. | Yes | ARIN |
| org_id | number | The unique identifier for the organization associated with the IP range. | Yes | 1 |
| admin_handles_id | number | The unique identifier for the administrative contact handle associated with the IP range. | Yes | 1 |
| tech_handles_id | number | The unique identifier for the technical contact handle associated with the IP range. | Yes | 1 |
| abuse_handles_id | number | The unique identifier for the abuse contact handle associated with the IP range. | Yes | 1 |
| irt_handles_id | number | The unique identifier for the Incident Response Team (IRT) contact handle associated, with the IP range. | Yes | 1 |
| raw_whois | string | The raw WHOIS record data associated with the IP range. | Yes | Raw WHOIS data string... |
| date_created | string | The date when the WHOIS record for the IP range was created. | Yes | 2020-01-01T12:00:00Z |
| date_updated | string | The date when the WHOIS record for the IP range was last updated. | Yes | 2023-01-15T12:00:00Z |
org_id joins to db-org-details.id to get organization details for IP, and *handles_id keys join to db-handles-details.id to get contact handles details.Example Records
2.db-handles-details.csv.gz
This file contains detailed information on various network handles. It links a unique ID to a specific handle, name, country, address, and contact details such as email, phone, and fax.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| id | number | The unique identifier for the WHOIS handle. | No | 1 |
| handle | string | The WHOIS handle. | No | EXAMPLE-HANDLE |
| name | string | The name associated with the WHOIS handle. | No | John Doe |
| country | string | The country associated with the WHOIS handle. | Yes | US |
| string | The email address associated with the WHOIS handle. | Yes | contact@example.org | |
| phone | string | The phone number associated with the WHOIS handle. | Yes | +1-800-555-0123 |
| fax | string | The fax number associated with the WHOIS handle. | Yes | +1-800-555-0456 |
| address | string | The physical address associated with the WHOIS handle. | Yes | 123 Example St, Example City, EX 12345, Country |
| date_updated | string | The date when the WHOIS handle information was last updated. | Yes | 2023-01-15T12:00:00Z |
| source | string | The source of the WHOIS handle information. | Yes | ARIN |
id in the db-handles-details.csv.gz file joins to the *_handles_id fields in db-ip-whois.csv.gz (e.g., admin_handles_id,tech_handles_id,abuse_handles_id,irt_handles_id).Example Records
3.db-org-details.csv.gz
This file provides detailed organization information. It links a unique ID to an organization's handle, name, type, address, country, and various contact details including email, phone, and fax.
| Field | Type | Description | Can be empty? | Example |
|---|---|---|---|---|
| id | number | The unique identifier for the WHOIS organization. | No | 1 |
| handle | string | The handle of the WHOIS organization. | Yes | EXAMPLE-ORG |
| name | string | The name of the WHOIS organization. | No | Example Organization |
| type | string | The type of the WHOIS organization. | Yes | organization |
| address | string | The address of the WHOIS organization. | Yes | 123 Example St, Example City, EX 12345, Country |
| country | string | The country of the WHOIS organization. | Yes | US |
| string | The email address of the WHOIS organization. | Yes | contact@example.org | |
| phone | string | The phone number of the WHOIS organization. | Yes | +1-800-555-0123 |
| fax | string | The fax number of the WHOIS organization. | Yes | +1-800-555-0456 |
| date_updated | string | The date when the WHOIS organization information was last updated. | Yes | 2023-01-15T12:00:00Z |
| source | string | The source of the WHOIS organization information. | Yes | ARIN |
id in the db-org-details.csv.gz file joins to the org_id field in db-ip-whois.csv.gz (linking each IP range to its organization details).Example Records
4.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 for person and organization handle files, ensuring consistent and accurate data across for all the records.
File Format & Encoding
All IP Whois 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 two files: one MMDB file containing all the data (organization and contact handle details), a README file, and a checksum file, and one checksum file, all compressed together in a ZIP file for easy delivery.
2.Archive Content
After downloading and extracting the IP Whois MMDB database archive, you’ll find the following files (with their types noted):
db-ip-whois.mmdbFull WHOIS details for IP addresses: name, country, domain, RIR, contact IDs, and raw WHOIS record.
README.mdDocumentation for dataset contents, schema, usage, and support.
db-ip-whois.md5Always 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-whois.mmdb: OK
README.md: OK
db-ip-whois.md5: OKIf 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.
Response Schema
This section describes the structure of the data returned from the IP Whois 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-whois.mmdb
This file contains detailed WHOIS mappings for both IPv4 and IPv6 address ranges. Below is an example of the structure you'll find 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.
Example Records
Data Format & Constraints
- All fields defined in the schema are always present in the IP Whois 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 Whois database, we’ll send you static download links for the archive in your chosen formats. These links never change, so you can use them both for your initial download and for all future updates.
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.
