Drop-catching
Drop-Catching Notes from the Backorder Queue
What actually gets caught, what gets missed, and why
Posted 14 March · 9 min read · 41 replies in the drop-catching board
I ran backorders on both sides of the queue for most of last season, mostly .co.za drops with a smaller set of .com names I had been watching since they lapsed. The log is not scientific, but it is long enough to see which assumptions held and which ones fell apart the moment two services went after the same name.
Short names are not automatically safe. Two-letter and three-letter .co.za drops were caught almost every time, but a handful of four-letter combinations sat unclaimed for days because the letters read as noise rather than a word. Length matters less than whether someone can say the name out loud without spelling it.
Keyword type split the results more cleanly than anything else. Names built on a trade or a place, like plumbing or a suburb, drew multiple backorders and cleared fast. Abstract strings with no obvious buyer sat in the queue and eventually dropped back into the open pool, where they stayed.
Competing services behave differently on the same drop. When two backorder providers both hold a claim, the one with the earlier timestamp usually wins, but registrars vary in how quickly they release the name, so a later claim can still take it if the first attempt fails on a technicality. Members who lost a name this way tend to post the registrar and the exact minute, which is more useful than a complaint.
When someone else catches the name you wanted, the practical move is to note who holds it and wait. A fair share of caught names reappear in the marketplace within a few months, often at a number the catcher is willing to discuss. Reaching out immediately rarely helps.
For beginners: expect most of your first backorders to miss. Pick names you would actually keep, log every result with the registrar and time, and read the drop-catching board before adding a second service to the same name.