Access authoritative WHOIS ownership, contact, and registry information for every routable IP range, including data from every RIR and RWHOIS.
range | source | name | country | status | org_id | tech_id | mnt_id | admin_id | abuse_id | geoloc | created | updated | raw |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
124.106.95.140 - 124.106.95.143 | APNIC | PREMIUM | PH | ASSIGNED NON-PORTABLE | NOC36-AP | PHIX-NOC-AP | NOC36-AP | AP713-AP | 2023-06-01 01:50:37.000 | *** | |||
156.231.166.0 - 156.231.166.255 | AFRINIC | OCTOPUS_WEB_SOLUTION_INC | JP | ASSIGNED PA | CIS1-AFRINIC | CIL1-M | LARUS-SERVICE-MNT | CIS1-AFRINIC | 2025-04-28 00:00:00.000 | 2025-04-28 00:00:00.000 | *** | ||
182.75.9.96 - 182.75.9.103 | APNIC | KOWN-2330410-Mumbai | IN | ASSIGNED NON-PORTABLE | NA40-AP | MAINT-IN-BBIL,IRT-BHARTI-IN | NA40-AP | AB913-AP | 2021-01-25 00:12:02.000 | *** | |||
194.22.165.192 - 194.22.165.199 | RIPE | SE-TEAMUGGLARP | SE | ASSIGNED PA | ORG-TUA2-RIPE | CM7765-RIPE | TELIANET-LIR | CM7765-RIPE | 2010-10-26 08:24:39.000 | 2013-10-02 05:46:58.000 | *** | ||
64.163.76.160 - 64.163.76.191 | ARIN | SBCIS-100829-151311 | US | Reassigned | C00105979 | ICC-ARIN,ZS44-ARIN,ROUTI59-ARIN | ABUSE7-ARIN | 2000-08-30 00:00:00.000 | 2000-08-30 00:00:00.000 | *** | |||
181.109.236.0/24 | LACNIC | Telecom Personal Bs As | AR | reallocated | AR-TPBA-LACNIC | ADI2 | ADI2 | ADI2 | 2024-10-01 00:00:00.000 | 2024-12-20 00:00:00.000 | *** | ||
62.30.226.47 - 62.30.226.47 | RIPE | LINDALE-HOMES-LIMITED | GB | ASSIGNED PA | ORG-CIL2-RIPE | NNMC1-RIPE | AS5089-MNT | DH687-RIPE | 2021-01-29 14:24:44.000 | 2021-01-29 14:24:44.000 | *** | ||
125.7.11.16 - 125.7.11.19 | APNIC | MCT-MNBAS28672003-004 | AU | ASSIGNED NON-PORTABLE | MCT2-AP | MAINT-AU-MCT,IRT-MCT-AU | MCT2-AP | AM2341-AP | 2021-01-06 13:28:49.000 | *** |
Track ownership, registry, and abuse contacts with rich WHOIS and RWHOIS metadata for IPv4 and IPv6 prefixes worldwide.
On this page we describe our standardized databases and fields available for licensing. We can also tailor any of our Whois and network data to your specific needs.
Details based on every registered inetnum/inet6num object.
Field | Description |
---|---|
range |
The IP address range covered by the record (CIDR or explicit range). |
id |
The unique identifier for the network object. |
source |
The registry of the record (e.g., APNIC, ARIN, RIPE, AFRINIC, LACNIC). |
name |
The registry object or allocation name. |
country |
Two-letter country code. |
status |
Allocation/assignment status reported by the registry. |
org_id |
Organization identifier from the registry. |
tech_id |
Technical contact handle/identifier. |
mnt_id |
Maintainer (mntner) identifier. |
admin_id |
Administrative contact handle/identifier. |
abuse_id |
Abuse contact handle/identifier. |
geoloc |
Geolocation coordinates string, if present. |
created |
Record creation timestamp. |
updated |
Record last updated timestamp. |
raw |
Raw text of the record. |
Details for every registered organization.
Field | Description |
---|---|
id |
The unique identifier for the organization. |
source |
The registry of the record (e.g., APNIC, ARIN, RIPE, AFRINIC, LACNIC). |
name |
The organization name. |
address |
The organization address. |
street |
The organization street. |
city |
The organization city. |
state |
The organization state. |
postalcode |
The organization postal code. |
country |
Two-letter country code. |
admin_id |
Administrative contact handles/identifiers. |
tech_id |
Technical contact handles/identifiers. |
mnt_id |
Maintainer (mntner) identifiers. |
abuse_id |
Abuse contact handles/identifiers. |
email |
The organization email. |
created |
Record creation timestamp. |
updated |
Record last updated timestamp. |
raw |
Raw text of the record. |
Details for every registered contact and contact-type object — like roles, abuse contacts, and maintainers.
Field | Description |
---|---|
id |
The unique identifier for the contact record. |
source |
The registry of the record (e.g., APNIC, ARIN, RIPE, AFRINIC, LACNIC). |
type |
The type of contact, based on the type of object the contact data was sourced from. For example: role , abuse , admin , tech , routing , noc , mntner . |
name |
The contact name. |
mobilephone |
The contact mobile phone number. |
officephone |
The contact office phone number. |
fax |
The contact fax number. |
address |
The contact address. |
country |
Two-letter country code. |
email |
The contact email. |
abuse_email |
The contact abuse email. |
created |
Record creation timestamp. |
updated |
Record last updated timestamp. |
raw |
Raw text of the record. |
Details for every registered, active and inactive Autonomous System (ASN).
We also provide a free, daily-updated IP to ASN database, and a separate Autonomous System database enriched with BGP and organizational data.
Field | Description |
---|---|
asn |
The Autonomous System Number. |
rir |
The Regional Internet Registry that assigned the ASN (APNIC, ARIN, LACNIC, RIPE, AFRINIC). |
status |
The RIR assignment/allocation status for the ASN. |
active |
Whether the ASN is active. |
country_code |
The ISO 3166-1 alpha-2 country code of the ASN. |
name |
The short name of the ASN. |
created |
Date the ASN was created/assigned. |
updated |
Last updated timestamp from the registry. |
org_id |
Organization identifier from the registry. |
tech_id |
Technical contact handle/identifier. |
mnt_id |
Maintainer (mntner) identifier. |
admin_id |
Administrative contact handle/identifier. |
abuse_id |
Abuse contact handle/identifier. |
Details for networks represented by RWHOIS servers. RWHOIS servers are used by the ARIN registry to handle smaller network delegations.
Field | Description |
---|---|
range |
The IP address range covered by the record (CIDR or explicit range). |
source |
The registry of the record, usually ARIN. |
rwhois_server |
The RWHOIS server that provided the record. |
id |
The identifier for the network. |
name |
The network name. |
street |
Street address related to the network, if available. |
city |
City related to the network, if available. |
region |
Region/state related to the network, if available. |
postalcode |
Postal code related to the network, if available. |
country |
Two-letter country code. |
org_name |
Name of the organization associated with the network, if available. |
org_email |
Email of the organization associated with the network, if available. |
tech_email |
Email of the tech contact associated with the network, if available. |
abuse_email |
Email for the abuse contact associated with the network, if available. |
created |
Record creation timestamp. |
updated |
Record last updated timestamp. |
Abuse contacts are covered by our IP Whois databases. We also offer a separate Abuse Contacts database to support network intelligence and cybersecurity use cases.
Field | Description |
---|---|
range |
The IP address range covered by the abuse contact (CIDR or explicit range). |
name |
The name of the abuse contact. |
address |
The physical address of the network abuse contact. |
country |
The ISO 3166-1 alpha-2 country code of the network abuse contact. |
email |
The email address of the network abuse contact. |
network |
The network range of the IP address. |
phone |
The phone number of the network abuse contact. |
Our WHOIS and RWHOIS data is available in CSV or JSON format by default, or we can deliver custom data formats and specific fields to fit your workflow.
Our datasets cover all active/allocated networks and associated objects from all RIRs and RWHOIS servers. We also have historical data available on request.
Complete IP Whois data from every Regional Internet Registry (RIR) and RWHOIS server. Fetched daily and parsed into structured network, organization, contact, and ASN objects.
Get abuse contact data for every registered IP address. Name, email, phone number, and address.
To purchase a database for internal business use, fill out the form so we can verify your use case. No sales calls — we’ll send you a direct purchase link after verification.
For commercial or redistribution use, data samples, or a quote for a custom dataset, get in touch and we’ll get back to you as soon as possible.
You can also integrate high-accuracy geolocation, network, and threat & privacy data in minutes with our IP geolocation API, free up to 1,000 requests per day.
The IP Whois Database is a downloadable dataset with ownership, registry, and contact information for IP address ranges. Use it to identify network operators, route traffic appropriately, and automate compliance workflows.
Our daily data pipeline constantly scans for updated networks and registry information. From this process, we create our bundled datasets weekly. We can also support custom update schedules — just get in touch.
Dozens of fields are available across each WHOIS object type (networks, organizations, contacts, and ASNs). For example, IP address/network range, organization names, contact information, allocation dates, registry identifiers, and related IP ranges.
Need specific attributes? Get in touch and we can tailor the dataset.
Yes. Customers often pair WHOIS with our geolocation, ASN, and threat datasets to build a complete enrichment pipeline.
Yes. Request a sample via the form and we’ll send example records so you can validate coverage.
Our IP Whois database subscription includes access to our RWHOIS database. This includes details for networks represented by every RWHOIS server.
Yes, the dataset includes complete IPv4 and IPv6 WHOIS coverage so you can track all network deployments.
We think you’re in ...
Did we get it right?
Waiting for location...
Our policy for safe geolocation means we don’t identify specific individuals or households. When you submit your location here, we only keep a lower-accuracy version for a limited amount of time, without any other identifying data.
Read how this works in our privacy policy