Loading
Loading
Query real-time WHOIS records for any IPv4 or IPv6 address. Returns organization, CIDR range, network handle, and abuse contacts - sourced live from all 5 RIRs.
The WHOIS IP Lookup API provides full network registration data including inet_num blocks, organization details, technical and abuse contacts, routing information, and raw WHOIS text. Perfect for abuse reporting, fraud detection, and network intelligence.
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.
formatoptionalStringdefault: jsonResponse format: 'json' (default) or 'xml'.
iprequiredStringIPv4 or IPv6 whose WHOIS required
A successful request returns a 200 OK response with a JSON object containing the WHOIS data. The response includes the top-level fields listed below. See the response preview on the right for the full JSON structure.
statusIndicates if the WHOIS response from whois_server is a complete response
ip_addressIP address (IPv4 or IPv6) to query live WHOIS
query_timeDate and time of WHOIS query in the yyyy-MM-dd HH:mm:ss format
whois_serverWHOIS host server used to query the ip_address
whois_raw_responseWHOIS response (unparsed) from the whois_server WHOIS server
r_whois_raw_responseWHOIS response from the rwhois server
start_ip (String), end_ip (String), cidr (Array<String>), net_name (String), net_handle (String), …
handle (String), address (Array<String>), street (String), city (String), district (String), …
handle (String), name (String), type (String), description (Array<String>), address (Array<String>), …
handle (String), name (String), address (Array<String>), street (String), city (String), …
handle (String), name (String), address (Array<String>), street (String), city (String), …
handle (String), name (String), address (Array<String>), street (String), city (String), …
route (String), origin (String), description (Array<String>), country (String), pingable (Array<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.
Request-param 'ip' (<ip>) is not valid.
Request-param 'format' (<format>) is not valid. Supported formats are json, xml