ASN WHOIS Database

Overview

Our ASN WHOIS (parsed) Database provides clean, normalized ownership and contact intelligence for Autonomous System Numbers worldwide. Instantly see who operates an ASN, where it’s registered, and how to reach the right people, so you can validate routing policies, accelerate incident response, enrich threat intelligence, and keep network inventories accurate across security and NetOps workflows.

Updated daily and standardized across all RIRs (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC). Delivered as CSV and JSON, with MMDB, Parquet, or any custom export on request at no extra cost, backed by stable schemas and changelogs. 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

JSON

File Size: 48.32 MB

Entries: 132.1K

Fields: 55

Last Updated: Yesterday

Documentation

CSV Database Documentation

1. Overview

The CSV version is a set of Gzip-compressed CSV files containing ASN and ASN WHOIS information. These files are designed for bulk imports and integration into relational databases.

2. Archive Content

After downloading and extracting the ASN WHOIS CSV database archive, you'll find the following files (with their types noted):

Schema

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

1. db-asn-whois.csv.gz

This file contains detailed WHOIS information for Autonomous System Numbers (ASNs). It maps each AS Block and autNum to the name, country, domain, and RIR, as well as different contact handle IDs and the full rawWhois record.

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.

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.

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

JSON Database Documentation

1. Overview

JSON version of the database consists of two files: one JSON 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 ASN WHOIS MMDB database archive, you'll find the following files (with their types noted):

db-asn-whois.json.gz

Full WHOIS details for ASN: name, country, domain, RIR, contact IDs, and raw WHOIS record.

File Size: 48.31 MB

Entries: 132.1K

README.md

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

File Size: 9.19 KB

checksum.txt

SHA-256 checksums for verifying file integrity.

File Size: 163 Bytes

Response Schema

This section describes the structure of the data returned from the ASN 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-asn-whois.json

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 JSON 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 10 of 56

Select a field to view details

I. Example Records

Example

{
  "asBlock": "AS87 - AS87",
  "autNum": "87",
  "country": "US",
  "domain": "iu.edu",
  "rir": "ARIN",
  "org": {
    "handle": "INDIAN-Z",
    "name": "Indiana University",
    "type": "",
    "address": "2709 E 10th Street, Indiana University Information Technology, networks division, Bloomington, IN, 47408, US",
    "country": "US",
    "email": "",
    "phone": "",
    "fax": "",
    "dateUpdated": "2026-07-15",
    "source": "https://rdap.arin.net/registry/entity/INDIAN-Z"
  },
  "admin": null,
  "tech": [
    {
      "handle": "JEA98-ARIN",
      "name": "Ambern, Jeff Edward",
      "country": "",
      "email": "jambern@iu.edu",
      "phone": "+1-765-792-0002",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/JEA98-ARIN"
    },
    {
      "handle": "NEM12-ARIN",
      "name": "Network Enginering Manager",
      "country": "",
      "email": "ctgarret@iu.edu",
      "phone": "+1-812-855-4776",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/NEM12-ARIN"
    },
    {
      "handle": "DBE43-ARIN",
      "name": "Beals, Damon",
      "country": "",
      "email": "dbeals@iu.edu",
      "phone": "+1-317-274-7946",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/DBE43-ARIN"
    },
    {
      "handle": "IUD-ORG-ARIN",
      "name": "Indiana University Computing Services",
      "country": "",
      "email": "dns-admin@iu.edu",
      "phone": "+1-317-274-7788",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/IUD-ORG-ARIN"
    },
    {
      "handle": "SPENC364-ARIN",
      "name": "Spencer, Mark",
      "country": "",
      "email": "maespenc@iu.edu",
      "phone": "+1-812-855-3098",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/SPENC364-ARIN"
    },
    {
      "handle": "IGRP-ARIN",
      "name": "I-Light and GigaPOP Routing POC",
      "country": "",
      "email": "routing@indiana.gigapop.net",
      "phone": "+1-317-278-6635",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/IGRP-ARIN"
    }
  ],
  "abuse": [
    {
      "handle": "INDIA-ARIN",
      "name": "IndianaUniversity-abuse",
      "country": "",
      "email": "abuse@iu.edu",
      "phone": "+1-812-855-9255",
      "fax": "",
      "address": "",
      "dateUpdated": "",
      "source": "https://rdap.arin.net/registry/entity/INDIA-ARIN"
    }
  ],
  "irt": null,
  "bgp": null,
  "rawWhois": "\n#\n# ARIN WHOIS data and services are subject to the Terms of Use\n# available at: https://www.arin.net/resources/registry/whois/tou/\n#\n# If you see inaccuracies in the results, please report at\n# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/\n#\n# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.\n#\n\n\nASNumber:       87\nASName:         INDIANA-AS\nASHandle:       AS87\nRegDate:        1986-10-10\nUpdated:        2018-08-03\nRef:            https://rdap.arin.net/registry/autnum/87\n\n\nOrgName:        Indiana University\nOrgId:          INDIAN-Z\nAddress:        2709 E 10th Street\nAddress:        Indiana University Information Technology\nAddress:        networks division\nCity:           Bloomington\nStateProv:      IN\nPostalCode:     47408\nCountry:        US\nRegDate:        2009-11-03\nUpdated:        2026-07-15\nRef:            https://rdap.arin.net/registry/entity/INDIAN-Z\n\n\nOrgTechHandle: SPENC364-ARIN\nOrgTechName:   Spencer, Mark \nOrgTechPhone:  +1-812-855-3098 \nOrgTechEmail:  maespenc@iu.edu\nOrgTechRef:    https://rdap.arin.net/registry/entity/SPENC364-ARIN\n\nOrgTechHandle: JEA98-ARIN\nOrgTechName:   Ambern, Jeff Edward\nOrgTechPhone:  +1-765-792-0002 \nOrgTechEmail:  jambern@iu.edu\nOrgTechRef:    https://rdap.arin.net/registry/entity/JEA98-ARIN\n\nOrgRoutingHandle: IGRP-ARIN\nOrgRoutingName:   I-Light and GigaPOP Routing POC\nOrgRoutingPhone:  +1-317-278-6635 \nOrgRoutingEmail:  routing@indiana.gigapop.net\nOrgRoutingRef:    https://rdap.arin.net/registry/entity/IGRP-ARIN\n\nOrgTechHandle: NEM12-ARIN\nOrgTechName:   Network Enginering Manager\nOrgTechPhone:  +1-812-855-4776 \nOrgTechEmail:  ctgarret@iu.edu\nOrgTechRef:    https://rdap.arin.net/registry/entity/NEM12-ARIN\n\nOrgAbuseHandle: INDIA-ARIN\nOrgAbuseName:   IndianaUniversity-abuse\nOrgAbusePhone:  +1-812-855-9255 \nOrgAbuseEmail:  abuse@iu.edu\nOrgAbuseRef:    https://rdap.arin.net/registry/entity/INDIA-ARIN\n\nOrgTechHandle: DBE43-ARIN\nOrgTechName:   Beals, Damon \nOrgTechPhone:  +1-317-274-7946 \nOrgTechEmail:  dbeals@iu.edu\nOrgTechRef:    https://rdap.arin.net/registry/entity/DBE43-ARIN\n\nRTechHandle: IUD-ORG-ARIN\nRTechName:   Indiana University Computing Services\nRTechPhone:  +1-317-274-7788 \nRTechEmail:  dns-admin@iu.edu\nRTechRef:    https://rdap.arin.net/registry/entity/IUD-ORG-ARIN\n\n\n#\n# ARIN WHOIS data and services are subject to the Terms of Use\n# available at: https://www.arin.net/resources/registry/whois/tou/\n#\n# If you see inaccuracies in the results, please report at\n# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/\n#\n# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.\n#\n",
  "dateCreated": "1986-10-10",
  "dateUpdated": "2018-08-03",
  "name": "INDIANA-AS"
}

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 ASN WHOIS 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.

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:

*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 ASN WHOIS JSON 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 ASN WHOIS 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 updated continuously and shipped on a daily or weekly cycle depending on your plan, 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.

ASN WHOIS Database

Overview

Available Database Formats

CSV Database Documentation

1. Overview

2. Archive Content

Schema

1. db-asn-whois.csv.gz

2. db-handles-details.csv.gz

3. db-org-details.csv.gz

4. File Relationship Diagram

File Format & Encoding

JSON Database Documentation

1. Overview

2. Archive Content

Response Schema

1. db-asn-whois.json

2. Field Reference

I. Example Records

Database Integrity & Authenticity Verification

1. Using the Signature File (Recommended)

2. Using the Checksum File (Legacy)

Data Format & Constraints

Database Updates & Delivery

Subscribe to Our Newsletter