# WhoisXML

Last-known WHOIS, reverse WHOIS, and reverse IP from Domain Research Suite.

URL: https://osintverse.com/docs/providers/whoisxml

WhoisXML Domain Research Suite returns the latest defined WHOIS fields (including values that are redacted on the live record), a history archive count, reverse WHOIS by email or registrant name, and domains hosted on an IP.

## Capabilities

* Domain Info last-known WHOIS with redacted-now flags
* WHOIS history record count without a 50-credit full dump
* Reverse WHOIS by email or registrant name
* Reverse IP: domains hosted on an IPv4 address
* Published corpus, measured 9 July 2026: 28.7 billion+ WHOIS records, 1.2 billion+ historical domains, 374 million+ active domains, and 7,596+ TLDs

## Data

WhoisXML’s [figures page](https://main.whoisxmlapi.com/whoisxmlapi-in-figures), measured 9 July 2026, lists &#x2A;*28.7 billion+** WHOIS records, &#x2A;*1.2 billion+** domains tracked historically, &#x2A;*374 million+** active domains, and &#x2A;*7,596+** TLDs. It also lists 99.5% of IP addresses in use and 10.6 million+ IP netblocks. SearchIn queries last-known WHOIS, the history archive count, reverse WHOIS, and reverse IP. It does not query the DNS, subdomain, or threat-intel products on that page.

## What you get back

* WHOIS card with last-known contacts and “now redacted” badges
* Nameservers from Domain Info
* History archive count
* Reverse WHOIS and reverse-IP domain lists

## UI workflow

Open SearchIn and choose Domain, Email, Name, or IP.

Select WhoisXML as the provider.

Review last-known WHOIS fields, history count, or the related domain list.

## Sample queries

| Input type | Query               | Notes                             |
| ---------- | ------------------- | --------------------------------- |
| `domain`   | `example.com`       | Last-known WHOIS + history count  |
| `email`    | `admin@example.com` | Domains tied to an email          |
| `name`     | `Alex Rivera`       | Domains tied to a registrant name |
| `ip`       | `203.0.113.10`      | Domains hosted on an IP           |

## Pricing

`email` **$0.40** · `domain` **$0.60** · `name` **$0.40** · `ip` **$0.50**

## Best for

* Recovering contacts that are redacted on live WHOIS
* Mapping an email or name to a domain portfolio
* Finding other hosts on the same IP

## How it works & why through OSINTverse

### How the request runs

1. Choose domain, email, name, or IP and select WhoisXML.
2. Domain queries read Domain Info for the last-known WHOIS fields, including values now hidden on the live record.
3. SearchIn reports the WHOIS history archive count without pulling a full history dump.
4. Email and name run reverse WHOIS; IP runs reverse IP to list domains hosted on that address.

**Coverage.** WhoisXML measured these figures on 9 July 2026: 28.7 billion+ WHOIS records, 1.2 billion+ domains tracked historically, 374 million+ active domains, and 7,596+ TLDs. SearchIn queries last-known WHOIS, the history archive count, reverse WHOIS, and reverse IP.

### Why route WhoisXML through OSINTverse

- Last-known WHOIS surfaces contacts that are redacted on the live record, flagged with a clear “now redacted” badge.
- You get the history archive count without paying for a 50-credit full history dump.
- One flat SearchIn charge per query instead of reconciling a pooled DRS credit balance across products.

|  | WhoisXML directly | Through OSINTverse |
| --- | --- | --- |
| Getting started | WhoisXML bills Domain Research Suite in pooled DRS credits shared across many products, where a single full WHOIS history dump alone costs 50 credits. | Sign in, top up from $10, and run WhoisXML the same minute — no vendor contract, seat, or sales call. |
| What a query costs | Plan, credit pack, or contract pricing set by the vendor and paid up front. | Pay per query from your prepaid balance — WhoisXML starts at $0.40 for email lookups, with the exact price shown before you run it. |
| Failed lookups | Handled under the vendor's own credit and refund policy. | Automatically refunded to your wallet — a search that fails upstream after billing is not charged. |
| Output format | A vendor-specific response shape you normalise and render yourself. | Normalised result panels plus the raw JSON, returned by the same POST /v1/search contract as every other integration. |
| Cross-source work | Copy-paste between vendor dashboards to follow a lead into another dataset. | Results join one case graph, so you can pivot an entity into any of the other 16 integrations in a click. |
| Running it for a team | Per-seat or per-account access, billed and administered per analyst. | One shared team wallet with roles, provider allowlists, enforced MFA, and audit history — no per-seat fee. |
| Volume work | Script the vendor API yourself, including retries, polling, and rate handling. | Bulk search takes up to 50 queries across selected providers in one submission (max 100 jobs), with per-job status and partial-failure handling. |

- **One wallet, no subscriptions.** Top up prepaid USD from $10 and spend it a query at a time across all 17 integrations. No monthly fee, no seat count — and the balance never expires.
- **Failed searches are refunded.** If an upstream provider errors or times out after the charge, the search is marked refunded and the money goes back to your wallet automatically.
- **One API for every source.** The same POST /v1/search contract and x-api-key header work for every integration, so adding a source to your automation is a one-word change.
- **Cases and pivot graph.** Results land in a named case you can reopen. Entities become graph nodes you can pivot from into any other integration without retyping.
- **Team wallets and controls.** Share one balance with roles, provider allowlists, enforced MFA, and audit history — instead of buying a vendor seat for every analyst.
- **Exports built in.** Download any result as JSON, CSV, or PDF, and export the case graph as PNG, SVG, entities CSV, or graph JSON.

### Good to know

- Last-known values can lag the current live record.
- Reverse WHOIS and reverse IP are only as complete as the DRS index.

## API example

Try `whoisxml` free with mock data in the API sandbox: https://osintverse.com/developers/sandbox

> Invalid `provider` + `input_type` pairs return HTTP 422. Confirm combinations with [GET /v1/providers](https://osintverse.com/docs/api/overview) or the [pricing matrix](https://osintverse.com/docs/pricing).

Run this in the [SearchIn UI](https://osintverse.com/searchin/search) or create an [API key](https://osintverse.com/dashboard/api). Full HTTP reference: [search workflow](https://osintverse.com/docs/api/search). Marketing overview: [WhoisXML integration](https://osintverse.com/integrations/whoisxml).
