Provide current and historical ownership information on domains / IPs. Identify all connections between domains, registrants, registrars, and DNS servers.
Look into all current and historical DNS / IP connections between domains and A, MX, NS, and other records. Monitor suspicious changes to DNS records.
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.
Access our web-based solution to dig into and monitor all domain events of interest.
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.
Independent, evidence-based DNS and abuse intelligence for applicants, advisors, governments, and counsel participating in the ICANN 2026 New gTLD Program.
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.
Unlock integrated intelligence on Internet properties and their ownership, infrastructure, and other attributes.
Our complete set of domain, IP, and DNS intelligence available via API calls as an annual subscription with predictable pricing.
Offers complete access to WHOIS, IP, DNS, and subdomain data for product enrichment, threat hunting and more.
Uncover entire attack surfaces with this API to embed asset discovery, vulnerability scanning, and technology metadata into your platform. Now in early access.
Talk to our APIs using LLMs. Connect your preferred LLM to WhoisXML API and simply chat about WHOIS, DNS, threat intelligence, and more.
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.
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.
One Universal API Credit Pool
Simplify API credit purchasing and usage with one balance that works across our product portfolio.
If you are populating a bid request, you do not want to map our category paths onto AdCOM identifiers yourself. Ask for the projection.
Add output_format=openrtb:
curl -X POST "https://website-categorization.whoisxmlapi.com/api/v4/categorize?apiKey=YOUR_API_KEY&output_format=openrtb" \
-H "Content-Type: application/json" \
-d '{"domain": "stackoverflow.com"}'
The response gains an openrtb object. Without the parameter it is null.
{
"domain": "stackoverflow.com",
"primary_category": {
"id": "IAB-631",
"iab_id": "IAB-631",
"name": "Programming Languages",
"tier1": "Technology & Computing",
"tier2": "Computing",
"tier3": "Programming Languages",
"tier4": null,
"confidence": 0.99,
"path": "Technology & Computing > Computing > Programming Languages"
},
"openrtb": {
"cattax": 9,
"cat": ["596", "599", "631"]
}
}
| Field | Type | Description |
|---|---|---|
cattax |
integer | The AdCOM 1.0 "List: Category Taxonomies" enumeration value for the ids in cat. |
cat |
array of string | Raw IAB v3.1 identifiers — no IAB- prefix. |
cattax is always 99 is IAB Tech Lab Content Taxonomy 3.1. It does not vary.
If your integration currently sends 7, that is Content Taxonomy 3.0 — a different taxonomy with different identifiers. Sending 7 alongside 3.1 ids misdescribes your inventory to every bidder downstream. Take the cattax we give you rather than carrying a constant of your own.
cat carries the full path, not just the leafcat lists every node on each predicted category path, root to leaf, in candidate rank order, deduplicated. For Technology & Computing > Computing > Programming Languages you get the tier-1, tier-2 and tier-3 ids.
That is deliberate. Buyers target at different depths: one wants everything under Technology & Computing, another wants Computing specifically. Because the whole path is present, a consumer matches at whatever tier granularity they target without having to walk the taxonomy themselves.
Note the identifiers are raw — "596", not "IAB-596". Elsewhere in the API, id and iab_id carry the prefixed form. OpenRTB wants them bare, so that is what cat holds.
The object is shaped to be used verbatim:
{
"site": {
"domain": "stackoverflow.com",
"cattax": 9,
"cat": ["596", "599", "631"]
}
}
result = categorize("stackoverflow.com", output_format="openrtb")
rtb = result["openrtb"]
bid_request["site"]["cattax"] = rtb["cattax"]
bid_request["site"]["cat"] = rtb["cat"]
The same projection populates app.cattax / app.cat for app inventory.
openrtb is a pure projection of categories[]. Requesting it does not affect classification, caching or billing, and credits_charged is unchanged. primary_category and categories[] keep exactly the same values they would have had without the parameter.
It is also orthogonal to the other opt-ins — you can combine output_format=openrtb with include=policy, include_status=true and output_mode=set on one request.
OpenRTB output is available on the single-domain endpoint only.
A domain with no classifiable content returns no categories, so there is nothing to project. Handle openrtb.cat being an empty array before you write to a bid request — sending an empty cat is better than sending a stale one from a previous lookup.
We are here to listen. For a quick response, please select your request type. By submitting a request, you agree to our Terms of Service and Privacy Policy.