Skip to content

Drop catching .io at 4am: my week of failure and one weird win

Domain Names by HeadRich 24 replies 3.4K views
7 #1

So I burned $200 on backorders across three services for a four-letter .io that dropped last Tuesday. Zero hits. Nada.

The services: DropHawk ($79), SnapRegistry ($89), and some API thing I found on a Discord called Contabo Catch. Contabo won with €5 in API credits. I had €200 in play and lost to a script and pocket change.

My setup: Threadripper 3960X, 128GB RAM, 10Gbps at home. Thought maybe I could beat the API crowd by being close to the registry. Nope. The backorder services don't even hit the registry directly—they have agreements. My latency advantage meant nothing.

The weird win: I did catch a different LLL.io on Friday using Contabo's API. Cost me €3.47 in credits plus registration. Sold it yesterday for $800. But I'm still salty about the Tuesday loss.

Anyone actually understand .io drop timing? I watched the WHOIS and it went from serverHold to available in about 3 seconds. Backorder services claim they catch in milliseconds. How?

#2

Simple is better

Your home hardware does not matter against registry-side queues

#3

Prices only go up

.io is the new /24. Watched five drops this month. Backorder services caught four. The fifth went to API at 4:07am when everyone else timed out wrong

Your $200 bought you nothing but hope

#4

Contabo at 4:07am is just GitOps for domains

#5

In the March thread on ccTLD mechanics—the .io registry does not publish exact drop times. What we observe is:

  • ServerHold expires at 00:00 UTC nominally
  • Actual availability drifts 1-4 hours based on batch processing
  • Backorder services poll at 50-100ms intervals via EPP
  • API services use the same EPP but with custom retry logic

Your 10Gbps home connection is irrelevant because (1) you are not EPP-accredited and (2) the registry rate-limits unaccredited connections to 1 query/5 seconds. The backorder services have accreditations and persistent connections.

Contabo likely won because they detected the batch window shift. Your $200 services used static timing. The $5 API spent $3.47 on actual compute and pocketed the rest as margin.

I have a table of observed drift patterns by day-of-week if anyone wants. Tuesday drops averaged 2.7 hours late in Q3 2025.

#6

Thank you very much sir @WendyBird

I made script last month for check.io drop, used Contabo API also. Very cheap sir, made VPS at RackNerd for run it. Cost $4/month. Caught two domain already, sold one for $150. Still learning timing sir, your table will help very much

traffic worse than my packet loss
#7

I looked at Contabo and I cant find the catch service, only regular hosting? Is it separate account or something

Thank you everyone this thread is so helpful

learning on $5 VPS and prayers
#8
sarahjey said:
I looked at Contabo and I cant find the catch service, only regular hosting?

It is not a separate product page. You need an existing Contabo account with billing, then generate API keys from the customer panel. The catch endpoint is documented only in their community forum, not the main site. Search "domain catch API" in their German-language subforum and use a translator.

The €5 in credits comes from their standard API billing pool. No special signup.

#9

Found it thank you! The forum post is from 2022 but still works. Do I need a VPS with them or can I run from home

learning on $5 VPS and prayers
#10
JokoNord said:
RackNerd for run it. Cost $4/month

My Threadripper weeps. But you are right. The VPS location matters more than the silicon.

I ran mine from Dubai. Closest Contabo datacenter is Mumbai or Singapore. EPP to .io registry goes through London regardless. So my 10Gbps was routing through five hops of sadness.

The €3.47 win was from their Singapore zone. I checked logs later.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft