Dynadot

.com drop order

Spaceship Spaceship
Watch

B Klug

Established Member
Impact
88
This site says "This unique feature takes your list of COM/NET domains and arranges them into their exact drop order. DesktopCatcher will take your domains and check them to see which one will drop first, second..etc. Once in order, this thread will put all of its focus on just one domain at a time. So, rather than cycling through your entire list of domains, it only tries to register the first domain which is suppose to drop. Once that domain has dropped and been registered (by you or someone else), it will then move onto the second domain, and so on"

How does one know the order a .com drops? (I'm not talking about the day, I'm talking about the time).

I know .coms drop between 11am and noon or so (pacific time) each day, but the above linked site claims their software knows what order domains drop in.

That would be helpful to not waste API calls and focus on the proper domain in question.
 
0
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
Would you be interested by a service to know the drop order of a list of domains ?
 
Last edited:
0
•••
Paid service? No, because I suspect it can be deduced from publicly available information, possibly whois data. Maybe they drop, for example, by order of "last update" date. (Just a guess, I have no idea what the order is.)

But yeah, If I knew what the rule was, I could build such a service.
 
0
•••
1
•••
Funny. I had just ordered today's drops by update time just to see if my theory was right. Good guess! Thank you for confirmation.
 
0
•••
Sure enough, the domains dropped in order of their updated time.

"But wait, there's more."

If you add exactly 140 hours to the updated time (5 days 20 hours) and you look at the time (18:02 is 11:02 AM Pacific time), then compare the actual registered time of the drop caught name, you can see a rough pattern emerge.

For today's drop (guessing this might change day by day) it took rough 2.5 times the number of minutes in the updates time to drop the name. For example if a .com was last updated at 10 minutes after the hour, it would drop approximately 10*2.5 = 25 minutes after 11am.

domain updated plus 140hours seconds after registered at seconds after difference seconds ratio
icestar.com 2019-05-17 18:02:31 151 2019-05-17 18:05:48 348 197 2.3046
rivz.com 2019-05-17 18:14:55 895 2019-05-17 18:37:24 2244 1349 2.5073
opposure.com 2019-05-17 18:15:29 929 2019-05-17 18:38:57 2337 1408 2.5156
peladic.com 2019-05-17 18:16:26 986 2019-05-17 18:41:17 2477 1491 2.5122
sparassis.com 2019-05-17 18:18:12 1092 2019-05-17 18:45:36 2736 1644 2.5055
zeekeo.com 2019-05-17 18:18:39 1119 2019-05-17 18:46:46 2806 1687 2.5076
kozna.com 2019-05-17 18:20:22 1222 2019-05-17 18:51:40 3100 1878 2.5368

(I ended up catching 4 of the names above FWIW.)
 
Last edited:
7
•••
From my sources, they are processed by registrar order... at least such scheme was in the past.
Verisign deletes all domains of the registrar1, then all inventory of 2nd registar and so on...
How registrars are sorted in Verisign list - I don't know.
Updated Date/Time doesn't matter.

Also various backorder services have the exact time of deletion directly from Verisign.
They don't calculate anything.
 
Last edited:
1
•••
In other words, backorder platforms like SnapNames don't DDoS Verisign to catch the domains...
They know the exact time.
 
0
•••
Jurgen: what you say may be 100% correct -- while at the same time ALSO matching this working theory. They might do it by registrar -- and they might also put them into pendingDelete status by registrar too - which means the last update time would be in order just like we are talking about.

(This theory could be wrong, but the pattern today would be one heck of a coincidence. The odds of 7 domains dropping in any particular order is 1 in 5040 (7 factorial). The odds of them falling nicely into my minute formula like the did much greater.)
 
1
•••
DesktopCatcher is not even needed.
This can be done on Linux just via 1 command in terminal... also you may insert 1 or more seconds pause between API calls...
API for .com drops is good only to beat handregs or another API users... its efficiency against backorders is ~0.00%
 
Last edited:
1
•••
Absolutely. I was only on DesktopCatcher's website to see what APIs they were using. I have built my own personal dropcatching service. Right now it uses APIs from multiple companies all at the same time. Currently, NameSilo, Dynadot, AJM and OpenProvider. Adding Gandi and Name Bay tomorrow.

I have spoken with reps at all of them to understand what the max responsible API usage looks like. They all have different answers. NameSilo allows 2 requests per second. Dynadot has no limit but only allows 1 call at a time (effectively, 1 every 10 seconds since that is how long API calls take during the drop). And so on.

Am using a dozen custom scripts to drop catch with my own admin interface. Today it caught 4 of the 7 names I wanted. (To be realistic, my code would still have to be lucky in order to catch super high value names, since Dropcatch owns 49% of all registrars (!).)
 
1
•••
AJM ???
This is just PDR/Endurance (ResellerClub)... or LogicBoxes platform in other words.
LogicBoxes limit, if I recall correctly, just high XXX API calls per 10 min - then red flag and ban.
 
0
•••
0
•••
LogicBoxes - former brand of Directi (one of the largest Asian companies, based in India).
Few years ago it was sold to Endurance (also Indian company).
 
Last edited:
0
•••
LB API is slow in terms of processing and its implementation... even regardless of their limit.
Don't waste your time.
It is suitable for non-.com TLDs only.
 
1
•••
Very good to know. Thank you! Do you use APIs to drop catch as well? What APIs have worked well for you? Every gotten a 4L .com or other high value name that way?
 
0
•••
Regarding @Dynadot
The most bottleneck there - their algorithm which depends on your $$$ volume during the last 365 days and how many API calls you did for the previous day... Using this formula they rank you among other API users.
 
Last edited:
0
•••
Regarding 4L.COM
Forget... it is impossible to catch it via API since 2010 or so... backorder only.

p.s. Yes, I have the long API experience...
But I usually use it for non-.com domains only.
 
Last edited:
0
•••
@namesilo looks the most optimal...
Just your own speed matters... no any other algorithms.
 
Last edited:
0
•••
Use Dynadot + NameSilo = this should be enough.
 
0
•••
Regarding Gandi...
If I recall correctly - the domain push is absent there... only transfer-out is possible.
 
0
•••
p.s. With API even in smart hands - you can beat GoDaddy backorder only.
 
Last edited:
2
•••
I agree. Using api namesilo seemed to outperform other registrars. Even still, expect some timeouts during drops time.
 
2
•••
Today's drop.

Again, they followed the order exactly of update time exactly. Odds of 8 items being in any certain order is 1 in 40,320.

And they followed a similar pattern with timing, although today's magic ratio was closer to 2.45 vs yesterday's 2.5. And again the earlier names had lower ratio.

This is enough to predict to minute level, but not second level, drop time.


domain updated_plus_140hours registered_at ratio
copyprinter.com 2019-05-18 18:01:51 2019-05-18 18:03:52 2.0901
asurl.com 2019-05-18 18:14:23 2019-05-18 18:34:18 2.3847
uglyfuck.com 2019-05-18 18:16:12 2019-05-18 18:39:23 2.4311
hantey.com 2019-05-18 18:19:26 2019-05-18 18:47:27 2.4417
wherehow.com 2019-05-18 18:20:11 2019-05-18 18:48:58 2.4261
sporters.com 2019-05-18 18:21:45 2019-05-18 18:53:23 2.4544
maoe.com 2019-05-18 18:23:16 2019-05-18 18:57:21 2.4649
paykin.com 2019-05-18 18:24:08 2019-05-18 18:59:42 2.4738
 
6
•••
I am trying to figure the use of these timing. Are you trying to catch domain drops manually?
 
0
•••
Back