Why not show unverified names with a warning?
Because a label next to a name is read as a detail, and the word “available” is read as a fact. In testing the warning loses. Hiding is unambiguous.
Unverified means the registry didn’t give a clear answer about a name. It is not a synonym for free, and it is not a synonym for taken. Webault hides those names rather than showing them as available, because a hidden free name costs you nothing and a fake free name costs you an afternoon.
Unverified means Webault asked the registry about a name and did not get an answer it can rely on. The name might be free. It might be registered. The lookup didn’t settle it, so the status records that rather than pretending otherwise.
The first three are transient. The fourth is structural, and it is why some extensions aren’t in the 532 at all.
Because the two mistakes are not the same size.
Hide a name that turns out to be free, and you never learn about a name you might have liked. That is a real cost, and it is invisible and painless.
Show a registered name as free, and someone builds a shortlist on it, presents it to a client, sketches a logo, and finds out at checkout. That cost is concrete, and it lands at the worst possible moment — which is exactly how studios lose a name a client already approved.
Any tool that sells domains faces this trade with a thumb on the scale, because a hidden name is a lost sale. Webault doesn’t sell domains, so hiding costs it nothing, which is the whole reason the strict choice is available to us. The full check explains where the three statuses come from.
Unverified means the registry did not answer clearly, so Webault will not call the name free. Hiding a name that might be available is a smaller failure than presenting a registered name as available.
Unverified names are counted but never listed as free. Running the round again re-checks them, because the cause is usually temporary.
Because a label next to a name is read as a detail, and the word “available” is read as a fact. In testing the warning loses. Hiding is unambiguous.
It depends almost entirely on the extension. Generic extensions on RDAP answer clearly the overwhelming majority of the time; some country-code registries are far less consistent.
Yes. Run the round again. Timeouts and rate limits are transient, so a second pass usually resolves them.
By YBM Labs. Last reviewed . Terms used here are defined in the glossary.