IP Abuse Contact Database


Overview

Our IP Abuse Contact Database gives you instant access to the correct abuse desk for any routable IP that connecting you to verified addresses, phone numbers, and emails worldwide. By mapping IPs to the responsible operator (ISPs, cloud providers, hosting networks, and enterprises) and their preferred reporting channels, it streamlines abuse escalation, speeds up takedowns, and helps you quickly pinpoint the source of malicious or unwanted activity to keep your environment safer.

Updated daily and delivered in flexible formats (CSV, JSON, MMDB, or custom exports/API), each record includes organization and netblock context, primary abuse mailbox and phone. Below, you'll find full documentation of the archive contents, schema definitions, file specifications, and integration notes to help you integrate with SIEM/SOAR, ticketing, and security workflows—fast.


Available Database Formats

CSV
CSVCSV
  • File Size: 318.19 MB
  • Entries: 29.9M
  • Fields: 9
  • Last Updated: Today
MMDB
MMDBMMDB
  • File Size: 763.54 MB
  • Entries: 29.9M
  • Fields: 9
  • Last Updated: Today
Important
If you require our IP to Abuse Contact Database in a different format, such as Parquet or any custom structure, please feel free to reach out to us via our contact form. We are happy to accommodate specific format requests to meet your needs.

CSV Database Documentation


1.Overview

The CSV version is a set of Gzip-compressed CSV files containing IP ranges and their Abuse Contact details. Designed for bulk imports and integration into relational databases.


2.Archive Content

After downloading and extracting the IP to Abuse Contact CSV database archive, you'll find the following files (with their types noted):

db-abuse-details.csv.gz
db-abuse-details.csv.gzdb-abuse-details.csv.gz

Gzip-compressed CSV provides abuse contact info: unique ID, network, and contact details.

  • File Size: 111.32 MB
  • Entries: 12.3M
  • Fields: 8
db-ip-abuse.csv.gz
db-ip-abuse.csv.gzdb-ip-abuse.csv.gz

Each start_ip, end_ip link to the abuse details ID that is related to the abuse-details file.

  • File Size: 206.87 MB
  • Entries: 29.9M
  • Fields: 3
README.md
README.mdREADME.md

Documentation for dataset contents, schema, usage, and support.

  • File Size: 4.55 KB
checksum.txt
checksum.txtchecksum.txt

SHA-256 checksums for verifying file integrity.

  • File Size: 251 Bytes

Schema

This section describes the schema of each file included in the IP to Abuse Contact Database archive. For every file, you'll find its purpose, field definitions, and examples to help with integration.


1.db-ip-abuse.csv.gz

This file contains IP address ranges linked to abuse details. It maps each IP block to a unique abuse_details_id , which in turn corresponds to the abuse contact information.

FieldTypeDescriptionCan be empty?Example
start_ipstringThe starting IP address of the range in IPv4 or IPv6 format.No192.168.0.1
end_ipstringThe ending IP address of the range in IPv4 or IPv6 format.No192.168.0.255
idnumberThe unique identifier for the abuse contact.No1
Tip
abuse_details_id joins to db-abuse-details.id to get abuse contact information for IP.

I.Example Records

Example
start_ip,end_ip,abuse_details_id
202.83.50.21,202.83.50.21,9053784
182.177.150.75,182.177.150.75,7699976
205.250.74.37,205.250.74.37,9263600
191.255.84.0,191.255.84.72,8198055
99.139.209.19,99.139.209.19,5509570
66.117.238.222,66.117.238.222,2294295
208.98.142.243,208.98.142.243,9397770
36.161.58.204,36.161.58.204,688694
1.178.130.23,1.178.130.23,4586
71.173.198.83,71.173.198.83,2818393

2.db-abuse-details.csv.gz

This file provides detailed abuse contact information. It links a unique ID to a specific network, country, and other contact details, including name, address, emails, and phone numbers.

FieldTypeDescriptionCan be empty?Example
idnumberThe unique identifier for the abuse contact.No1
networkstringThe network associated with the abuse contact.Yes192.168.1.0/24
countrystringThe ISO 3166-1 alpha-2 code of the country associated with the abuse contact.YesUS
kindstringThe kind specifies whether the contact is a person or an organization.Yesgroup
nameobjectThe name (english) of the abuse contact.YesAbuse Team
addressstringThe physical address of the abuse contact.Yes1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
emailsstringComma-separated email addresses associated with the abuse contact.Yesabuse@example.com
phone_numbersstringComma-separated phone numbers associated with the abuse contact.Yes+1-800-555-0199
Tip
id in the db-abuse-details.csv.gz file joins to the abuse_details_id field in db-ip-abuse.csv.gz

I.Example Records

Example
id,network,country,kind,name,address,emails,phone
2294295,66.117.192.0/18,,group,Fuse Internet Access Abuse Team,"209 W. Seventh St.
MS 121-550
Cincinnati
OH
45202
United States",abuse@fuse.net,+1-513-397-6598
9397770,208.98.142.0/23,,org,Farmers Mutual Telephone Company,"319 SW 3rd St
Fruitland
ID
83619
United States",,
4586,1.178.128.0/20,PS,group,Abuse-C Role,"Palestine Telecommunications (PALTEL) Khaled Sayeh Rafeedya St. 1570 Nablus PALESTINIAN TERRITORY, OCCUPIED",RipeAdmin.TechEng@PaltelGroup.ps,"+ 970 9 2376227, + 970 9 2376225"
688694,36.128.0.0/10,CN,group,IRT-CHINAMOBILE2-CN,"China Mobile Communications Corporation
29, Jinrong Ave., Xicheng District, Beijing, 100032",abuse@chinamobile.com,"+86 1052686688, +86 10 52616187"
5509570,99.128.0.0/13,,group,abuse,"2701 W 15th ST
Plano
TX
75075
United States",abuse@att.net,+1-919-319-8167
9263600,205.250.74.0/24,,group,Abuse at TELUS,"10035 102 AVE
Edmonton
AB
T5J 0E5
Canada",abuse@telus.com,+1-877-945-8220
8198055,191.254.0.0/15,BR,individual,CSIRT TELEFONICA BR,,abuse.br@telefonica.com,
7699976,182.177.0.0/16,PK,group,IRT-PTCLBB-PK,"General Manager,
Pakistan Telecommunication Company Limited.
H-9/1, CDDT Building, Training Block
Islamabad, Pakistan","abuse.irt@ptcl.net, csirt@ptcl.net",+92-51-4865412
9053784,202.83.32.0/19,IN,group,IRT-ASIANET-IN,"2 nd Floor , Leela Tower
Technopark,Kazhakuttam
Trivandrum
Kerala","abuse-reports@asianet.co.in, muralin@asianet.co.in","+91 471 2527878, +91 471 2700244, +91 471 3071300, +91 471 3071100"
2818393,71.173.96.0/19,,group,Abuse,"22001 Loudoun County Parkway
Asburn
VA
20147
United States",abuse@verizon.com,+1-800-900-0241

3.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 table for abuse contact details, ensuring accurate data linkage and integrity.

Image

File Format & Encoding

All IP to Abuse Contact 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 abuse contact 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 Abuse Contact MMDB database archive, you'll find the following files (with their types noted):

db-ip-abuse.mmdb
db-ip-abuse.mmdbdb-ip-abuse.mmdb

Provides full abuse contact details for IP addresses: network, country, kind, and contact info.

  • File Size: 763.54 MB
  • Entries: 29.9M
README.md
README.mdREADME.md

Documentation for dataset contents, schema, usage, and support.

  • File Size: 4.55 KB
checksum.txt
checksum.txtchecksum.txt

SHA-256 checksums for verifying file integrity.

  • File Size: 159 Bytes

Response Schema

This section describes the structure of the data returned from the IP to Abuse Contact 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-abuse.mmdb

This file contains abuse contact details 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.

Showing 0 of 7
Select a field to view details

I.Example Records

Example
{
  "abuse": {
    "address": "2 nd Floor , Leela Tower\nTechnopark,Kazhakuttam\nTrivandrum\nKerala",
    "country_code": "IN",
    "emails": "abuse-reports@asianet.co.in, muralin@asianet.co.in",
    "kind": "group",
    "name": {
      "en": "IRT-ASIANET-IN"
    },
    "phone_numbers": "+91 471 2527878, +91 471 2700244, +91 471 3071300, +91 471 3071100",
    "route": "202.83.32.0/19"
  }
}

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 Abuse Contact 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:

  1. Database file (the downloaded archive)
  2. Signature file (the matching signature for that archive)
  3. Public key (public-key.pem)

These files are available via official IPGeolocation.io download endpoints and are also shared in database update notifications.

Note

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 openssl

Verify OpenSSL installation:

openssl version

To 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 OK

if 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.

Tip

Always verify downloaded files with the provided checksum before importing.

On Linux, if sha256sum is not installed, first run:

sudo apt-get install coreutils

Then check the archive files against the checksum file with:

sha256sum -c checksum.txt

Example output:

db-abuse-details.csv.gz: OK
db-ip-abuse.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.

Important
Signature verification confirms both authenticity and integrity. Checksum verification confirms integrity only (it detects corruption/modification, but does not independently prove who produced the file).

Data Format & Constraints

  • All fields defined in the schema are always present in the IP to Abuse Contact 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 Abuse Contact 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:

  1. Database Archive URL : downloads the latest release of your subscribed database (CSV, MMDB or requested formats).
  2. Signature File URL : downloads the matching signature file for the latest release (used for authenticity verification).
  3. Public Key URL : downloads the public verification key (used with the signature file).
  4. 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.

Subscribe Our Newsletter

Get the latest in geolocation tech, straight to your inbox.