Home / Free domain availability checker
Free domain availability checker
Free to check. No card, ever.
What free actually means here
Domain availability checking is free and has no account requirement. You can open the page, paste a list, and read the results without giving an email address. There is no trial period on it and no card on file.
AI name generation is free too, but it does ask for a free account — each run spends real model time, and an account is the only identity a daily allowance can honestly follow. Checking stays open to everyone.
That is worth stating plainly because "free" is used loosely in this category. Several tools describe themselves as free and then require an account before showing results, or cap the free tier at a handful of lookups a day.
What free covers, precisely
| Feature | No account | Free account |
|---|---|---|
| Domain availability checking | Yes | Yes |
| Bulk lists, up to 2,000 | Yes | Yes |
| Excel and CSV export | Yes | Yes |
| AI name generation | — | 25 searches a day |
| Names per AI search | — | up to 100 |
There is no paid tier right now. The only thing an account changes is access to AI naming, which costs real model time per run and needs an identity a daily allowance can follow.
Why there are three answers, not two
Every check returns available, taken, or unknown. Most tools return only the first two, which forces them to guess when a registry does not answer clearly.
| Result | What it means |
|---|---|
| Available | The registry says no record exists, and the domain does not resolve in DNS. |
| Taken | The registry has a record, or the domain resolves. |
| Unknown | The registry did not answer, rate-limited the request, or replied ambiguously. |
Unknown is deliberate. A false "available" is the one wrong answer that costs you money — you build a plan around a name you cannot have. Reporting uncertainty is more useful than reporting a guess.
How fast registry lookups actually are
RDAP and WHOIS both answer the same question, but not at the same speed. These figures are from querying the same 16 registered domains through each protocol in turn, sequentially and without concurrency, so they describe the protocols rather than any particular thread pool.
| Protocol | Median | 95th percentile | Answered |
|---|---|---|---|
| RDAP | 179 ms | 782 ms | 16 of 16 |
| WHOIS | 355 ms | 529 ms | 15 of 16 |
RDAP answered about twice as fast at the median, which is why it is tried first. Its 95th percentile is the higher of the two, though — a small number of RDAP endpoints are slow enough that WHOIS would have been quicker for those specific names. The one WHOIS failure is the reason a fallback exists in both directions rather than one.
Measured 6 September 2026 from a single server in Europe, n=16 per protocol. Latency varies by registry and by network location, so treat these as one honest data point rather than a universal benchmark.
What happens to your searches
DotSeeka keeps anonymous search statistics — the domain or description searched, when, and the country it came from — to understand what people are looking for. They are never linked to an account, a device or an IP address, and never sold or shared.
The common worry about domain front-running — searching a name and finding it registered shortly after — comes from search boxes operated by companies that also sell domains. DotSeeka does not sell domains and does not act on searches.