Loading
Loading
Search over 1 billion domains and 3.5 billion WHOIS records to find all domain names linked to any owner name, company, email address, or keyword. Supports keyword, email, owner, and company lookups with pagination and two response modes.
The Reverse WHOIS Lookup API offers two modes: Default Mode returns up to 50 complete WHOIS records per page, while Mini Mode returns up to 100 records with only essential fields per page.
Authorize every request with your API key, passed either as a header or as a query parameter:
X-apiKeyapiKeyThis is version v1.0 of the API.
The following parameters can be used in your API requests. All parameters are passed as query string parameters. At least one of keyword, email, owner, or company is required.
formatoptionalStringdefault: jsonResponse format: 'json' (default) or 'xml'.
keywordoptionalStringkeyword search term in case of reverse WHOIS by keyword
emailoptionalStringemail search term in case of reverse WHOIS by email address (case-insensitive exact or regex match; * wildcard supported)
owneroptionalStringregistrant / owner name search term in case of reverse WHOIS by registrant / owner
companyoptionalStringregistrant company / organization search term in case of reverse WHOIS by organization / company
exactoptionalBooleandefault: falseAccepts 'true' or 'false'. 'true' returns only exact matches for keyword, owner/registrant, or company searches. 'false' returns all matches (default).
modeoptionalStringdefault: default"default" for Complete WHOIS data and "mini" for Only important fields of each matching domain.
pageoptionalIntegerdefault: 1page no. to retrieve paginated results.
A successful request returns a 200 OK response with a JSON object containing the top-level fields listed below. See the response preview on the right for the full JSON structure.
total_ResultTotal results found across the query.
total_PagesTotal number of pages (50 records per page in default mode, 100 in mini mode).
current_PageCurrent number of page.
whois_domains_historicalnum (Integer), domain_name (String), create_date (String), update_date (String), expiry_date (String), …
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
See the HTTP Status Codes documentation for a complete reference of common API errors and HTTP status codes.
Please provide correct value Param [For Technical Support: support@apifreaks.com].
Record not found.