Home / Domain name search
Domain name search
Search once, get an answer you can act on.
Why two domain searches can disagree
Run the same name through three different search boxes and you can get three different answers. This is not a bug in any of them — it is a consequence of where each one gets its data.
| Source | What it actually knows | Lag |
|---|---|---|
| Registry RDAP or WHOIS | The authoritative record | None |
| Cached zone file | What was registered at last snapshot | Hours to days |
| Reseller inventory | What that reseller can sell you | Varies |
| DNS lookup alone | Whether the domain resolves | Misses parked names |
A domain registered an hour ago is already taken in the registry, but may still look available in a zone-file cache until the next snapshot. DotSeeka asks the registry.
What each result means
| Result | What the check found | What to do |
|---|---|---|
| Available | No registry record, and no DNS resolution | Register it — but check trademarks first |
| Taken | A registry record exists, or the name resolves | Try a variation, or look into acquiring it |
| Unknown | The registry did not give a reliable answer | Re-run it; registries rate-limit under load |
The DNS cross-check
Some registries answer 404 for names they do not manage rather than for names that are free. Nominet does this for third-level .uk names, which would otherwise read as available. Every available verdict is therefore cross-checked against DNS: if the domain resolves, it is reported taken.
This is why ox.ac.uk correctly comes back as taken here, while a naive RDAP-only check would report it free.
What you can type
A bare keyword becomes a .com. A full domain is checked as written. A name followed by .* expands across every common ending. URLs and email addresses are reduced to their domain, so pasting a link works without editing it first.