Products APIs Data Feeds Web Tools Domain Research & Monitoring Enterprise Packages AI Deep Research
WHOIS / WHOIS History
WHOIS / WHOIS History

Provide current and historical ownership information on domains / IPs. Identify all connections between domains, registrants, registrars, and DNS servers.

DNS / DNS History
DNS / DNS History

Look into all current and historical DNS / IP connections between domains and A, MX, NS, and other records. Monitor suspicious changes to DNS records.

IP Geolocation / IP Netblocks
IP Geolocation / IP Netblocks

Get detailed context on an IP address, including its user’s geolocation, time zone, connected domains, connection type, IP range, ASN, and other network ownership details.

Domain Research Suite (DRS)
Domain Research Suite (DRS)

Access our web-based solution to dig into and monitor all domain events of interest.

Domain Research Suite (DRS)
Domain Research Suite (DRS)

Get access to a web-based enterprise-grade solution to search and monitor domain registrations and ownership details for branded terms, fuzzy matches, registrants of interest, and more.

New gTLD Intelligence Services (NGIS)
New gTLD Intelligence Services (NGIS)

Independent, evidence-based DNS and abuse intelligence for applicants, advisors, governments, and counsel participating in the ICANN 2026 New gTLD Program.

Research
Monitoring
White-Label
Predictive Threat Intelligence Feeds
Predictive Threat Intelligence Feeds

Predictive threat intelligence is your best first line of defense. Subscribe to the feeds to strengthen your cybersecurity posture. Contact us today for more information.

WhoisXML API Internet Infrastructure
Internet Infrastructure

Unlock integrated intelligence on Internet properties and their ownership, infrastructure, and other attributes.

Enterprise API Packages
Enterprise API Packages

Our complete set of domain, IP, and DNS intelligence available via API calls as an annual subscription with predictable pricing.

Security Intelligence (SI) Suite
Security Intelligence (SI) Suite

Offers complete access to WHOIS, IP, DNS, and subdomain data for product enrichment, threat hunting and more.

Attack Surface Discovery API
Attack Surface Discovery API

Uncover entire attack surfaces with this API to embed asset discovery, vulnerability scanning, and technology metadata into your platform. Now in early access.

MCP Server
MCP Server

Talk to our APIs using LLMs. Connect your preferred LLM to WhoisXML API and simply chat about WHOIS, DNS, threat intelligence, and more.

Jake AI
Jake AI

I’m your Domain Intelligence Assistant. I make it easy to explore WHOIS, DNS, and threat data from WhoisXML API — I’m cloud-based, fast, and always ready to help.

WhoisXML API Domain Intelligence Advisor (via ChatGPT)
WhoisXML API Domain Intelligence Advisor (via ChatGPT)

A custom GPT for WHOIS, DNS, IP, and threat intelligence research. Connects ChatGPT directly to WhoisXML API to enable fast, conversational investigations and domain insights.

Discover what you really pay for when buying commercial Internet intelligence data.

Download now
×
Contact Us
API docs Integrations Pricing Blog
Making requests Output Error handling Limits Server-to-Server OAuth
Balance information Generate new API key Resources

Making requests

Our Hosted Whois Web Service provides registration details, also known as WHOIS Records, of domain names, IP addresses or an email address.

WhoisXMLAPI.com provides RESTful APIs. It is designed for server-to-server communication between your system and the WhoisXMLAPI.com network using HTTPs protocol. Query responses are delivered in either XML or JSON format based on your requests which are made via GET/POST methods.

To get started you need an account with WhoisXmlApi.com. Authentication is required each time in order to use the API. The first 500 WHOIS API calls are complimentary when you register for a free account.

API endpoints

You can use the following endpoints to make requests to the WHOIS API:

  • Use the GET method with query parameters
  • Use the POST method with JSON body

Note: recommended request timeout for the API is 100 seconds.

GET https://www.whoisxmlapi.com/whoisserver/WhoisService?apiKey=API_KEY&domainName=google.com
POST https://www.whoisxmlapi.com/whoisserver/WhoisService
It takes up to a minute to activate your account after the registration.

Example of cURL request with body in JSON format

curl --location 'https://www.whoisxmlapi.com/whoisserver/WhoisService' \
    --header 'Content-Type: application/json' \
    --data '{
        "domainName": "google.com",
        "apiKey": "API_KEY"
    }'

Example of cURL request with an Authorization header

curl --location 'https://www.whoisxmlapi.com/whoisserver/WhoisService?domainName=google.com' \
--header 'Authorization: Bearer %accessToken%'

Postman collection

Postman is a desktop and web application that allows you to make requests to an API from a graphical user interface. We recommend using Postman with WhoisXML APIs endpoints when exploring the APIs functionality, as well as when you are troubleshooting issues with your application.

The WhoisXML API Postman collection is available at the following links:

The collection includes a preconfigured environment. You will need to set up the api_key variable to fire each request. Get your personal API KEY on the My products page. If you have questions related to the API, contact us.

Authorization: required

Use your personal API key or Server-to-Server OAuth token to authenticate your requests. You can find your API key on the My products page. The apiKey query parameter has the highest priority. If you provide the apiKey parameter, the service will ignore the Authorization header if it is present.

Via the query parameter

apiKey

Get your personal API key on the My products page.

Via the header

Authorization

API key or Server-to-Server OAuth token.

Authentication scheme: Bearer.

Example:
– Authorization: Bearer %API_KEY%
– Authorization: Bearer %OAUTH_ACCESS_TOKEN%

Input parameters: required

domainName

The domain/IPv4/IPv6/email address for which WHOIS data is requested.

Input parameters: optional

rdap

0 results in retrieving data via Auto protocol.

1 results in retrieving data via RDAP protocol.

2 results in retrieving data via WHOIS protocol.

Acceptable values: 0 | 1 | 2

Default: 0

Please note that the RDAP protocol is not supported for all TLDs. Available for domains and IP records.

The Auto protocol retrieves the best data available from either RDAP or WHOIS based on ongoing technical tests and server monitoring across TLDs. For instance, if data cannot be retrieved through the WHOIS protocol, it will automatically be obtained via the RDAP protocol. If both protocols return data of equivalent quality, WHOIS will be preferred to minimize impact on the client side.

Monitoring of top-level domains across RDAP and WHOIS protocols: https://rdap.wxapros.com/.
maxCacheAgeHours

Maximum acceptable age, in hours, of a cached record. 0 requests the freshest record; -1 returns cached data of any age. Any value from 0 up to 24 is raised to 24 hours (the minimum refresh window).

Acceptable values: integer ≥ -1

Default: 168
preferFresh

1 narrows the acceptable cache age to 48 hours, returning a fresher record.

Cannot be combined with _hardRefresh.

Acceptable values: 0 | 1 | true | false

Default: 0
_hardRefresh

1 provides real-time data at a total cost of 5 WHOIS API credits, narrowing the acceptable cache age to 24 hours.

Cannot be combined with preferFresh.

Acceptable values: 0 | 1 | true | false

Default: 0
_dbOnly

1 results in reading cached data only, or returning an error (WHOIS_03) if no cached data is available.

Acceptable values: 0 | 1 | true | false

Default: 0
exactMatch

For IP lookups only: 1 enables RPSL exact-match (-x). Ignored for domain lookups.

Acceptable values: 0 | 1 | true | false

Default: 0
ignoreRawTexts

1 results in stripping all raw text from the output (rawText, header, footer, strippedText, and the rawText of name servers and contacts).

Acceptable values: 0 | 1 | true | false

Default: 0
cmd

GET_DN_AVAILABILITY (case-insensitive) returns the compact DomainInfo response instead of the full record (see Output). Any other value returns the normal record.

Acceptable values: GET_DN_AVAILABILITY

Default: no value
outputFormat

Response output format, matched case-insensitively. Any unrecognized value falls back to XML.

Acceptable values: JSON | XML

Default: XML

Unknown parameters are ignored. Sending a parameter the API does not recognize (e.g. the legacy getMode) does not cause an error — the lookup runs normally and the extra parameter is ignored.

Deprecated parameters

Kept for backward compatibility; no longer affect the response
da Deprecated

Deprecated: this parameter is ignored and is now always handled as 1.

1 results in a quick check on domain availability, 2 is slower but more accurate. Results are returned under WhoisRecord → domainAvailability (AVAILABLE | UNAVAILABLE | UNDETERMINED)

Acceptable values: 0 | 1 | 2

Default: 0
ip Deprecated

Deprecated: this parameter is ignored and is now always handled as 1.

1 results in returning IPs for the domain name.

Acceptable values: 0 | 1

Default: 0
ipWhois Deprecated

Deprecated: this parameter is ignored.

1 results in returning the WHOIS record for the hosting IP if the WHOIS record for the tld of the input domain is not supported.

Acceptable values: 0 | 1

Default: 1
checkProxyData Deprecated

Deprecated: this parameter is ignored.

1 results in fetching proxy/WHOIS guard data, if it exists, in the WhoisRecord → privateWhoisProxy schema element.

Acceptable values: 0 | 1

Default: 0
thinWhois Deprecated

Deprecated: this parameter is ignored.

1 results in returning WHOIS data from registry only, without fetching data from registrar. Returned registry data corresponds to the WhoisRecord → registryData schema element.

Acceptable values: 0 | 1

Default: 0
callback Deprecated

Deprecated: this parameter is ignored.

A javascript function used when outputFormat is JSON; this is an implementation known as JSONP which invokes the callback on the returned response.
registryRawText Deprecated

Deprecated: this parameter is ignored.

A string representing the registry WHOIS raw text to be parsed; works only when the _parse parameter is equal to 1.
registrarRawText Deprecated

Deprecated: this parameter is ignored.

A string representing the registrar WHOIS raw text to be parsed; works only when the _parse parameter is equal to 1.
multiIdIana Deprecated

Deprecated: this parameter is ignored.

1 results in having a multi ID IANA match for parsing registrarName to get registrarIANAID when it is not a strict match.

Acceptable values: 0 | 1

Default: 0
_parse Deprecated

Deprecated: this parameter is ignored.

1 provides parsing for input WHOIS raw texts described below.

Acceptable values: 0 | 1

Default: 0

Free access

After Sign Up you automatically get a free subscription plan limited to 500 queries.