Our database now contains whois records of 744 Million (744,083,434) domain names.
Login / Password / Signup
Low Price Guarantee

Whois API / Whois History / Reverse Whois

Our WHOIS API returns consistent and well-structured WHOIS data in XML & JSON format. Returned data contain parsed WHOIS fields that can be easily understood by your application. Along with WHOIS API, we also offer WHOIS History API and Reverse WHOIS API.

Powered by Amazon Web Services With support for 1596 TLDs, our cloud-based API lets you quickly access any domain's WHOIS data through Bulk Whois Lookup, Newly Registered Domains, Dropped Deleted Domains, Expiring Domains and Whois Database Download.
Our Services Price Order
5000 WHOIS Lookup API Queries $10 Details
5000 WHOIS History API Queries $25 Details
5000 Reverse WHOIS API Queries $50 Details
Package #1 (5,000 Credits Each API) $75 Details
Package #2 (10,000 Credits Each API) $135 Details

Reverse Whois

Reverse Whois Demo

Search our entire WHOIS database through the Reverse Whois API.

https://api.whoxy.com/?key=xxxxx&reverse=whois&identifier=value

Reverse Whois API lets you perform a comprehensive search on our database, to find domains owned by a company or person.
You just need to enter search terms such as the name, email or company, and you can find all the domains they ever owned.

Sample Output: JSON Schema • XML Schema • JSON Live Results • XML Live Results


Search Identifiers

You must send any one of following search identifiers to search the whois database.

Search by Domain Owner's Name:

https://api.whoxy.com/?key=xxxxx&reverse=whois&name=John+Smith

Search by Email Address:

https://api.whoxy.com/?key=xxxxx&reverse=whois&email=[email protected]

Search by Company / Organization Name:

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation

Search by Keyword present at start of Domain Name:

https://api.whoxy.com/?key=xxxxx&reverse=whois&keyword=yahoo

Please note that search identifiers are case-sensitive. Owner Name identifier is "name". If you send "Name", it will be ignored.


Search Results Pagination

100 results / call

Each API call returns up to 100 results in the default response format.
To retrieve the next batch, use the search_after parameter with the cursor returned by the previous response.

MIGRATION NOTICE

Numbered pagination is retiring. Numbered pagination using &page= is deprecated and will be removed soon. Please update your integration to use search_after for reliable sequential retrieval, especially for large searches. Numbered pagination depends on tracking earlier result positions; cursor pagination continues from the last returned position, avoiding increasingly expensive deep-page lookups.

HOW TO RETRIEVE EVERY BATCH
1

Start your search

Send your first request without page, search_after or mode:

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation

Read the records in search_result. When a continuation cursor is available, the response includes a top-level search_after field. The following JSON fragment illustrates this field; the cursor shown is a placeholder:

{ "search_after": "CURSOR_FROM_FIRST_RESPONSE" }
2

Request the next batch

Send the cursor returned by the preceding response:

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation&search_after=CURSOR_FROM_FIRST_RESPONSE

Replace the placeholder with the actual cursor from the preceding response. Treat the cursor as an opaque string: do not decode, edit or construct it. URL-encode its value once when building the request query string (for example, use PHP http_build_query() or JavaScript URLSearchParams). Keep the same search identifier, search value and other search settings for every batch, and omit page and mode.

3

Continue until the final batch

Always use the latest top-level search_after value to request the following batch. When present, search_identifier.after only echoes the cursor used for the current request; it is not the cursor for the next batch. Fetch batches sequentially; a cursor does not provide a way to jump directly to an arbitrary page number.

Process the final batch, then stop when the response has no non-empty search_after value, or when search_result is empty. Do not request another batch without a cursor, as that would restart the search. If the API reports an invalid or expired cursor, restart by omitting search_after. Check the API status before processing any response; an API error is not an end-of-results signal.

EXAMPLE

Retrieve 250 results in three requests

Suppose this search matches 250 records. Here is how you would retrieve them in batches of 100, 100 and 50. The example assumes the matching records do not change while you browse. CURSOR_A and CURSOR_B are illustrative placeholders, not working cursors; always substitute the actual, URL-encoded cursor returned by your own API response.

First batch — start without a cursor

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation

The response contains records 1–100 in search_result, plus a top-level cursor. Relevant JSON fragment:

{ "search_after": "CURSOR_A" }

Second batch — send CURSOR_A

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation&search_after=CURSOR_A

The response contains records 101–200 and a new top-level cursor, CURSOR_B. It also echoes the cursor you just used under search_identifier.after. Relevant JSON fragment:

{ "search_identifier": { "after": "CURSOR_A" }, "search_after": "CURSOR_B" }

Third batch — send CURSOR_B

https://api.whoxy.com/?key=xxxxx&reverse=whois&company=Acme+Corporation&search_after=CURSOR_B

The response contains the remaining records 201–250 and no top-level search_after cursor. Save these last 50 records and stop. All 250 records have now been retrieved in three successful calls.

The rule to remember

Each response supplies the cursor for the next request. Keep the search unchanged, replace the cursor each time, and stop when no next cursor is returned. No page numbers are needed.

Working with large result sets

For large searches, total_results may be capped at 10,000, with a total_results_note explaining the limit. More records may still be available, so follow the returned cursor rather than stopping at that count. Cursor pagination preserves the API's result order; it does not freeze the database while updates are being added.


Result Modes - End of Life

Retiring soon
ACTION REQUIRED

End-of-Life Notice: The &mode= parameter has reached end of life and will be permanently disabled soon. This includes the Mini (mode=mini), Micro (mode=micro) and Domains Only (mode=domains) result modes. Please remove the mode parameter from your API requests and use the default response format, which returns up to 100 results per call.

REMOVE FROM REQUESTSmode=mini  ·  mode=micro  ·  mode=domains
USE GOING FORWARDDefault format + search_afterUp to 100 results per call

Why we are making this change

The larger legacy result modes create uneven workloads: a single request can require substantially more database retrieval, response serialization, memory and transfer time. Under concurrent use, these large requests can become bottlenecks and increase response times for other searches. Standardizing on batches of 100 results keeps resource use more predictable and helps maintain consistent API performance.

Need more than 100 results?

To retrieve more than 100 results, continue through successive batches using search_after as explained above. If your application needs only selected fields or domain names, extract them from search_result in the default response. The legacy mode-specific response formats will no longer be available after retirement.


Retrieving Data in XML Format

Simple add "&format=xml" to your API call and get results in XML Format.

https://api.whoxy.com/?key=xxxxx&reverse=whois&name=John+Smith&format=xml

Kindly use XML format only if your application strictly requires XML data. Compared to lightweight JSON format, XML carries a lot of extra baggage. This results in slower data transmission, and affects the overall performance of your application interacting with our API. We highly recommend you use JSON format whenever possible.


Account Balance Check

You can check your account's API query balance through:

https://api.whoxy.com/?key=xxxxx&account=balance

Sample Output: JSON Schema • XML Schema • JSON Live Results • XML Live Results


API Status Codes

Every API call will return a Status of either: 0 (ERROR) or 1 (SUCCESS)
In case of Status 0, the reason behind failure of the API call will also be returned.

Sample Output: Invalid API Key (JSON) • Invalid API Key (XML)


Pricing & Packages

Reverse Whois Pricing Total API Calls Price CPM Purchase
1,000 Reverse Whois API Queries 1,000 $10 $10.00 Order Now
5,000 Reverse Whois API Queries 5,000 $50 $10.00 Order Now
10,000 Reverse Whois API Queries 10,000 $100 $10.00 Order Now
50,000 Reverse Whois API Queries 50,000 $400 $8.00 Order Now
250,000 Reverse Whois API Queries 250,000 $1,500 $6.00 Order Now
1 Million Reverse Whois API Queries 1,000,000 $4,000 $4.00 Order Now
5 Million Reverse Whois API Queries 5,000,000 $10,000 $2.00 Order Now

Frequently Asked Questions

  1. API Key is available through: Account Manager » API Settings
  2. Depending upon your search query, the results might contain multiple WHOIS records of the same domain name. However all the WHOIS records will be unique, and there will be no duplicate results. We save additional WHOIS record of a domain name only when there are any changes compared to the previous record. This is how we archive historical WHOIS records.
  3. As we do not save Raw Whois text in our database, this is not included with Reverse Whois results.
  4. Yes, this can be activated through: Account Manager » Account Settings
  5. Please signup now and receive FREE API Credits to test the Reverse Whois API.

If you have any questions, please contact us at Email Address