Press Releases

Product and Feature Updates for 2024

WhoisXML API continues to improve its service offerings with the release of the following products and feature upgrades in 2024 so far.

• Server-to-Server OAuth is now available for all API products: API users can now authorize API requests using Server-to-Server OAuth. This more secure authentication method enables your applications and WhoisXML API servers to communicate without involving user interactions, making API integration more straightforward and scalable. Using Server-to-Server OAuth is a simple two-step process detailed here.

Product and Feature Updates for Q3–Q4 2023

In line with WhoisXML API’s commitment to improving its service offerings, we released the following products and feature upgrades in Q3 and Q4 2023:

• “First seen” UNIX timestamp has been added to Threat Intelligence Data Feeds’ files: Subscribers of our Threat Intelligence Data Feeds can now reference the date and time when an indicator of compromise (IoC) was first detected. The new column has been added to these files:

Product and Feature Updates for Q1–Q2 2023

In line with WhoisXML API’s commitment to improving its service offerings, we released the following products and feature upgrades in Q1 and Q2 2023:

• Early DGA Detection Feed: To launch our threat prediction intelligence product line, we introduced Early DGA Detection Feed, a daily list of new domains likely created using domain generation algorithms (DGAs), along with their WHOIS details for deeper context. Threat actors typically use algorithmically created domains in zero-day attacks, phishing campaigns, spamming, and other malicious activities. Being able to filter and block them as they get registered can help organizations avoid becoming cyber attack victims.

Product and Feature Updates for Q3-Q4 2022

In line with WhoisXML API’s commitment to improving its services, we made the following changes and product feature upgrades in Q3 2022:

• DNS database now includes PTR records. A new important update was made to our DNS Database by adding pointer (PTR) records. PTR records are reverse DNS records that map domain names to IP addresses. They are, by definition, the opposite of A or AAAA records that provide the IP addresses associated domains point to. With this additional information, new use cases are enabled for users. For instance, they can now utilize our DNS Database to intensify mail server validation, among other processes.

Product and Feature Updates for Q2 2022

WhoisXML API made some significant changes and product feature upgrades in Q2 2022 . We are proud to announce the following updates:

• The coverage of our DNS database has increased. Our DNS Database v2.0 data coverage increased by 521% as of June 2022. Daily updates were also developed, and AAAA records were added on top of the existing DNS records— i.e., A, MX NS, TXT, CNAME, and SOA records. These updates allow for more extensive and accurate threat hunting, cybercrime investigation, cyber forensics analysis, and other security and business processes.

Product and Feature Updates for Q1 2022

In line with WhoisXML API’s commitment to improve its services, we released the following products and specific improvements so far in Q1 2022:

• Real-Time Domain Registration Streaming: We now have a new domain data delivery model that enables organizations to get a steady stream of newly registered, updated, discovered, and dropped domain names with their corresponding WHOIS information with data delivery cycle intervals between 1 and 59 minutes. With Real-Time Domain Registration Streaming, clients no longer need to wait for the next batch feed file or manually perform API calls to get the data they need.

Response to LOG4J vulnerability

WHOIS API, Inc. is a highly distributed, globally deployed platform, and ensuring the security of all our users is a top priority for us. Our engineering and security teams have been urgently assessing any potential impact on our system following the recent Log4J/Log4Shell vulnerability announcement (CVE-2021-44228).

An initial analysis has shown that appropriate mitigations are in place to protect our customer data and system integrity and that our system's security has not been breached. Due to the distributed nature and complexity of our platform, we are continuing our analysis to formally confirm that all possible attack vectors relating to this vulnerability have been identified and that required mitigations have been implemented.