Runs on our server. Names you check are sent to Toolz for the lookup and are not stored.

Domain Search checks whether a domain name is registered, across as many top-level domains as you care to ask about in one go. Type a name, pick a TLD list, and every combination is looked up against the registry that actually holds the record — not a reseller database, not a cached index. The answer for each domain is one of three things: available, taken, or unknown.
Every lookup asks RDAP first. RDAP is the Registration Data Access Protocol (RFC 9083), the structured JSON successor to WHOIS, and it is authoritative: a 404 from a registry RDAP server means the name genuinely is not registered. The list of which server serves which TLD comes from the IANA bootstrap file published under RFC 9224. For the several hundred TLDs that still have no RDAP service — most country-code zones among them — the lookup falls back to WHOIS on TCP port 43, using a per-registry table of servers and of the exact phrase each one uses to say "no such domain". When a bundled WHOIS host has gone stale, IANA is asked which server serves that TLD today.
The third verdict is the one that makes the other two trustworthy. WHOIS is unstructured text, and a registry that is rate-limiting you, refusing your query, or answering about a different name will happily produce a response that a naive substring match reads as "free". Those cases are reported as unknown with the reason attached rather than being guessed at, because "available" is the answer people act on. Availability services that answer "Available" or "Not Available" are read with negation awareness, records that describe a parent zone are rejected, and registries that echo your query back before saying nothing was found are handled explicitly.
Because registry lookups need a raw TCP socket and cross-origin HTTPS requests, this tool runs on our server rather than in your browser — the exception to how most Toolz tools work. The names you check are sent to Toolz to perform the lookups and are not stored. Results stream back as they arrive, so the fast registries answer while the slow ones are still thinking, and any name that comes back available is shown with the registry that operates the TLD and links to register it.
Type a bare name like mybrand, or a full domain like mybrand.com. Several names at once work too — separate them with commas or newlines.
Pick the Popular set, the Bangladesh (.bd) set, or type your own list such as com, io, co.uk. Leave it empty to check the domain exactly as typed.
Results stream in as each registry answers. Green is available, red is taken, amber means no registry could give a straight answer.
A taken domain shows its registrar, creation and expiry dates, status codes and nameservers. An available one shows the registry and where to register it.
One name is crossed with every TLD you list, up to 240 lookups per search, run in parallel and paced per registry so nobody gets rate-limited.
Authoritative RDAP where a registry offers it, port-43 WHOIS with a per-registry availability table everywhere else, and an IANA referral when a server has moved.
A refused, throttled or unreadable response is reported as unknown with the reason, never silently rounded down to "available".
Registrar and IANA ID, created, updated and expiry dates, EPP status codes, nameservers, DNSSEC and the abuse contact, from RDAP or parsed from WHOIS.
Turn a username and password into an HTTP Basic Authentication header, curl command and fetch snippet, and decode existing Basic auth tokens back.
Paste a User-Agent string and read the browser, rendering engine, operating system, device type and CPU it describes, all in your browser.
Preview how your link will look on Facebook, X, LinkedIn, Slack, and Discord, validate your og: tags, and copy a correct meta block
Build, validate, and test a robots.txt file - user-agent groups, allow/disallow rules, sitemaps, AI crawler blocking, and a live URL tester
0 comments
No comments yet. Be the first to share your thoughts!