Think Information. Think Security.
A member of the Anonymous hacktivist group appears to have taken downGoDaddy with a massive Distributed Denial of Service (DDoS). The widespread issue seems to be affecting countless websites and services around the world, although not for everyone. is down, but so are some of the site’s DNS servers, which means GoDaddy hosted e-mail accounts are down as well, and lots more. It’s currently unclear if the servers are being unresponsive or if they are completely offline. Either way, the result is that if your DNS is hosted on GoDaddy, your site may also look as if it is down, because it cannot resolve.

AnonymousOwn3r is claiming sole responsibility for the attack, which is why we haven’t seen this tweeted out by much bigger Twitter accounts such asYourAnonNews (over 628,000 followers) or AnonOps (over 299,000 followers). Either way, this is being done under the “Anonymous” name even if the main communication channels aren’t being used to announce it (though I’m pretty sure they will catch on soon enough). The good news is that GoDaddy is aware of the issue. 

This problem appear when Convo stopped working for Emil Protalinski, ironically stopping him from communicating with The Next Web staff and getting this story out quickly. The service isn’t down for he's colleagues, however, which shows just how erratic the problem is. This tweet, which was retweeted by AnonOpsLegion, sums up the situation perfectly:
Update: GoDaddy just sent out a second tweet, this time with an apology.
Update 2: The reason for the attack is still unclear.
Update 3: This outage is so massive it has taken Talk about irony.
Update 4: GoDaddy is finally fixing the problem.
Update 5: Anonymous is distancing itself from this attack. Remember, anyone can call themselves Anonymous
Update 6: GoDaddy is still hard at work. It’s now the company’s top priority 
Update 7: Someone noticed that GoDaddy’s DNS servers are pointing to VeriSign, one of its competitors. A Hacker News submission has the details.
Update 8: is working for him again. The issue still isn’t completely fixed though
Update 9: More progress, still not completely fixed.
Update 10: Problem solved.

Cross-posted from: Insider

Leave a Reply.