dotsweep vs Whose.Domains
A free domain-intelligence API covering WHOIS, DNS records, domain history, SSL certificate data and a domain score, with availability as one search type inside a bulk endpoint.
| dotsweep | Whose.Domains | |
|---|---|---|
| No key | YesNo key, no account, no signup. curl https://dotsweep.com/check/example.com works from a cold start. |
PartlyTheir documentation does not state a general key requirement, but several endpoints "require a page session token and can only be used from" their own tool pages, so those are not callable from your own code. |
| Admits doubt | YesA registry that is throttled, timed out or publishes no RDAP resolves to estimated, never available. A 429 from one registry does not become a confident answer about another one on the same host. |
Not documentedThe bulk endpoint accepts a searchType of availability, and the documentation gives no response fields for it. We did not test it. |
| Renewal + term | YesRegistration and renewal are separate figures, a first-year discount is flagged as a promotion, and an extension the registry sells only in multi-year terms is multiplied out so the leading number is what leaves your account. | NoTheir documentation states that no pricing information is included. |
| Eligibility | Partly38 extensions have had their registry policy read, 33 of them with an eligibility rule, each citing the registry's own page and the date it was read. An extension that is not in that set asserts nothing. | Not documentedNot mentioned in the documentation we read. |
| Free tier | Yes120 requests a minute, counted as requests rather than domains, and a batch endpoint carrying 20 domains each. Edge cache hits are not counted at all. | PartlyFree, at 5 to 10 requests a minute per IP depending on the endpoint. |
| Assistant-ready | YesAn MCP server at /mcp over the same handlers, plus /llms.txt, so an assistant can call it without a wrapper. |
Not documentedWe found no MCP server or assistant-facing reference on the pages we read. |
Where Whose.Domains is the better choice
Written first because a comparison written by one of the two products is worth nothing if it cannot say this.
- Domain history with WHOIS diffs, SSL certificate data, reverse IP and a health score, none of which we return.
- Free with no invoice and no account for the open endpoints, which is the same position we occupy.
- Expiring-domain discovery, which is a different question from availability and one we do not answer.
Where dotsweep is different
- No key, no account, no signup.
curl https://dotsweep.com/check/example.comworks from a cold start. - A registry that is throttled, timed out or publishes no RDAP resolves to
estimated, neveravailable. A 429 from one registry does not become a confident answer about another one on the same host. - Registration and renewal are separate figures, a first-year discount is flagged as a promotion, and an extension the registry sells only in multi-year terms is multiplied out so the leading number is what leaves your account.
- 38 extensions have had their registry policy read, 33 of them with an eligibility rule, each citing the registry's own page and the date it was read. An extension that is not in that set asserts nothing.
- An MCP server at
/mcpover the same handlers, plus/llms.txt, so an assistant can call it without a wrapper.
The unconfirmed-rather-than-available rule is the one worth explaining,
because it is the only wrong answer in this category that costs somebody money.
A registry that is rate-limiting you often phrases the refusal in words a parser
reads as "no such domain", so the naive result of a throttled lookup is a
confident "available" for a name somebody already owns. dotsweep asserts this in
its test suite in both engines, and marks the answer estimated
instead.
Is dotsweep better than Whose.Domains?
Not at everything, and not for every job. Whose.Domains does this better: Domain history with WHOIS diffs, SSL certificate data, reverse IP and a health score, none of which we return. dotsweep answers a different question: it needs no key or account, it returns the renewal price and the minimum term rather than the advertised first-year figure, it says who is allowed to register the extension, and it reports a throttled or unreachable registry as unconfirmed rather than available.
What Whose.Domains documents
- https://whose.domains, read 2026-07-30
- https://whose.domains/api-docs, read 2026-07-30
How we know this, and what we did not do
Every claim about another product here was read from that vendor's own documentation, and each one is listed with the page and the date it was read. No figure comes from a review, a listicle or another comparison.
We did not benchmark any of these services. Nothing on this page reports a measurement, and where a row says "not documented" it means their documentation did not answer the question and we did not test it. It is not a quiet way of saying no. Getting that distinction wrong is how the rest of a comparison table stops being worth reading, and it is the same rule the rest of this site follows about extensions whose registry policy nobody has read.
If something here is out of date or wrong, the date next to it is there so you can tell which, and support@dotsweep.com reaches a person.
Check a name without signing up for anything
curl https://dotsweep.com/check/example.com