Premium database | Specifications | DNS Database Download | WhoisXML API

Premium database

Samples

The premium 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/premium_dns_database.%DATE%.daily.csv.gz"
- "daily_datafeed/premium_dns_aaaa_database.%DATE%.daily.csv.gz"
- "daily_datafeed/premium_dns_mx_database.%DATE%.daily.csv.gz"
- "daily_datafeed/premium_dns_ns_database.%DATE%.daily.csv.gz",
- "daily_datafeed/premium_dns_txt_database.%DATE%.daily.csv.gz",
- "daily_datafeed/premium_dns_cname_database.%DATE%.daily.csv.gz",
- "daily_datafeed/premium_dns_soa_database.%DATE%.daily.csv.gz",
- "daily_datafeed/premium_dns_ptr_database.%DATE%.daily.csv.gz",
e.g. "daily_datafeed/premium_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:
- "premium_dns_database.%DATE%.weekly.diff.csv.gz"
- "premium_dns_aaaa_database.%DATE%.weekly.diff.csv.gz"
- "premium_dns_mx_database.%DATE%.weekly.diff.csv.gz",
- "premium_dns_ns_database.%DATE%.weekly.diff.csv.gz",
- "premium_dns_txt_database.%DATE%.weekly.diff.csv.gz",
- "premium_dns_cname_database.%DATE%.weekly.diff.csv.gz",
- "premium_dns_soa_database.%DATE%.weekly.diff.csv.gz",
- "premium_dns_ptr_database.%DATE%.weekly.diff.csv.gz",
e.g. "premium_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:
- "premium_dns_database.%DATE%.monthly.diff.csv.gz"
- "premium_dns_aaaa_database.%DATE%.monthly.diff.csv.gz"
- "premium_dns_mx_database.%DATE%.monthly.diff.csv.gz",
- "premium_dns_ns_database.%DATE%.monthly.diff.csv.gz",
- "premium_dns_txt_database.%DATE%.monthly.diff.csv.gz",
- "premium_dns_cname_database.%DATE%.monthly.diff.csv.gz",
- "premium_dns_soa_database.%DATE%.monthly.diff.csv.gz",
- "premium_dns_ptr_database.%DATE%.monthly.diff.csv.gz",
e.g. "premium_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:
- "premium_dns_database.%DATE%.full.csv.gz"
- "premium_dns_aaaa_database.%DATE%.full.csv.gz"
- "premium_dns_mx_database.%DATE%.full.csv.gz"
- "premium_dns_ns_database.%DATE%.full.csv.gz",
- "premium_dns_txt_database.%DATE%.full.csv.gz",
- "premium_dns_cname_database.%DATE%.full.csv.gz",
- "premium_dns_soa_database.%DATE%.full.csv.gz",
- "premium_dns_ptr_database.%DATE%.full.csv.gz",
e.g. "premium_dns_database.2021-12-01.full.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
Weekly full database export .full 244.3GB 1.0TB 31.1B
Weekly changes in the full database .weekly.diff 17.2GB 79.3GB 2.1B
Monthly changes in the full database .monthly.diff 68.9GB 295.6GB 8.4B
Records added during the previous day .daily 2.6GB 13.8GB 372.5M

MX files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 5.4GB 34.9GB 555.1M
Weekly changes in the full database .weekly.diff 144.5MB 0.9GB 13.7M
Monthly changes in the full database .monthly.diff 688.6MB 4.2GB 66.8M
Records added during the previous day .daily 127.9MB 2.4GB 15.9M

NS files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 10.0GB 67.4GB 1.2B
Weekly changes in the full database .weekly.diff 282.4MB 1.7GB 32.7M
Monthly changes in the full database .monthly.diff 1.2MB 7.8GB 146.4M
Records added during the previous day .daily 238.5MB 3.4GB 36.2M

TXT files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 6.2GB 28.4GB 358.4M
Weekly changes in the full database .weekly.diff 198.0MB 0.9GB 12.2M
Monthly changes in the full database .monthly.diff 945.7MB 4.6GB 56.2M
Records added during the previous day .daily 168.7MB 1.8GB 12.4M

CNAME files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 2.3GB 14.7GB 203.1M
Weekly changes in the full database .weekly.diff 112.3MB 665.8MB 9.7M
Monthly changes in the full database .monthly.diff 580.4MB 3.4GB 50.3M
Records added during the previous day .daily 33.6MB 1.1GB 5.9M

SOA files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 9.4GB 54.5GB 503.5M
Weekly changes in the full database .weekly.diff 478.3MB 2.8GB 25.98M
Monthly changes in the full database .monthly.diff 2.0GB 11.9GB 111.8M
Records added during the previous day .daily 231.0MB 2.3GB 15.2M

AAAA files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 13.2GB 62.8GB 1.42B
Weekly changes in the full database .weekly.diff 1.6GB 8.5GB 181.7M
Monthly changes in the full database .monthly.diff 5.0GB 24.9GB 547.7M
Records added during the previous day .daily 283.7MB 1.41GB 30.4M

PTR files

File content Filename suffix Avg. gzipped file size Avg. unpacked file size Avg. number of records
Weekly full database export .full 1.8MB 10.1MB 172.7K
Weekly changes in the full database .weekly.diff 344.6KB 1.6MB 27.4K
Monthly changes in the full database .monthly.diff 689.3KB 3.9MB 66.3K
Records added during the previous day .daily 73.1KB 352.5KB 5.9K

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.