How to Check If a Domain Is Available (and What 'Available' Really Means)

Type a name into any registrar's search box and you get a confident green tick or a red cross. It feels like a lookup against a definitive list. It mostly is — but the answer is less binary than the interface suggests, and in a few cases the tick is simply wrong.

Here's how availability actually works, and what to check before you get attached to a name.

Where the real answer lives

Every domain registration ultimately sits in a registry — the organisation that runs a TLD. Verisign runs .com and .net, Public Interest Registry runs .org, Nominet runs .uk. Registrars like GoDaddy or Namecheap sell to you, but they're resellers writing into the registry's database.

So the authoritative answer to "is this taken?" comes from the registry, and most publish it openly through RDAP — the structured successor to WHOIS. Ask the registry's RDAP server about a domain and you get one of two useful answers: a registration record, or a 404 meaning no such registration exists.

That's what our free domain availability checker does. It resolves each TLD's authoritative RDAP server and asks the registry directly, so the answer isn't filtered through anyone with something to sell. How to read a WHOIS record covers what's in the response when a domain is registered.

The TLDs nobody can check reliably

Here's something most availability tools won't tell you: some popular TLDs have no public RDAP service at all.

.io, .co, .me, .es, .de and .eu are among them. They're absent from IANA's RDAP bootstrap registry, which means there's no authoritative endpoint to query.

That matters more than it sounds, because of how tools fail here. Query one of these through a generic RDAP redirector and it returns "not found" — the same response an unregistered domain produces. We tested this: github.io, unmistakably registered, came back as not found. A checker that trusts that response will tell you a taken domain is free.

Our tool leaves those TLDs out entirely and says so, rather than showing an answer that might be wrong. If you're set on a .io or .co, check it at a registrar and confirm before making plans — and treat any tool that cheerfully reports on them with suspicion, because it's either using private registry access or guessing.

For TLDs without RDAP there's still a rough signal: if the domain resolves in DNS, it's definitely registered. The reverse doesn't hold — plenty of registered domains have no DNS records at all — so it can prove taken but never available.

Four reasons "available" still isn't yours

An unregistered domain isn't automatically a domain you can buy at the price you expect.

1. Premium pricing. Registries reserve dictionary words, short names and obviously commercial terms, and sell them at multiples of the standard rate — sometimes thousands. The registry has no registration on file, so it reports as available, and you find out at checkout. Newer TLDs do this most aggressively.

2. Registry reserved names. Every registry holds back a list: single characters, two-letter combinations, geographic and government terms, its own operational names. These are unregistered and unregisterable.

3. Eligibility rules. Plenty of TLDs restrict who may register. Some ccTLDs require local presence or a national ID; .edu and .gov are tightly controlled; some industry TLDs need credentials. Available to someone isn't available to you.

4. Trademark. Nothing in DNS checks whether a name belongs to someone else in the legal sense. A domain can be free to register and still land you in a UDRP dispute. If the name is close to an existing brand, that's worth checking before building on it.

None of this makes availability checks useless — it makes them the first step rather than the last.

Does searching put a name at risk?

A persistent worry: search for a name, come back later, find it registered by someone else. Domain front-running — where a party uses knowledge of searches to register names speculatively — has been alleged against registrars and resellers over the years, and ICANN has looked into the practice.

Whether it still happens meaningfully is genuinely hard to prove; it's the kind of claim that's easy to assert after a coincidence and hard to demonstrate. What's reasonable is to reduce the surface anyway:

• Check somewhere that doesn't sell domains. Our tool doesn't register anything and reserves nothing — there's no commercial reason for the search to go anywhere.
• Don't shop around with the same name across five registrar search boxes over two weeks.
• If you're sure, register it. A .com costs roughly a coffee. Deliberating for a fortnight over a name you know you want is the more expensive risk.

Picking which TLD to actually take

Once you know what's free, the choice is mostly about signalling:

• .com still carries default trust and is what people type from memory. If it's available and affordable, it's usually the safe answer.
• .dev, .app and .ai read as credible to technical audiences. Note that .dev and .app are on the HSTS preload list, so HTTPS is mandatory — not a burden today, but it means a certificate is non-negotiable from day one.
• ccTLDs signal a market. Excellent when you serve one country, limiting when you don't, and often subject to eligibility rules.
• Newer generic TLDs (.xyz, .site, .store, .tech) are cheap and available where .com isn't. Watch renewal pricing — first-year promotions and later renewal rates can differ sharply.

A common pattern is to take the .com plus one or two defensively, and redirect the extras. Just remember each one is a separate registration with its own renewal date — which is exactly how portfolios quietly grow past the point anyone tracks them.

The clock starts the moment you register

The day you buy it, a domain becomes something that can lapse. And the failure mode is nastier than people expect: you don't get a warning page, you get a name that stops resolving — site, email, everything — followed by grace and redemption windows with restoration fees, and eventually the possibility of someone else taking it (what happens when a domain expires).

Auto-renew is the obvious answer and it's not sufficient on its own, because it's only an instruction to attempt a charge — against a card that will itself expire on an unrelated schedule (why auto-renew fails).

So: check availability at the registry, buy from whichever registrar you like, then track the renewal date somewhere that isn't the registrar's inbox. DomainChest watches domain and certificate expiry across every registrar you use and emails you well before either lapses — free for three domains.

Start with the availability checker to see what's free, and the domain & SSL expiry checker once you own it.