Standard database | Specifications | DNS Database Download | WhoisXML API

Standard database

Samples

The database comes in five forms, which include A, AAAA, MX, NS, TXT, CNAME, SOA, and PTR records and can be downloaded in CSV.

Subscription type Description
Daily updates Include DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA, PTR) that have been added during a previous day for a given date in unified and consistent CSV format. These files are located in the daily_datafeed subdirectory and are named in format:
- "daily_datafeed/dns_database.%DATE%.daily.csv.gz"
- "daily_datafeed/dns_aaaa_database.%DATE%.daily.csv.gz"
- "daily_datafeed/dns_mx_database.%DATE%.daily.csv.gz"
- "daily_datafeed/dns_ns_database.%DATE%.daily.csv.gz",
- "daily_datafeed/dns_txt_database.%DATE%.daily.csv.gz",
- "daily_datafeed/dns_cname_database.%DATE%.daily.csv.gz",
- "daily_datafeed/dns_soa_database.%DATE%.daily.csv.gz",
- "daily_datafeed/dns_ptr_database.%DATE%.daily.csv.gz",
e.g. "daily_datafeed/dns_database.2021-12-01.daily.csv.gz".
Weekly updates Include changes in the full database of DNS records compared to the previous period. Includes added, dropped, and modified records since the previous week. These files are named in format:
- "dns_database.%DATE%.weekly.diff.csv.gz"
- "dns_aaaa_database.%DATE%.weekly.diff.csv.gz"
- "dns_mx_database.%DATE%.weekly.diff.csv.gz",
- "dns_ns_database.%DATE%.weekly.diff.csv.gz",
- "dns_txt_database.%DATE%.weekly.diff.csv.gz",
- "dns_cname_database.%DATE%.weekly.diff.csv.gz",
- "dns_soa_database.%DATE%.weekly.diff.csv.gz",
- "dns_ptr_database.%DATE%.weekly.diff.csv.gz",
e.g. "dns_database.2021-12-01.weekly.diff.csv.gz".
Monthly updates Include changes in the full database of DNS records compared to the previous period. Includes added, dropped, and modified records since the previous month. These files are named in format:
- "dns_database.%DATE%.monthly.diff.csv.gz"
- "dns_aaaa_database.%DATE%.monthly.diff.csv.gz"
- "dns_mx_database.%DATE%.monthly.diff.csv.gz",
- "dns_ns_database.%DATE%.monthly.diff.csv.gz",
- "dns_txt_database.%DATE%.monthly.diff.csv.gz",
- "dns_cname_database.%DATE%.monthly.diff.csv.gz",
- "dns_soa_database.%DATE%.monthly.diff.csv.gz",
- "dns_ptr_database.%DATE%.monthly.diff.csv.gz",
e.g. "dns_database.2021-12-01.monthly.diff.csv.gz".
Full database A full database of DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA, PTR) collected for the previous 90 days before a given date in a unified and consistent CSV format. These files are named in format:
- "dns_database.%DATE%.full.csv.gz"
- "dns_aaaa_database.%DATE%.full.csv.gz"
- "dns_mx_database.%DATE%.full.csv.gz"
- "dns_ns_database.%DATE%.full.csv.gz",
- "dns_txt_database.%DATE%.full.csv.gz",
- "dns_cname_database.%DATE%.full.csv.gz",
- "dns_soa_database.%DATE%.full.csv.gz",
- "dns_ptr_database.%DATE%.full.csv.gz",
e.g. "dns_database.2021-12-01.full.csv.gz".
Lite database A partial database of A DNS records for a given date made for academic purposes. It includes about 5% of a full database. These files are named in format:
- "dns_database.%DATE%.academic.csv.gz"
e.g. "dns_database.2021-12-01.academic.csv.gz".


Note that the weekly and monthly data are derived from the concatenation of the respective daily data and the addition of the first field, the date.

Downloading via FTP

When dealing with extensive data sets, factors such as download speed, round-trip times, network stability, and disk I/O can influence the successful completion of your download over the HTTP protocol. Additionally, external elements like antivirus software may introduce complexities that hinder the seamless transfer of your data. To ensure a smoother and more reliable download experience, we highly recommend utilizing the FTP (File Transfer Protocol) option whenever possible. FTP provides a robust solution that minimizes the impact of potential challenges associated with HTTP downloads. If you encounter download errors or face any difficulties, we encourage you to reach out to our dedicated support department. They will be more than happy to assist you in enabling FTP access, thereby optimizing your data transfer process.

Downloading via HTTPS

Downloading via FTPS

Read more about the FTPS connection: https://en.wikipedia.org/wiki/FTPS.

Our FTP server supports explicit FTP over TLS encryption. You may configure your FTP client to use explicit FTP over TLS encryption for secure communications.

Our FTPS server is accessed using the same paths and API keys as a regular FTP server, the instructions for which are described above. To connect via FTPS, select the "Require explicit FTP over TLS" encryption option in your FTP client, if it supports it. FileZilla configuration example:

explicit FTP over TLS encryption

Average file sizes

Measured as of 22 January 2024.

A files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Partial database for academic purposes .academic 294MB 1.0GB 30.6M
Weekly full database export .full 4.93GB 20.6GB 611.7M
Weekly changes in the full database .weekly.diff 112.9MB 429.4MB 12.43M
Monthly changes in the full database .monthly.diff 477.1GB 1.7GB 51.49M
Records added during the previous day .daily 122.3MB 563.5MB 14.5M

MX files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 3.9GB 25.9GB 437.9M
Weekly changes in the full database .weekly.diff 65.6MB 409.4MB 7.1M
Monthly changes in the full database .monthly.diff 260.1GB 1.5GB 27.5M
Records added during the previous day .daily 94.7MB 839.5GB 11.1M

NS files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 7.6GB 51.8GB 1.03B
Weekly changes in the full database .weekly.diff 159.1MB 0.9GB 19.8M
Monthly changes in the full database .monthly.diff 658.5MB 3.8GB 81.3M
Records added during the previous day .daily 190.7MB 1.4GB 26.5M

TXT files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 4.7GB 20.1GB 265.5M
Weekly changes in the full database .weekly.diff 110.8MB 453.6MB 6.3M
Monthly changes in the full database .monthly.diff 488.0MB 1.8GB 26.4M
Records added during the previous day .daily 137.8MB 690.3MB 7.4M

CNAME files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 0.9GB 6.7GB 91.2M
Weekly changes in the full database .weekly.diff 33.8MB 167.6MB 3.0M
Monthly changes in the full database .monthly.diff 127.3MB 622.2MB 11.3M
Records added during the previous day .daily 10.0MB 192.1MB 1.3M

SOA files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 7.4GB 41.9GB 405.9M
Weekly changes in the full database .weekly.diff 366.8MB 2.0GB 20.2M
Monthly changes in the full database .monthly.diff 1.5GB 8.8GB 86.9M
Records added during the previous day .daily 197.5MB 1.1GB 10.6M

AAAA files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 1.0GB 4.0GB 93.0M
Weekly changes in the full database .weekly.diff 22.8MB 92.2MB 2.0M
Monthly changes in the full database .monthly.diff 100.2MB 406.6MB 9.0M
Records added during the previous day .daily 20.6MB 80.4MB 1.9M

PTR files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 482.3KB 1.8MB 33.8K
Weekly changes in the full database .weekly.diff 117.3KB 381.8KB 7.3K
Monthly changes in the full database .monthly.diff 95.9KB 390.9KB 6.9K
Records added during the previous day .daily 27.3KB 91.8KB 1.7K

CSV output structure and fields' descriptions

The database files are comma-separated value-files without text delimiters. The files use DOS/Windows - style line terminators (CR+LF). The first line is a header line with the field names. Each line has four or five fields depending on the subscription type:

A files

  • Structure: <DOMAIN>,<LAST_UPDATE_TIMESTAMP>,<IP1> <IP2> ... <IPn>
  • Example: zs12p1.gotoip1.com.cname.yunjiasu-cdn.net,1530959456,162.159.210.99 162.159.211.99
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record. If there is more than one IP address, the timestamp corresponds to all of them.
IP1, IP2, IPn
List of IPs associated with the domain, separated by space.

AAAA files

  • Structure: <DOMAIN>,<LAST_UPDATE_TIMESTAMP>,<IP1> <IP2> ... <IPn>
  • Example: 212120--jekyllrb.netlify.app,1647929159,2604:a880:400:d0::1738:6301 2604:a880:400:d0::1b6b:7051
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record. If there is more than one IP address, the timestamp corresponds to all of them.
IP1, IP2, IPn
List of IPs associated with the domain, separated by space.

MX files

  • Structure:
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<PRIORITY>,<MX1>
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<PRIORITY>,<MX2>
    - <DOMAIN-B>,<LAST_UPDATE_TIMESTAMP>,<PRIORITY>,<MX1>
    - ...
  • Example:
    - 003vendor.com,1608996228,20,alt1.aspmx.l.google.com
    - 003vendor.com,1608996228,20,alt2.aspmx.l.google.com
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
PRIORITY
Priority identifies which mailserver should be preferred.
MX
The MX record associated with the domain.

NS files

  • Structure:
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<NS1>
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<NS2>
    - <DOMAIN-B>,<LAST_UPDATE_TIMESTAMP>,<NS1>
    - ...
  • Example:
    - 0001.cn,1608996268,dns1.hichina.com
    - 0001.cn,1608996268,dns2.hichina.com
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
NS
The NS record associated with the domain.

TXT files

  • Structure:
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<TXT1>
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<TXT2>
    - <DOMAIN-B>,<LAST_UPDATE_TIMESTAMP>,<TXT1>
    - ...
  • Example:
    - 0--00.holiest.science,1619741985,|v=spf1 ip4:67.225.166.63 +a +mx +ip4:67.225.166.41 ~all!
    - 0--00.holiest.science,1619741985,|v=spf1 ip4:67.225.166.63 +a +mx +ip4:67.225.166.41 ~alla
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
TXT
The TXT record associated with the domain.

CNAME files

  • Structure:
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<CNAME1>
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<CNAME2>
    - <DOMAIN-B>,<LAST_UPDATE_TIMESTAMP>,<CNAME1>
    - ...
  • Example:
    - 0-131-3-149.rackcentre.redstation.net.uk,1619742251,redstation.com
    - 0-132-3-149.rackcentre.redstation.net.uk,1619741776,redstation.com
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
CNAME
The CNAME record associated with the domain.

SOA files

  • Structure:
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<SOA1>
    - <DOMAIN-A>,<LAST_UPDATE_TIMESTAMP>,<SOA2>
    - <DOMAIN-B>,<LAST_UPDATE_TIMESTAMP>,<SOA1>
    - ...
  • Example:
    - 0-rings.com,1619741730,NS25.DOMAINCONTROL.com dns.jomax.net 2018091300 28800 7200 604800 3600
    - 0-rings.com,1619741730,NS25.domaincontrol.com dns.jomax.net 2018091300 28800 7200 604800 3600
DOMAIN
Domain or subdomain name.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
SOA
The SOA record associated with the domain.

PTR files

  • Structure:
    - <IP-A>,<LAST_UPDATE_TIMESTAMP>,<PTR1>
    - <IP-A>,<LAST_UPDATE_TIMESTAMP>,<PTR2>
    - <IP-B>,<LAST_UPDATE_TIMESTAMP>,<PTR1>
    - ...
  • Example:
    - 1.0.135.155,1661516953,node-1i3.pool-1-0.dynamic.totinternet.net
    - 1.0.0.1,1661724824,one.one.one.one
IP
IP address.
LAST_UPDATE
UNIX timestamp of the last visit/update on current record.
PTR
The PTR record associated with the IP.