The anatomy of a 280-millisecond catch
When an expired domain is released, the winner is decided faster than you can blink. Here's exactly what happens inside Auto DropCatch in the quarter-second that matters.
Every dropped domain has a single moment of truth: the instant the registry releases the name back into the available pool. Whoever lands a valid registration request first wins. Not the highest bidder, not the earliest to queue — the fastest packet. Everything Auto DropCatch does is in service of being that packet.
The race is shorter than a heartbeat
Registry release windows are unannounced down to the second, and the gap between "taken" and "available" can close again within a few hundred milliseconds as competing catchers pile in. We measured our median end-to-end catch at 280ms from release detection to confirmed registration. The slowest 5% still came in under 600ms.
Pre-warming is the whole game
You cannot open a TLS connection, authenticate, and serialize a registration request after you detect the drop — that's already too late. Auto DropCatch keeps persistent, authenticated sockets open to all eight registrar APIs and pre-builds the request payloads. The moment release is detected, we're not connecting; we're just flushing bytes that are already staged.
- Persistent keep-alive sockets to every registrar
- Pre-signed, pre-serialized registration payloads
- Clock sync against registry NTP to predict the window
- Parallel fire — all eight APIs, not sequential fallback
Why eight registrars and not one
Each registrar has its own connection to the registry, its own rate limits, and its own millisecond-level quirks under load. Firing through all eight in parallel turns a single coin-flip into eight simultaneous attempts. The first success wins; the rest are harmlessly discarded. It's the single biggest lever on catch rate we've found.
“We stopped thinking about catching as a request and started thinking about it as a starting gun. The work happens before the trigger, not after.”
What you actually do
Nothing, in the moment. You add the domain to a watchlist, optionally arm auto-catching, and Auto DropCatch handles the millisecond choreography. The first you'll hear of it is a confirmation that the name is in your account — usually before you've finished your coffee.