IT.COM

The HugeDomains bot and GoDaddy Auctions

NameSilo
Watch

How to verify the bidder during the auction process?

  • This poll is still running and the standings may change.
  • Set their public homepage to show the domains that have been won and are being bid.

    vote
    16.7%
  • Non-robot verification for each bid

    votes
    50.0%
  • Limit the number of simultaneous bids

    votes
    33.3%
  • others

    votes
    0.0%
  • This poll is still running and the standings may change.

Kai W.

CollectorTop Member
Impact
692
Auctions are an important way, and my experience tells me that this is not just happening in GD. Everyone here will benefit as a seller. But I know very well that the presence of robots will limit the number of sales in this industry (obviously, the average transaction price of a cheap domain will be higher than its market value).
Is there a mechanism similar to WHOIS protection to provide a perfect solution for the auction?

Read the original
 
0
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
I'm somewhat relaxed about robots. At the end of the day, no one is forced to pay more than they want to. If you know your max price, whether you're bidding against people or robots makes no real difference in my mind.

I mean, if I set my max bid as xxx and rely on the platform to increase my bids for me, there's not much difference between that and a robot anyway.
 
3
•••
I'm somewhat relaxed about robots. At the end of the day, no one is forced to pay more than they want to.

Your approach is correct.
There are few cases where it is based on love, not budget. Because there are many valuable domain names underestimated by GDV.
 
0
•••
At this point I don't think HD is even using an api, I think it's somehow built into the system. Consider this auction from the moment ago:

Bidder 1 (Auto)
2/1/2020 9:52 PM $54
+$5

Your bid
2/1/2020 9:52 PM $49
+$7

Bidder 1 (Auto)
2/1/2020 9:52 PM $42
+$5

Bidder 2
2/1/2020 9:51 PM $37
+$5

Your bid
2/1/2020 9:51 PM $32
+$5

Bidder 2
2/1/2020 9:50 PM $27
+$5

Your bid
2/1/2020 9:50 PM $22

Bidder 2
2/1/2020 9:50 PM $22
+$5

Your bid (Auto)
2/1/2020 9:50 PM $17
+$5

Bidder 2
2/1/2020 9:48 PM $12

The auction was originally scheduled to end at 9:50 PM. One bidder made an offer at 9:48 and they are shown as Bidder 2(!). I made an offer at 9:50 and we were bidding for a while. Then, at 9:52(!), all of a sudden a "Bidder 1" jumps in! Which, of course, turns out to be "Bidder 913932" after the auction ends. Now, answer this, how did they do it "through an api"? The system had to have their offer "on hold" to be "released" when there is someone else already bidding. That's the only explanation (I can think of) why they are "Bidder 1".

So taken all that, here's what I currently believe. HD processes the list of GD expired auctions, assigns a value to each domain and then queue a proxy bid for this value (to be used in case of someone bidding on the auction) or snap the domain between the auction and the closure. So the bright side is, it doesn't matter if you bid on the auction or try to snap it at the closure - if they have the name queued, they will get it anyway (unless you're willing to outbid them). On the other hand, if they don't have the name queued, they won't bid on it anyway, so the only "bad" thing about bidding might be attracting other domainers to the auction, but for HD bot it's probably meaningless.

Attached are some screenshots as a proof for the above paste.
 

Attachments

  • ffs-bid-bottom.png
    ffs-bid-bottom.png
    17 KB · Views: 287
  • ffs-bid-top.png
    ffs-bid-top.png
    16.3 KB · Views: 301
  • ffs-bid-top-after.png
    ffs-bid-top-after.png
    18.5 KB · Views: 276
2
•••
At this point I don't think HD is even using an api, I think it's somehow built into the system. Consider this auction from the moment ago:

Bidder 1 (Auto)
2/1/2020 9:52 PM $54
+$5

Your bid
2/1/2020 9:52 PM $49
+$7

Bidder 1 (Auto)
2/1/2020 9:52 PM $42
+$5

Bidder 2
2/1/2020 9:51 PM $37
+$5

Your bid
2/1/2020 9:51 PM $32
+$5

Bidder 2
2/1/2020 9:50 PM $27
+$5

Your bid
2/1/2020 9:50 PM $22

Bidder 2
2/1/2020 9:50 PM $22
+$5

Your bid (Auto)
2/1/2020 9:50 PM $17
+$5

Bidder 2
2/1/2020 9:48 PM $12

The auction was originally scheduled to end at 9:50 PM. One bidder made an offer at 9:48 and they are shown as Bidder 2(!). I made an offer at 9:50 and we were bidding for a while. Then, at 9:52(!), all of a sudden a "Bidder 1" jumps in! Which, of course, turns out to be "Bidder 913932" after the auction ends. Now, answer this, how did they do it "through an api"? The system had to have their offer "on hold" to be "released" when there is someone else already bidding. That's the only explanation (I can think of) why they are "Bidder 1".

So taken all that, here's what I currently believe. HD processes the list of GD expired auctions, assigns a value to each domain and then queue a proxy bid for this value (to be used in case of someone bidding on the auction) or snap the domain between the auction and the closure. So the bright side is, it doesn't matter if you bid on the auction or try to snap it at the closure - if they have the name queued, they will get it anyway (unless you're willing to outbid them). On the other hand, if they don't have the name queued, they won't bid on it anyway, so the only "bad" thing about bidding might be attracting other domainers to the auction, but for HD bot it's probably meaningless.

Attached are some screenshots as a proof for the above paste.
I honestly don't like to bid much unless if I want to cost you money for placing a bid.
 
Last edited:
1
•••
I honestly don't bid much unless if I want to cost you money for placing a bid. I truly believe I have being beating hugedomains at well either they have it on their list or not. I haven't lost a name for about 2 month once it goes to closeouts. So, this notion they can get it if it is on their list is incorrect...invest in developing an application...
What programming language do you think is better for such app?
 
1
•••
I honestly don't bid much unless if I want to cost you money for placing a bid. I truly believe I have being beating hugedomains at well either they have it on their list or not. I haven't lost a name for about 2 month once it goes to closeouts. So, this notion they can get it if it is on their list is incorrect...invest in developing an application...

Do you have the api access?
 
1
•••
.net
 
Last edited:
2
•••
1
•••
At this point I don't think HD is even using an api, I think it's somehow built into the system. Consider this auction from the moment ago:

Bidder 1 (Auto)
2/1/2020 9:52 PM $54
+$5

Your bid
2/1/2020 9:52 PM $49
+$7

Bidder 1 (Auto)
2/1/2020 9:52 PM $42
+$5

Bidder 2
2/1/2020 9:51 PM $37
+$5

Your bid
2/1/2020 9:51 PM $32
+$5

Bidder 2
2/1/2020 9:50 PM $27
+$5

Your bid
2/1/2020 9:50 PM $22

Bidder 2
2/1/2020 9:50 PM $22
+$5

Your bid (Auto)
2/1/2020 9:50 PM $17
+$5

Bidder 2
2/1/2020 9:48 PM $12

The auction was originally scheduled to end at 9:50 PM. One bidder made an offer at 9:48 and they are shown as Bidder 2(!). I made an offer at 9:50 and we were bidding for a while. Then, at 9:52(!), all of a sudden a "Bidder 1" jumps in! Which, of course, turns out to be "Bidder 913932" after the auction ends. Now, answer this, how did they do it "through an api"? The system had to have their offer "on hold" to be "released" when there is someone else already bidding. That's the only explanation (I can think of) why they are "Bidder 1".

So taken all that, here's what I currently believe. HD processes the list of GD expired auctions, assigns a value to each domain and then queue a proxy bid for this value (to be used in case of someone bidding on the auction) or snap the domain between the auction and the closure. So the bright side is, it doesn't matter if you bid on the auction or try to snap it at the closure - if they have the name queued, they will get it anyway (unless you're willing to outbid them). On the other hand, if they don't have the name queued, they won't bid on it anyway, so the only "bad" thing about bidding might be attracting other domainers to the auction, but for HD bot it's probably meaningless.

Attached are some screenshots as a proof for the above paste.
You should have bid them up to $150, they would have probably paid more. Anytime you get the chance bid them up, just like they bid you up, if their bots wants it that bad, make them pay for it.
 
Last edited:
2
•••
I honestly don't bid much unless if I want to cost you money for placing a bid. I truly believe I have being beating hugedomains at well either they have it on their list or not. I haven't lost a name for about 2 month once it goes to closeouts. So, this notion they can get it if it is on their list is incorrect...invest in developing an application...
Curious to know how they gave you API access if you don't bid much, you have to spend a decent amount of money to get access?
 
2
•••
Curious to know how they gave you API access if you don't bid much, you have to spend a decent amount of money to get access?
I used to bid a lot last year. And don't get me wrong. That was a mistake as hugedomains always jumps in and cost me money than I was willing to pay. Spend over $200 per domain. Lesson learned. Never again unless if I absolutely wanted the name.
 
Last edited:
2
•••
I used to bid a lot last year. And don't get me wrong. That was a mistake as hugedomains always jumps in and coat me money than I was willing to pay. Spend over $200 /per domain where I could have got them for $20 have I waited to closeout. Lesson learned. Never again unless if I absolutely wanted the name.
Yes, your exactly right, now my concern has always been Huge Names with 7 million names, and the most drop catch connections, what are they doing over at Godaddy paying $200 per domain, for domains that should be wholesaling for $20-50?
 
3
•••
Yes, your exactly right, now my concern has always been Huge Names with 7 million names, and the most drop catch connections, what are they doing over at Godaddy paying $200 per domain, for domains that should be wholesaling for $20-50?
I think they are in it to drive domainers out of business.
 
3
•••
I think they are in it to drive domainers out of business.
Well at the same time they are the single largest portfolio holder, and if they can disrupt supply, and demand, they essentially driving up the value of their portfolio, and forcing people to buy from them, making sure there are no cheap domains on the open market to be acquired. I really don’t know, but I hate it when they push single bidders up into hundreds, just based on that one person bidding. They been at it a while, including with the backorder loophole a few years back, any weakness they find in the system, they will game it.
 
2
•••
Well at the same time they are the single largest portfolio holder, and if they can disrupt supply, and demand, they essentially driving up the value of their portfolio, and forcing people to buy from them, making sure there are no cheap domains on the open market to be acquired. I really don’t know, but I hate it when they push single bidders up into hundreds, just based on that one person bidding. They been at it a while, including with the backorder loophole a few years back, any weakness they find in the system, they will game it.
Very true. I hate it. My question that I am always wondering about is how much sales they do a month in order to keep it going like this. With 7M+ domains, they need almost 60M+ a year just to break even...I always tend to bid when I sense they jumped in. I have no desire in the domain, but I just want to cost them just like how they cost every domainers. Got screwed few times where I ended up being the highest bidder, but that's OK I guess...
 
1
•••
I used to bid a lot last year. And don't get me wrong. That was a mistake as hugedomains always jumps in and cost me money than I was willing to pay. Spend over $200 per domain. Lesson learned. Never again unless if I absolutely wanted the name.
You are lucky, I get the names you want for more than $ 1,000 each. And many times, prices start to rise from the last 30 minutes. Right now I just trust registration.
 
0
•••
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back