Sometimes you get an alert that a domain is available, try to register it, and find it is already taken. Sometimes a domain's status appears to change back and forth. Both come from the same underlying fact: the public registry data you can read is not the registry's own database, and the gap between them is where these surprises live.
Why an available domain can already be gone
1. The drop-catching industry
The most common reason. Drop catchers are automated services built to register valuable expired domains the instant they are released. They hold high-speed connections to the registries and execute a registration in milliseconds. Even with a fast alert, a human at a normal registrar rarely wins that race.
2. Registry-premium domains
When some domains expire, the registry reclassifies them as premium rather than releasing them to the general pool, and sells them at a much higher price. The name is genuinely no longer registered, so it reads as available, but it is not available at standard prices.
3. Propagation delay between the check and your attempt
There is a delay between a registration happening and the public WHOIS and RDAP servers reflecting it. Somebody may have registered the name in the seconds between our check and yours.
What you can do
- Be ready. When the alert arrives, register immediately, from an account you are already logged into.
- Use a drop catcher for contested names. For a domain you expect heavy competition on, a professional backorder service is the realistic route. Domainyze tells you which names are worth backordering and when.
- Consider alternatives. If you consistently lose a name, an alternative extension or variation may be the better outcome.
Why a status sometimes flaps back and forth
Less often, you may see a domain's status change rapidly between two states, or show conflicting information between checks. The causes:
1. Inconsistent propagation
Domain data is spread across registrar, registry and WHOIS/RDAP servers, and updates do not reach all of them at once. Consecutive checks that reach different servers can see different answers.
2. Registry glitches or maintenance
Registries have outages, synchronisation lag and maintenance windows, any of which can produce inconsistent responses for a short period.
3. Race conditions at the drop
On a contested name, the moment of release triggers a race. You can genuinely see available, then registered by a drop catcher, then briefly available again if that registration fails to complete.
4. Aggressive caching
Some WHOIS and RDAP endpoints cache responses. Domainyze queries authoritative sources where it can, but intermediate caching still happens.
What Domainyze does about it
- An ambiguous read is not an answer. A timeout, a rate-limited registry or an unparseable response is recorded as a failed check. It is never reported as availability, because a false available alert costs you a wasted registration attempt at the worst possible moment.
- A drop is corroborated before it is announced. A newly-seen availability is re-confirmed before it becomes an alert.
- Everything is logged. Every detected change is kept in the domain's history, so you can see exactly what was observed and when.
If you see persistent or inexplicable flapping on a domain that matters, contact support with the name and what you observed.