TrustRadius: an HG Insights company

WhoisXML API Enterprise API and Data Feed Packages Reviews & Insights

Score9.1 out of 10

2 Reviews and Ratings

Reviews

2 Reviews

Good packages to enhance our data

Rating: 9 out of 10

Use Cases and Deployment Scope

Our IP data is of greater value when enriched with other reliable sources so the enterprise packages on offer turned out to be valuable. The API package gives access to 10+ domain research and monitoring services each with a specific purpose. In comparison, the data feed package allows users to download any of the databases the solutions provider compiles. In short, these products are good to establish context around our IP addresses and therefore cross-check the validity of entries in our own repository.

Pros

  • The products allow us to validate the information from our own data-gathering efforts.
  • Packages are customizable. Available credits can be used on any of the APIs. The databases come in a series of tiers for domain WHOIS data or IP data only or all-inclusive.
  • The APIs and data feeds both enrich our data and help us protect our own network.
  • Because the APIs give results in JSON and XML, we were able to make them work with our existing systems without hassle. The same is true for the data feeds as they are available in both JSON and CSV formats, which are suitable for pretty much any general or specialized software.

Cons

  • Like most WHOIS sources, a lot of the new records have been redacted for privacy. That sometimes poses problems but the access to historical records helps somewhat.

Likelihood to Recommend

No service is perfect so I am giving a score of 9 for this question. I'd recommend the packages to colleagues who need blanket access to different sources of WHOIS and IP data. As indicated in the name, the packages are more suited for enterprise users with a large number of queries needed.

Enterprise API and Data Feed Packages help improve our cybersecurity posture

Rating: 10 out of 10

Use Cases and Deployment Scope

WhoisXML API's enterprise data feeds and APIs add substance to our monitoring activities and cybersecurity investigations. From the data packages, we selected a feed tier that allows us to scope a significant share of the domain registration space and learn more about past owners when Whois records were still unredacted. The IP data feed tier we worked with, on the other hand, gave us a better understanding of the location and netblock owner behind IP addresses that are either part of or external to our network. In turn, we have been better able to steer clear of domains and IP addresses that may represent a risk to business continuity.

Also, the enterprise APIs let us reinforce various in-house applications and processes. For example, we were able to screen all registered email addresses with Email Verification to verify their existence and validity. Domain Reputation, in parallel, proved useful to categorize domains based on their perceived safety score.

Pros

  • The APIs connect to massive WHOIS, IP geolocation, netblocks, and DNS databases, allowing us to scan an enormous chunk of the Internet for potentially harmful IP addresses and domains.
  • Email Verification API, in particular, is useful for us. It helps us avoid dealing with potential threat actors using fake or disposable email addresses.
  • The databases are results of at least a decade of crawling the Web for all relevant data. Careful parsing and structuring also make them easier to feed as threat intelligence and marketing data sources for our existing solutions.
  • Domain Reputation API is also useful as it immediately lets us know if a domain or IP can be trusted or not just based on its reputation score. Deep technical know-how is not required.

Cons

  • It took us a bit of time to understand which APIs and feeds were the most relevant to us at first. Fortunately, documentation is available and someone from WhoisXML API helped us understand each service better.

Likelihood to Recommend

In general, the enterprise APIs are relevant for organizations that need access to various and compatible sources of domain and IP intelligence for a large number of queries. That is opposed to using each product in the packages separately, which is also possible but less advantageous when scaling up use.

Similarly, the enterprise feed packages are useful for users who want access to various types of domain and IP data but prefer to avoid API calls. Users who only need access to one type of said data, however, may prefer not to use the package.