.com drop order

[B Klug]

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.

 

[Jurgen Wolf]

Regarding Gandi...
If I recall correctly - the domain push is absent there... only transfer-out is possible.

 

[Jurgen Wolf]

p.s. With API even in smart hands - you can beat GoDaddy backorder only.

 

[wayne wooldridge]

I agree. Using api namesilo seemed to outperform other registrars. Even still, expect some timeouts during drops time.

 

[B Klug]

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

 

[Dandelion]

I am trying to figure the use of these timing. Are you trying to catch domain drops manually?

 

[wayne wooldridge]

I am trying to figure the use of these timing. Are you trying to catch domain drops manually?

Knowing the specific time of each drop makes dropcatching more effective, especially if you're going after a batch of pending delete domains.

It doesn't help for names that are heavily targeted by backorder services. However if you are only competing against others using registrar api calls you will achieve better efficiency by only sending api calls for 1 domain at a time.

So for example, if you have a list of 10 domains you want to catch, you would normally just start cycling through each domain at once when the droptime begins. You are wasting precious resources and time by blindly trying each one.

Now say you know the order of the drop and approximate time each will drop. You will only be targeting 1 domain at any given time until it is registered and then rest until the next domain drop time approaches, so on and so forth.

Hope this helps.

 

[Dom Catcher]

@Brian Klug - Did you get a list before yesterdays drops? I recently tried to catch a valuable domain that has a previous high sale against it so thought it would be worth giving it a short whilst also baring in mind that dropcatch/snapnames/namebright are going to be hammering requests over in order to secure it.

I have built a system that has been showing half decent results for realistic names (Some single keyword and single word .coms have been caught but just under 30% at the moment as get beat by the bigshots with direct access.. so still working on it)

Can you share what your list said prior to yesterdays drop and compare that to the actual time's registered? Im happy to send you the domain im curious about via PM.

Recently i had several systems in place and i wasn't even able to detect the drop for "a specific domain" which to me says one of two things:-

Verisign block's all other requests for valuable domains apart from the ones requests from Dropcatch accounts

OR: Dropcatch was sending thousands of requests per second from all of their accounts which in theory is legit because 1000 miliseconds / second and they have over 2000+ accounts therefore they can send at least 2 requests / every millisecond from each account and avoid any quota or limitations (They probably dont have limits anyway due to their investment into all their accounts )

I wont say how or what domain but i know for certain that more than 200 requests per second was reaching verisign (between a narrowed down 4 minute window) to register a domain name a few days ago that again was not even detected to drop and was suddenly assigned to dropcatch - Seems fishy?.

 

[davidc1]

optimizing api catching is only suitable if your competitors are using api.

If by the end you see that all domains are taken by snapnames or dropcatch you dont need to optimize anything...

 

[Jurgen Wolf]

2000+ accounts???
Who said this non-sense???

Limit is set per accredited registrar...
2000+ registrars under DropCatch or what???

Those backorder services have no more than 100 registrars in the best scenario.
Also they know the exact deletion time directly from Verisign.

 

[Jurgen Wolf]

And tons of such registrars were deaccredited by ICANN recently.

 

[Dom Catcher]

@Jurgen Wolf i beg to differ, they have far more? or maybe i'm wrong but ive been doing plenty of research into dropcatch, namebright, snapnames, networksolutions and web group.

Regarding the exact deletion time, this is received how? Inside knowledge or via epp info commands or a simple whois history log?

I don't have direct access to Verisign at the moment hence my question as im lacking the knowledge to what Verisign makes public via there interfaces.

 

[Jurgen Wolf]

Pheenix had mid xx registrars...
SnapNames/Namejet no more than 1xx cumulatively.
And this was in the past, prior the mass termination of such registrars by ICANN.

 

[Jurgen Wolf]

Regarding Verisign...
This information is not public... it is provided to a few major backorder services only.

 

[Dom Catcher]

This is old news or no longer true? domainincite.com/21309-dropcatch-spends-millions-to-buy-five-hundred-more-registrars

Also what about all the subtags dropcatch have like Dropcatch_1506 ... Dropcatch_1222 ... Dropcatch_xxxx

 

[Jurgen Wolf]

It is really old... 2016...
Most of them were terminated.

 

[Jurgen Wolf]

You may google it...
Just 1 link: http://domainincite.com/22261-icann-terminates-450-drop-catch-registrars

 

[Dom Catcher]

When was they terminated? This thread: namepros.com/threads/beating-dropcatch-com-possible.1086384/ has posts from last year stating Dropcatch still have around 750 registrar accounts.

Even if they had a hundred's, combined with the "non public info" you said is passed on from Verisign, that yields very little chance for any other player thus passes majority if the Monopoly to Dropcatch.

How does icann sit back and allow it to happen? I am sure Verisign are favouring certain companies based on finances - lets be honest, Verisign don't have the best track record with icann.

 

[Jurgen Wolf]

At the end of 2017 and in 2018...

 

[Jurgen Wolf]

And finally, you may contact ICANN directly... or try to find on their website how many DropCatch* registrars are active (still accredited) as of today...
But definitely not 2000+ what you said initially.

 

[Jurgen Wolf]

All are here: https://www.icann.org/registrar-reports/accredited-list.html
Count them...