ShadesDaddy founder offers advice on Domain Name Hijacking recovery

Our exclusive coverage of the brazen theft and subsequent recovery of ShadesDaddy.com has a pleasant follow-up.

Pablo Palatnik, founder of ShadesDaddy, promised to return and has published an article that was picked up by Forbes.

In this three-pager, Palatnik offers advice on how to proceed, if your domain has been hijacked.

The key points that Palatnik identifies as important, are:

  • Understanding the role of the company that operates the domain hierarchy
  • Alerting the domain Registrar immediately
  • Hiring an attorney
  • Speed up the process by filing a motion at court
  • Go public about the incident

Mr. Palatnik also notified the FBI, which collected information about the incident, potentially using that in the future to identify other related crimes by the Chinese cybercriminals.

For the full article, click here.

Copyright © 2024 DomainGang.com · All Rights Reserved.

Comments

2 Responses to “ShadesDaddy founder offers advice on Domain Name Hijacking recovery”
  1. Jamie Zoch says:

    Relating to the hijacked domain he stated: “How did this happen? Hackers got into our registrar account, changed all of the information on our account and went ahead and transferred the domain name from our account to their account in China.”

    I was shaking my head from the start of the article, because the most important information wasn’t provided. What actually lead to the hijacking!!?? How did they access the registrar account? You prevent that in the first place, all the other shit doesn’t matter!

    The article is good for those who have a domain hijacked after they click a phishing email, or send login details in wide open spaces etc.

    The real learning part would have been to know HOW the hijackers accessed the account and how to prevent THAT. Prevent that from happening and the rest of the article is not needed!

  2. DomainGang says:

    Jamie – I think that’s too deep for the Forbes readership 😉 But as explained in our coverage of the incident, it all started with a GoDaddy phishing email, and the lack of two-factor authentication.

Leave a Reply

Your email address will not be published. Required fields are marked *

 characters available