After a Transfer, Make Sure Whois Information is Accurate

The other day, I received an email from Go Daddy telling me that action was required for a domain name I had sold months ago. The email I received was the standard email that is sent when a transfer is initiated for a Godaddy-registered domain name, and it contained the security code and password needed to transfer the domain name.

For whatever reason, when I sold the domain name and it was transferred to Godaddy, my contact information was retained for the domain name. If you do a Whois lookup for this domain name, you will still see all of my information listed, as if I had never sold and transferred the domain name. Since the DNS had been changed by the buyer, I know it is in his account and he has control of the domain name, despite the Whois information.

If I had nefarious intentions, I could possibly transfer the domain name out of Godaddy, put privacy on it, and pretend to know nothing about it. Of course, I don’t have these intentions, but it is conceivable and that is problematic. At the very least, it would make proving an ownership change difficult if Escrow.com was used and the buyer decided to not acknowledge the transfer.

When you buy a domain name and transfer it to a new registrar, I strongly recommend you do a Whois search to be sure that you actually are listed as the registrant. It can take up to 24 hours for the new information to be reflected, but it’s important to note. If the information is not accurate, you should change it in your account as soon as possible.

One would hope your business colleagues are honest, but there are plenty of people that wouldn’t think twice about screwing you over and claiming it was an accident “oops, I forgot that I had sold the name!”

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

3 COMMENTS

  1. I think GoDaddy has an issue in their software. I’ve had this same kind of whois thing happen more than once.

    It also seems to happen with the annual ICANN whois info confirmations. The domain doesn’t show in your account, but the ICANN whois notice still has the old info before it was sold and transferred.

    Strange.

  2. Another important thing to do is to CHANGE the EPP auth-info code too, after the transfer completes. Otherwise, the old registrant would have that knowledge (and if the domain name was ever unlocked, could transfer it away).

    Registrars should be randomizing the EPP code so that it’s reset to a new value after a successful transfer, to save one having to do it oneself. Fortunately, I don’t do very many transfers, as I focus only on a small number of good domain names.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Recent Posts

Do You Own Your FirstNameLastName.com?

10
Owning your first name last name .com domain name is a flex for some people. It can make it easier for people to find...

Moonshot BIN Pricing, but Invite a Negotiation

0
TonyNames shared another exceptional .ai domain name sale earlier today. Tony sold the 3 letter FRL.ai domain name for $30,000. In the post announcing...

The $5k Limit

8
I have been in a negotiation with a buyer, and it seems like we are close to an agreement on a domain name sale....

No Nameserver Change ≠ Fake Sale

1
A few years ago, I privately closed a very substantial domain name sale. Following the sale, the buyer did absolutely nothing with the domain...

GoDaddy to Launch “Premium Domain Marketplace” on DomainNames.com

6
The Afternic X account posted a link on X without much context that caught my attention this morning: 👀 https://t.co/JL8P45lRng 🔜 — Afternic (@afternic) October 3, 2025 https://platform.twitter.com/widgets.js Visiting...