The ENOM Reseller API Is Blocking Drop Catching Activity

Since I developed some effective drop catching software for the ENOM Reseller (API) Program, it has come to my attention that ENOM is now rejecting API calls to their reseller API during the drop window. If that isn’t odd enough, they actually enforce the API ban for about 4 hours total (1pm – 5PM CST).

It seems to me like they are checking the whois of each domain that is processed via their API. During the ban, their API works fine for any domain that is not in “pending delete” status – But flat out fails to grab any dropping domain. This “change” has come about over the past few days – 1 week’s time.

Perhaps this is a temporary bug? Or permanent? I am not sure, but all I know is that ENOM which was once the drop catcher’s #1 API reseller program – has cut the cord on drop catching activity. I guess drop catchers will need to find other sources and API’s to use for their daily drop catching.

This will really hurt enom. This issue was reported to me by drop catchers that catch between 30-50 domains a day. So it will greatly impact the market from sharks to the sardines.

I have yet to test & find out if this API issue also applies to the CCTld drops. I believe it has only impaired the .com & .net drop catching connections.

More to follow as I get some answers from ENOM.