Query live, structured WHOIS data for any domain and get owner details, registrar, registration dates, nameservers - returned as clean JSON or XML in milliseconds. No caching. No stale records. Directly from authoritative WHOIS servers and RDAP on every request.
Our Products
A WHOIS API gives developers programmatic access to domain registration records. Instead of manually querying registries, wrestling with rate limits, and parsing inconsistent plaintext output, you send a domain name and receive structured information about domain names, including registration date, expiry date, registrar information, owner details, and host name server information, available in both JSON and XML formats. Live WHOIS Lookup fetches data in real time from WHOIS servers and RDAP to ensure the freshest results on every request, with no database dependency.
Features
We query four sources per lookup: the WHOIS protocol, RDAP, our own scrapers, and proprietary feeds. When one source is rate-limited or returns a stub record, the next one fills the gap. That is why coverage holds on registrar and TLD combinations where single-source APIs return blanks.
We collect data through the WHOIS protocol, the oldest and still one of the most effective methods for retrieving domain ownership details. Its priority varies depending on the registrar and TLD combination, so it is not always our primary source of our WHOIS API.
Our WHOIS API also retrieves data through RDAP, the modern protocol designed to replace the traditional WHOIS protocol. Since WHOIS and RDAP generally provide the same ownership details, we switch between them based on TLD support, registrar configuration, and availability.
WhoisFreaks has developed in-house scrapers to collect WHOIS records across a wide range of TLDs. These scrapers can solve CAPTCHAs in real time, enabling consistent and reliable data collection. They play a key role in expanding TLD coverage and strengthening our fallback mechanisms.
Our WHOIS data is also enriched with proprietary data feeds. Although these sources are limited in number, they add unique coverage, improve WHOIS data quality, and enhance threat correlation with domain ownership data.
Our Products
Access the full historical ownership timeline for any domain, back to 1986. Each record is deduplicated and only where the WHOIS data actually changed are stored. Ideal for tracking ownership transfers, uncovering past registrants, and building domain reputation profiles.
Features
Four things every WHOIS API call returns, and what each one is for.
Fetch real-time, accurate domain data using live WHOIS lookup by domain, IP, or ASN. We fetch details directly from live servers.
Who owns a domain is no longer a limitation. Use our Live or Bulk WHOIS API to retrieve the ownership and registrar details.
WHOIS API returns structured data in both JSON and XML Formats for easy integration in threat intelligence platforms.
Compressed, uniformly parsed records cut storage costs and keep API response payloads small.
Product
Our WHOIS database covers 1,529+ TLDs and 4.4B+ unique historical WHOIS records.
Use Cases
Six jobs teams run on WHOIS data, and the query that does each one.
A reverse WHOIS search on a lead's email or company name returns the full domain portfolio for your CRM record.
Reverse WHOIS your own registrant email to surface forgotten domains before they lapse.
Reverse WHOIS one malicious domain's registrant email to map the rest of that actor's infrastructure in one query.
Reverse WHOIS your trademark as a keyword and catch cybersquatted domains before a phishing campaign starts.
Reverse WHOIS a competitor's organization name to reveal domains they registered before an unannounced launch.
Check a counterparty's claims with a reverse WHOIS search on their registrant email, using our pre-GDPR era records.
Pull live and historical WHOIS into your detection pipeline, and pivot from one registrant to every domain they hold.
Integrations
The WhoisFreaks WHOIS API ships with official Python and Go SDKs so you can query live registrant, registrar, nameserver, and expiry data across 1,529+ TLDs with a single install.
Zapier, Make, and n8n let no-code teams trigger lookups on schedule and push ownership data to CRMs, spreadsheets, or Slack automatically.
Security and compliance teams integrate it into Splunk, Microsoft Sentinel, and SOAR playbooks to enrich domain alerts, detect registrant changes, and fire automated investigation workflows the moment a suspicious registration is flagged.
Yes, we have rate limiting on requests being made on all of our paid plans. The requests limit is shown in the following table.
The Table is divided into three types of plans:
| Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
|---|---|---|---|
| 5000 | 20 | 8 | 3 |
| 15000 | 35 | 12 | 5 |
| 50000 | 80 | 20 | 10 |
| 150000 | 120 | 25 | 15 |
| 450000 | 150 | 35 | 20 |
| 1000000 | 200 | 50 | 25 |
| 3000000 | 300 | 70 | 35 |
| Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
|---|---|---|---|
| 5000 | 20 | 8 | 3 |
| 15000 | 35 | 12 | 5 |
| 50000 | 80 | 20 | 10 |
| 150000 | 120 | 25 | 15 |
| 450000 | 150 | 35 | 20 |
| 1000000 | 200 | 50 | 25 |
| 3000000 | 300 | 70 | 35 |
In case, the request per minute exceeds, it'll throw an error with HTTP error code of 429.