Provide current and historical ownership information on domains / IPs. Identify all connections between domains, registrants, registrars, and DNS servers.
Look into all current and historical DNS / IP connections between domains and A, MX, NS, and other records. Monitor suspicious changes to DNS records.
Get detailed context on an IP address, including its user’s geolocation, time zone, connected domains, connection type, IP range, ASN, and other network ownership details.
Access our web-based solution to dig into and monitor all domain events of interest.
Get access to a web-based enterprise-grade solution to search and monitor domain registrations and ownership details for branded terms, fuzzy matches, registrants of interest, and more.
Independent, evidence-based DNS and abuse intelligence for applicants, advisors, governments, and counsel participating in the ICANN 2026 New gTLD Program.
Predictive threat intelligence is your best first line of defense. Subscribe to the feeds to strengthen your cybersecurity posture. Contact us today for more information.
Unlock integrated intelligence on Internet properties and their ownership, infrastructure, and other attributes.
Our complete set of domain, IP, and DNS intelligence available via API calls as an annual subscription with predictable pricing.
Offers complete access to WHOIS, IP, DNS, and subdomain data for product enrichment, threat hunting and more.
Uncover entire attack surfaces with this API to embed asset discovery, vulnerability scanning, and technology metadata into your platform. Now in early access.
Talk to our APIs using LLMs. Connect your preferred LLM to WhoisXML API and simply chat about WHOIS, DNS, threat intelligence, and more.
I’m your Domain Intelligence Assistant. I make it easy to explore WHOIS, DNS, and threat data from WhoisXML API — I’m cloud-based, fast, and always ready to help.
A custom GPT for WHOIS, DNS, IP, and threat intelligence research. Connects ChatGPT directly to WhoisXML API to enable fast, conversational investigations and domain insights.
One Universal API Credit Pool
Simplify API credit purchasing and usage with one balance that works across our product portfolio.
The Website Categorization Database covers more than 180 million domains, more than 100 million of them with a category from the IAB Content Taxonomy v3.1: all 704 categories, across four tiers. It comes as files: a weekly full snapshot of every domain, and a daily file of the rows that changed.
Every domain in the database, one row per domain. A new snapshot starts every Sunday at 03:00 UTC and is normally complete by Monday afternoon (UTC).
The domains we newly categorized, re-categorized or re-checked since the previous daily file, including changes in a domain's status, such as a site that became parked or stopped responding. A daily file can also repeat rows that did not change, and a few corrections arrive only with the next weekly snapshot. A daily file is normally published every day except Sunday, around 10:30 UTC, and normally covers the 24 hours up to 10:00 UTC. Monday's covers Saturday and Sunday, and it arrives later when the weekly snapshot runs long. After some updates on our side, daily files pause until the next weekly snapshot. Each daily file's manifest gives the window it covers.
Apply each daily file as an update by domain: add the domains you do not have, and replace the rows you do. Load each weekly snapshot as a full replacement of what you hold, not as an update: a daily file never removes a domain, and removals reach you only that way. After loading a snapshot, apply the first daily file that was made after the snapshot was complete and whose window began before the snapshot started: normally Monday's. If that file has not arrived yet, wait for it. Then apply every later daily file in order, going by the windows, not by the order the files arrive. The Data dictionary's "Resuming after a full set" gives the exact rule.
Each snapshot and each daily file comes as a compressed CSV file (Zstandard, .csv.zstd) and as a Parquet file (.parquet). Both hold the same rows in the same column order, so you need only one of them. A manifest beside them gives each file's size and SHA-256 checksum and the row count: check every download against it.
A weekly snapshot is about 15 GB in the two formats together, about half of that in each. A daily file is usually tens of megabytes per format; Monday's, which covers two days, is larger.
Each row has 51 columns, among them the domain, its IAB v3.1 category at up to four tiers with the category id, confidence scores, the domain's status (active, parked, blocked and others), and the dates we categorized and last observed it. Some columns are reserved for fields we do not populate yet. Column order is fixed, and new columns are only ever added at the end.
Every column is defined in the Data dictionary, and every change to the files is listed in the Feed changelog.
The files are in the Website_Categorization_Database folder:
weekly/<date>/webcat.<date>.weekly.csv.zstd
weekly/<date>/webcat.<date>.weekly.parquet
weekly/<date>/manifest.<date>.weekly.json
daily/<date>/webcat.<date>.daily.csv.zstd
daily/<date>/webcat.<date>.daily.parquet
daily/<date>/manifest.<date>.daily.json
A weekly folder is named for the Sunday its snapshot starts. A daily folder is named for the date its window ends, normally the day it is published: daily/2026-11-17/ holds the changes up to about 10:00 UTC on 17 November 2026.
The CSV files are compressed with Zstandard: decompress them with zstd -d (or unzstd), or stream them with zstd -dc. The Parquet files need no separate decompression step; read them with any Parquet reader.
Note: if the IP allowlist is enabled in your account settings, HTTPS downloads are accepted only from the listed IP addresses; other requests are rejected with 403 "Your IP address is not on the allowlist".
Note: if the IP allowlist is enabled in your account settings, it applies to data feed downloads as well as to API calls: FTP, FTPS and HTTPS requests from IP addresses that are not on the list are rejected with 403 "Your IP address is not on the allowlist". Add the IP addresses of every machine that downloads the data feeds before enabling it.
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:
We are here to listen. For a quick response, please select your request type. By submitting a request, you agree to our Terms of Service and Privacy Policy.