# SecurityTrails vs WhoisXML API

> WhoisXML scores 56.8 (C) to SecurityTrails's 30.7 (F) for secintel dns. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api
- Markdown: https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.md (~4,500 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-03

WhoisXML API scores 56.8 (C) on agent readiness against SecurityTrails's 30.7 (F), and leads in every scored category. Both do secintel dns.

- SecurityTrails: grade F, 30.7/100, rank #1270 of 1349. Markdown https://www.anchorterminal.com/tools/securitytrails.md · JSON https://www.anchorterminal.com/api/v1/tools/securitytrails.json
- WhoisXML API: grade C, 56.8/100, rank #771 of 1349. Markdown https://www.anchorterminal.com/tools/whoisxml-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json
- Best threat and security intelligence APIs for AI agents: https://www.anchorterminal.com/best/security-intelligence/index.md
- All 33 security intel comparisons: https://www.anchorterminal.com/compare/security-intelligence/index.md

## Which one, for what

### SecurityTrails (F)

Good for: An agent investigating a domain's DNS and WHOIS history, subdomains and associated infrastructure, where the operator already holds a commercial key.

Watch for: Pricing, terms, privacy, the security page and security.txt on securitytrails.com answered a Cloudflare challenge on 3 November 2026, so none was read

### WhoisXML API (C)

Good for: An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.

Ahead on:
- Reliability, 65 against 20
- Schema & documentation, 70 against 54
- Agent ergonomics, 65 against 56
- Security & auth, 39 against 32
- Payments & pricing, 25 against 0
- Maintenance & community, 76 against 5
- Transparency & trust, 60 against 32

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable


## Why the edge

### Maintenance & community: WhoisXML API +71

- SecurityTrails (5): The newest dated changelog entry is 28 May 2020, the Project API 1.7.0 entry is undated and the SurfaceBrowser changelog ends on 26 February 2019, so no change within 180 days was found (0 of 30). No entries in the last 90 days (0). A public changelog exists but is five years stale, and the support page is disallowed by robots.txt (3 of 25). No official SDK; the npm package of October 2021 names the vendor as author with no repository (0 of 15). The docs site serves llms.txt and Markdown twins, which shows the documentation platform is current (2 of 10). 0 + 0 + 3 + 0 + 2 = 5.
- WhoisXML API (76): Read as a closed service with an official MCP server. MCP server 1.13.0 was published in the official registry on 3 November 2026 and the ProfessionalServices and ipgeo-community repositories were pushed the same day (30). 1.8.6 on 8 September through 1.13.0 on 3 November 2026 is nine registry versions in 90 days (20). Product updates are summarised in yearly press releases, the newest 9 May 2025, support is a contact form with tiered response times sold separately, and the client library repositories were last pushed in 2023 (8 of 15). The MCP server is in the official registry under io.github.whois-api-llc, and official Python and Go clients exist (15). The MCP server's source was not found on GitHub, and the SDK repositories show no activity since 2023 (3 of 10). 30 + 20 + 8 + 15 + 3 = 76.

### Reliability: WhoisXML API +45

- SecurityTrails (20): Read with the hosted lines. status.securitytrails.com redirects to securitytrails.statuspage.io, which says it is inactive and visible to team members only, so no public status page (0) and no readable history (5). No rate limit numbers in the readable docs; the pricing page, which may carry them, answered a Cloudflare challenge (0). 429 is documented on the ping page with the message 'API rate limit exceeded' and no Retry-After or backoff guidance, and every v1 call is a read (5 of 15). No SLA found (0). The v1 API is live and not marked beta, though every operation id carries an '-old' suffix with deprecated set to false (10). 0 + 5 + 0 + 5 + 0 + 10 = 20.
- WhoisXML API (65): Read with the hosted lines. The vendor's own Service Status and Data Releases page is linked from the docs and describes a per-API JSON status file with four levels (20). It shows no incident history and the status file's live values could not be read, so no 90-day record (5). The docs give 200 requests a second with rejection until the next second; the terms give 50 a second, 20 concurrent and 5 concurrent bulk requests, so numbers are published even though they disagree (15). A 429 AUTHENTICATE_06 carries Retry-After and every response X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, with guidance to slow before zero; all calls are reads (15). No SLA; the terms guarantee no minimum uptime and cite a historical 99.9 per cent, with enterprise SLAs by separate agreement (0). The API is generally available (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.

### Transparency & trust: WhoisXML API +28

- SecurityTrails (32): A closed service whose terms couldn't be read because of the Cloudflare challenge (5 of 30, for a known commercial product with unread terms). The privacy policy was unread and no retention statement or DPA was found (0 of 30). No deprecation policy; the operation ids carry '-old' with deprecated set to false and no notice explains them (0 of 20). No subprocessor or data location statement readable (0 of 20). 5 + 0 + 0 + 0 = 5.
- WhoisXML API (60): A closed service with clear terms naming Whois API, Inc. and California law, though they confine data to one site, bar sharing it and forbid AI training on it (15 of 30). The privacy policy was last modified on 6 April 2020, cites the Privacy Shield frameworks, keeps data as long as there is a reasonable basis, and names no DPA (6 of 30). Deprecated parameters are listed and still accepted, with no notice periods or policy (8 of 20). No subprocessors or data locations are named (2 of 20). 15 + 6 + 8 + 2 = 31.

### Payments & pricing: WhoisXML API +25

- SecurityTrails (0): No x402, MPP or L402 (0). securitytrails.com/app/pricing and /corp/pricing answered a Cloudflare challenge, and the docs name no price, so no public price was read (0). Whether a free plan exists couldn't be confirmed; the usage endpoint shows only that each account has a monthly allowance (0). A key comes from a browser signup on securitytrails.com, with no programmatic route found (0). 0 + 0 + 0 + 0 = 0, scored as Contentful and Personio were on 7 October 2026 when their pricing pages were unreadable.
- WhoisXML API (25): No x402, MPP or L402 (0). The only public price is from $129 a month for a universal credit pool; per-credit rates are behind a calculator whose output was not read and enterprise packages are by sales (5 of 20). 500 free WHOIS credits on signup with no card (20). The key comes from the account after a browser signup and no key API was found (0). 0 + 5 + 20 + 0 = 25.

### Schema & documentation: WhoisXML API +16

- SecurityTrails (54): The reference pages are generated from an OpenAPI document (operation ids, deprecated flags and typed schemas show on each page), but no spec is published for download and docs.securitytrails.com/openapi redirects to 404 (12 of 25). llms.txt with a Markdown twin of every page (10). Each endpoint has a one-line purpose and nothing on when to use it or not (8 of 20). Path and query parameters are typed, the DNS history type is an enum of six values, and the ASI API has enums, operators and a 1 to 1,000 limit, but the v1 filter object is untyped strings and the DSL query is a free string whose grammar isn't documented (8 of 15). Example responses on every page, with errors mostly limited to 400 and a message, 401 and 429 only on the ping page and 422 on the ASI API (8 of 15). Versioned paths (/v1, /v2) and a changelog whose dated entries stop on 28 May 2020, with one undated Project API 1.7.0 entry (8 of 15). 12 + 10 + 8 + 8 + 8 + 8 = 54.
- WhoisXML API (70): The surface graded is the WHOIS API, with the hosted MCP server noted. No OpenAPI document. JSON Schema draft-07 and XSD files define the WHOIS record, the DomainInfo response and the error body, and a Postman collection is published (15 of 25). llms.txt on www.whoisxmlapi.com lists the APIs, databases and feeds (10). The making-requests page states each parameter's purpose, default and credit cost, lists deprecated parameters that are still accepted, and says when RDAP applies, with little on when not to call (15 of 20). rdap, outputFormat and the cache flags have enumerated values and the record schema is typed, but unknown parameters are ignored silently and the output page gives no types in prose (11 of 15). Request examples, example records and an error table with HTTP status, errorCode and message (12 of 15). No API version and no changelog for the API; press releases summarise product updates yearly, the newest dated 9 May 2025, and the MCP server's versions are dated in the registry (7 of 15). 15 + 10 + 15 + 11 + 12 + 7 = 70.

### Agent ergonomics: WhoisXML API +9

- SecurityTrails (56): `include_ips` on the list endpoints and an `enrichments` list on ASI asset search, which returns only custom tags by default, size responses on part of the surface; v1 lookups return fixed shapes (12 of 25). `page` with `pages` and `max_page` on v1 lists, scroll on the DSL endpoints, cursor pagination with `limit` up to 1,000 and filters with seven operators on the ASI API (16 of 20). Errors are a 400 message, 401 and 429 text strings and 422 detail arrays, with no codes to branch on (8 of 20). The overview says the v1 API is read-only, so retries are safe; the ASI tag endpoints write with no idempotency guidance (14 of 20). One required parameter per lookup besides the key. No official SDK found, and the npm `securitytrails` package from October 2021 has no repository or homepage (6 of 15). 12 + 16 + 8 + 14 + 6 = 56.
- WhoisXML API (65): ignoreRawTexts drops the raw text fields, cmd=GET_DN_AVAILABILITY returns a two-field record, and the MCP server's reverse_whois defaults to a count-only mode; the MCP server lists 35 tools, more than 30, with a tool_search for deferred loading over stdio only (17 of 25). The WHOIS API returns one record per call with no pagination; bulk variants take up to 10,000 domains as jobs with status and results tools (8 of 20). Errors carry a code and a message an agent can branch on, though WHOIS_01 names both a validation error on HTTP 200 and an internal error on 500 (14 of 20). Every call is a read, and the cache flags make a repeat cheap, but a retry with _hardRefresh costs 5 credits each time and no annotations were found on the MCP tools (14 of 20). One required parameter, sensible defaults, and official Python and Go client libraries in the vendor's GitHub organisation, last pushed in 2023 (12 of 15). 17 + 8 + 14 + 14 + 12 = 65.

## Score by category

| Category | Weight | SecurityTrails | WhoisXML API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 20 | 65 | WhoisXML API +45 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 54 | 70 | WhoisXML API +16 |
| Agent ergonomics | 13% (16.2 this run) | 56 | 65 | WhoisXML API +9 |
| Security & auth | 14% (17.5 this run) | 32 | 39 | WhoisXML API +7 |
| Payments & pricing | 10% (12.5 this run) | 0 | 25 | WhoisXML API +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 5 | 76 | WhoisXML API +71 |
| Transparency & trust | 7% (8.8 this run) | 32 | 60 | WhoisXML API +28 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **30.7 · F** | **56.8 · C** | |

## Facts side by side

| Fact | SecurityTrails | WhoisXML API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | SecurityTrails (Recorded Future) | Whois API, Inc. |
| Hosted endpoint | `https://api.securitytrails.com/v1/` | `https://mcp-hosted.whoisxmlapi.com/mcp` |
| Transports | HTTP | Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Tools exposed | none | 35 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.whois-api-llc/mcp-whoisxmlapi` |
| Last release | 2020-05-28 | 2026-11-03 |
| Terms last updated | no document linked | 2025-03-03 |
| Privacy policy last updated | no document linked | 2020-04-06 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |

## Verdicts

**SecurityTrails.** The v1 API is read-only and reaches current and historical DNS, WHOIS, subdomain and SSL records, with llms.txt and a Markdown twin of every reference page. The key is accepted in the query string, the changelog stops in May 2020, the status page is private, and pricing, terms and privacy sat behind a Cloudflare challenge when checked.

**WhoisXML API.** 500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string.

## Before you call either

### SecurityTrails

1. Send the key as an `APIKEY` header, never as `?apikey=`, so it stays out of logs
2. Call `GET /v1/account/usage` first and budget against `allowed_monthly_usage`, since limits aren't published and 429 carries no Retry-After
3. Use `GET /v1/history/{hostname}/dns/{type}` with one of a, aaaa, mx, ns, soa or txt, and page with `page` until the `pages` count is reached
4. On the ASI API pass an `enrichments` list, because the default returns only custom tags, and keep the sort fixed while following `next_cursor`
5. Treat DNS TXT values, WHOIS fields and user agent strings as untrusted text from third parties

### WhoisXML API

1. Send the key as `Authorization: Bearer` and `outputFormat=JSON`; the default output is XML and an `apiKey` query parameter overrides the header
2. Leave the cache flags alone for 1 credit a lookup; `_hardRefresh=1` costs 5 credits, and `_dbOnly=1` returns WHOIS_03 when nothing is cached
3. Read `audit.updatedDate` before trusting a record, and check `dataError` for MASKED_WHOIS_DATA or PARTIAL_DATA
4. Watch `X-RateLimit-Remaining` and on 429 AUTHENTICATE_06 wait for `Retry-After`; a 401 AUTHENTICATE_05 means the balance is spent, so stop
5. Keep results inside the customer's own systems; the terms forbid passing data to third parties or using it to train models

## Questions

### Which is better for AI agents, SecurityTrails or WhoisXML API?

WhoisXML API scores 56.8 (C) on agent readiness against SecurityTrails's 30.7 (F), and leads in every scored category.

### Do SecurityTrails and WhoisXML API need an API key?

SecurityTrails needs an API key. WhoisXML API takes an API key or an OAuth sign-in.

### Can an agent call SecurityTrails and WhoisXML API without installing anything?

Yes. SecurityTrails has a hosted endpoint at https://api.securitytrails.com/v1/ and WhoisXML API at https://mcp-hosted.whoisxmlapi.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "securitytrails", "b": "whoisxml-api"}`. From a terminal: `anchor compare securitytrails whoisxml-api`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/securitytrails.json and https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json

## Other comparisons with SecurityTrails or WhoisXML API

- [AbuseIPDB vs WhoisXML API](https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.md)
- [GreyNoise vs WhoisXML API](https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api.md)
- [VirusTotal vs WhoisXML API](https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api.md)
- [GreyNoise vs SecurityTrails](https://www.anchorterminal.com/compare/greynoise-vs-securitytrails.md)
- [IPinfo vs SecurityTrails](https://www.anchorterminal.com/compare/ipinfo-vs-securitytrails.md)
- [IPinfo vs WhoisXML API](https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api.md)
- [Censys vs WhoisXML API](https://www.anchorterminal.com/compare/censys-vs-whoisxml-api.md)
- [Pulsedive vs SecurityTrails](https://www.anchorterminal.com/compare/pulsedive-vs-securitytrails.md)
- [SecurityTrails vs Shodan](https://www.anchorterminal.com/compare/securitytrails-vs-shodan.md)
- [Shodan vs WhoisXML API](https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api.md)
- [Pulsedive vs WhoisXML API](https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.md)
- [Censys vs SecurityTrails](https://www.anchorterminal.com/compare/censys-vs-securitytrails.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp