Why I Prefer Transfers at Dan.com

It’s always nice to see the triple email string at Dan.com notifying me that a domain name was sold on the platform. One of those messages is to ask how I would like to handle the domain name transfer. With most of my domain names registered at GoDaddy, I am given the choice of doing a push to Dan.com’s holding account or sending the authorization code for an outbound transfer.

In the past, I would usually choose an internal transfer at GoDaddy. It is easy to do an account change, and I wouldn’t have to rely on another registrar’s processes to handle. The one thing to note is Dan.com requests that sellers keep Whois information the same when pushing presumably so the domain name is not locked by GoDaddy following a Whois change. Here’s the note that is/was sent to sellers when the account change option was chosen:

“Important: select (Yes) while pushing the domain to copy the current domain information to the new account. We’ll edit the contact details of importance ourselves when accepting the domain in our account at Godaddy.”

One thing I noticed is that some buyers do not update Whois contact information once Dan.com pushes the domain name to them. I do not believe this is the case when a buyer subsequently transfers a domain name to a different registrar. I notice this because I occasionally receive GoDaddy emails meant for the buyer of the domain name rather than for me, the previous registrant.

I presume Dan.com asks buyers to update Whois records but perhaps buyers don’t follow these instructions. Maybe they intend to transfer the domain name out of GoDaddy and don’t want to lock it up for 60 days following a Whois change. I can’t really speculate since that’s not something I would do.

Because of this, I have opted to unlock my sold domain names and submit the transfer authorization code to Dan.com. Immediately after receiving the code, Dan.com will generally initiate a transfer to their preferred registrar, Metaregistrar. Of note, on my last sale via Dan.com last week, they sent the auth code to the buyer rather than initiating the transfer themselves. This slowed down the process slightly since I had to wait for the buyer to start the transfer.

Elliot Silver
Elliot Silver
About The Author: Elliot Silver is an Internet entrepreneur and publisher of DomainInvesting.com. Elliot is also the founder and President of Top Notch Domains, LLC, a company that has closed eight figures in deals. Please read the DomainInvesting.com Terms of Use page for additional information about the publisher, website comment policy, disclosures, and conflicts of interest. Reach out to Elliot: Twitter | Facebook | LinkedIn

1 COMMENT

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Recent Posts

It Pays to Know Random Phrases

3
My eyes bulge out of my head sometimes when I see a somewhat obscure term in a domain name coming up for auction. Oftentimes,...

Monitor Landing or Parking Page Downtime

0
When I first started developing my domain names, I learned the importance of downtime monitoring. On some of my growing websites, there would be...

Squadhelp is Reinvesting and So Am I

10
Squadhelp CEO Darpan Munjal shared a series of tweets about the growth of the platform. Darpan shared that revenue last month was higher than...

If You Want to See a Stampede, Look No Further Than This…

4
If you're seeking engagement on Twitter in the domain name space, the best thing you can do is tell people you're looking to buy...

Nick Huber: “drop a little coin” for a Premium Domain Name

2
I do not know Nick Huber, but I see he has a large following on Twitter and frequently offers advice to startup founders and...