What a domain checker actually knows
8 min readUpdated
Type a domain into two different availability tools and you can get two different answers. That is not a bug in one of them. They are asking different questions.
Knowing which question was asked tells you how much to trust the answer — and whether you are about to design a brand around a name somebody already owns.
Three different questions
'Is this domain available' can mean any of three things, and they do not always agree.
| Question | How it is asked | What it misses |
|---|---|---|
| Does it resolve? | DNS lookup | Registered names with no server |
| Is it registered? | RDAP / WHOIS | Nothing, for .com |
| Can I buy it? | Registrar search | Nothing, but adds their pricing |
The gap in the first row is the one that hurts. It is also the fastest and cheapest check, which is why so many tools use it.
Why a DNS check misleads
DNS answers where a domain points. If nothing answers, the tempting conclusion is that nobody owns it.
But a large share of registered domains do not resolve at all:
- Investor-held names, registered and never configured.
- Defensive registrations — a company buying the misspellings of its own brand.
- Expired names in the redemption window, still owned, not yet released.
- Domains whose owner simply never pointed them anywhere.
Every one of those looks available to a DNS check. If your shortlist came from a tool that works this way, some of it is fiction.
RDAP is the authoritative answer
RDAP — Registration Data Access Protocol — is the modern replacement for WHOIS. You ask the registry that runs the extension, and it answers whether a registration record exists.
For .com that registry is Verisign, and its answer is definitive in a way no inference from DNS can be. There is no category of registered .com that RDAP fails to report.
The trade-off is cost. RDAP is slower than DNS and registries rate-limit it by IP, which is exactly why tools that check hundreds of names quickly are tempted to use DNS instead and hope.
The third answer: unknown
Availability tools usually offer two outcomes. Honest ones offer three.
Lookups fail. A registry times out, a rate limit trips, a resolver returns SERVFAIL. In that moment the tool does not know the answer, and it has a choice: guess, or say so.
Guessing 'available' is the damaging direction — it puts a name on your shortlist that may be owned. Guessing 'taken' quietly throws away names you could have had. Reporting 'unknown' is less satisfying and is the only answer that is true.
A checker that never says 'I do not know' is not more confident. It is less careful.
Why results expire
Availability is a snapshot, not a property. A name that was free when you checked can be registered before you finish reading the list.
This is rarer than domain folklore suggests. The idea that searching for a name causes somebody to register it — 'domain front-running' — has been investigated repeatedly and never demonstrated at reputable registries. What actually happens is ordinary: tens of thousands of .com registrations happen daily, and occasionally one collides with your shortlist.
The practical response is not paranoia. It is to do the checks that are not availability first, and then register the one you decided on promptly rather than sitting on a shortlist for three weeks — the order is here.
Registered, but on its way out
A domain does not go from owned to free the moment it expires. It moves through a fixed sequence, and for most of that sequence a checker correctly reports it as taken while the site it once pointed at has been dead for months.
| Stage | Roughly how long | Can you register it? |
|---|---|---|
| Registered and active | Until it expires | No |
| Expired, auto-renew grace | Up to 45 days | No — the owner can still renew |
| Redemption period | 30 days | No — only the owner can restore it, for a fee |
| Pending delete | 5 days | No, and nothing can stop the deletion |
| Released | — | Yes, the moment it drops |
So a name can sit in the taken column for two and a half months after the last person who cared about it stopped paying. Nothing you can do shortens that, and no checker can tell you the exact second it ends.
This is also why 'it expired last week' is not the good news it sounds like. Expired names that anybody wants are watched by drop-catching services with far better infrastructure than a browser tab, and the ones that quietly drop unnoticed are usually unnoticed for a reason.
Unregistered, and still not yours
There is a small category of names that no registration record exists for and that you cannot register anyway. A checker querying the registry sees no record and, unless it knows about these cases, reports them as free.
- Single-letter .com labels — a.com through z.com have been reserved since 1993, with a handful grandfathered in before the freeze.
- Strings reserved by standards for documentation and testing, such as example.com, and the .test and .invalid extensions. They exist so writing can use a domain without accidentally naming a real one.
- Names a registry has reserved for itself or is contractually required to withhold.
- Registry-premium names, which are genuinely unregistered but priced far above the ordinary rate — a price, not an owner. .com has no premium tier at all, which is why this only bites on other extensions.
None of this is common enough to worry about while generating candidates. It is worth knowing only so that an odd result at checkout reads as a category of name rather than as a broken tool.
Why a checker cannot answer a thousand names at once
Registries rate-limit registration lookups per source address, and they are entitled to: every query costs them something and returns data that used to be scraped wholesale. A tool checking a long list is therefore working against a ceiling it does not control.
There are three ways to handle that ceiling, and only one of them is honest.
- Check fewer names, in batches, pacing the requests — slower, and every answer means what it says.
- Switch to DNS for the bulk of the list and reserve the authoritative check for whatever survives — fast, and now some of the list is guesswork.
- Fire everything at once and treat every failure as available — fastest, and the results are worthless.
This is the reason a careful checker asks you to work through a shortlist rather than handing you a thousand green ticks. A tool that never seems to be limited by anything is not better engineered. It is answering a cheaper question.
The registrar's search is the final word — and a sales page
Whatever any tool told you, the registrar's own search is authoritative in the only sense that matters: it is the system that will take your money and create the record. Check there before you commit to anything.
But separate the answer from the page around it. The answer is a fact. The page is a shop, and it is designed to sell you something adjacent to what you asked for.
Read past the frame
- Alternatives on other extensions, shown because your .com was taken — a different name, not the one you searched.
- First-year prices next to renewal prices in smaller type. The renewal is the number you will pay every year after.
- Urgency language. Nobody else is looking at your invented name.
- Bundled privacy, hosting and email, pre-ticked more often than not.
Take the availability answer, ignore the merchandising, and decide on the name you actually came for.
Reading a result properly
- Available, from a registry check — trustworthy. Register it when you are ready.
- Available, from a tool that does not say how it checked — verify at a registrar before you commit anything.
- Taken — believe it. False negatives are rare in this direction.
- Unknown — check again later. It usually means a rate limit, not a registration.
And whatever the tool says, the registrar's own search is the final word, because that is the system that will actually take your money and create the record. If the answer keeps coming back taken, that is a naming problem rather than a searching one — changing the shape of what you look for is the way out.
In short
Resolving and registered are different questions. Anything that answers the first while claiming to answer the second will eventually cost you a name you had already fallen for.
Frequently asked questions
Why do two availability checkers disagree about the same domain?
- Usually because they asked different questions. One resolved the domain in DNS and found nothing, which only proves nobody has pointed it at a server. The other queried registration data and found an owner. Registered but unused is an extremely common state.
Does a parked page mean the domain is for sale?
- It means somebody owns it and has pointed it at a placeholder. Some of those placeholders carry an asking price, many do not, and an owner who has held a name for fifteen years may have no interest in selling at any price you would pay.
A domain expired months ago — why can I still not register it?
- Because expiry starts a sequence rather than ending one. The owner keeps a renewal window of up to 45 days, then a 30-day redemption period in which only they can restore it, then five days of pending deletion that nothing can interrupt. Only after that does the name become registrable, and a name anybody wants is usually caught within seconds of dropping.
Is a registry check as reliable for other extensions as it is for .com?
- Not always. Every gTLD registry publishes registration data over RDAP, so .com, .io and the newer extensions answer definitively. Some country-code registries expose limited data, rate-limit aggressively, or answer only through a web form — which is exactly where tools quietly fall back to a DNS lookup and start guessing.
How long is an availability result good for?
- It is accurate at the moment of the check and no longer. Domains are registered continuously, so a result from an hour ago is history rather than a reservation. Nothing about seeing a name marked free holds it for you.
Sources
- ICANN Lookup — registration data for a domain
- ICANN — About domain names
- ICANN — Life cycle of a gTLD registration
- ICANN — EPP status codes, and what each one means
- RFC 2606 — reserved top-level DNS names
- IANA — the RDAP bootstrap registry for DNS
These support factual background only. The guide itself is original writing, and nothing here should be read as legal advice.
Related guides
Domain Names
Every good .com is taken. Here is what actually works.
Roughly every dictionary word is registered. The way out is not a cleverer search — it is changing the shape of what you search for.
12 min read
Domain Names
From shortlist to registered, without regret
What to check between finding an available name and paying for it: the spoken tests, the searches, trademarks, handles, history, and the settings that matter at checkout.
9 min read
Domain Names
.com vs .io vs .ai vs .co: which should you choose?
What each extension actually is, what it costs to renew, which ones hide premium pricing, and when a shorter name on .com beats a perfect name elsewhere.
10 min read
Domain Names
The domain you want is taken. Now what?
Taken means six different things, and each one has a different answer. How to find out which you are facing, then choose between buying it, renaming, and walking away.
9 min read