Wikileaks Says Its Site Has Been 'Killed'
from the yeah-that'll-help dept
This is definitely a "developing" story, but apparently the entire Wikileaks.org site has gone down again and the Wikileaks folks are claiming that the domain was "killed by US everydns.net after claimed mass attacks." That's a bit cryptic and Wikileaks has not been above jumping to conclusions at times. It's unclear, for example, if it was just the company EveryDNS who did something on their own, or if the US government was involved. It could be as simple as the sort of pressure Senator Lieberman is applying on US companies. Update: The EveryDNS website says they made the decision because the DDoS attacks on Wikileaks violated their terms of service in that it could interfere with other websites. I understand the fear that it could cause problems with other websites, but it seems weird to say that getting attacked by a DDoS violates your terms of service. It's something totally out of the control of the website.Either way, it is a bit silly to think that taking down Wikileaks' website would actually do anything in this situation. The data that they're releasing is out there and plenty of people can easily find it. It won't take long for them to set up another website if they want to -- and while it may be a bit harder for people to find them, to date, the organization hasn't exactly had any problems getting everyone else to promote what they release for them. Whatever the reason is for taking the domain name offline, it's difficult to think it would be effective in stopping Wikileaks in any way. If anything, it just calls that much more attention to the organization.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: domain, wikileaks
Companies: everydns, wikileaks
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
Re:
Interesting. Had checked it before and didn't see anything, but now I do see it... Updating the post (and it's EveryDNS, not EasyDNS)
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re: Re:
Wikileaks is now back up.
http://yro.slashdot.org/story/10/12/03/1232248/WikiLeaks-Moves-To-Swiss-Domain-After-DNS-Takedo wn
[ link to this | view in chronology ]
Thanks Mike
See http://blog.easydns.org for details.
[ link to this | view in chronology ]
Re:
Also, can a denial of service attack against a website really affect the DNS system to such a degree that EveryDNS would little choice but to shut them down? I thought DNS requests were cached by ISPs, thus limiting the registrar's exposure to excessive requests. Isn't that the case here?
I suspect government pressure is involved and wonder how long until we see one of those Homeland Security notices on the Wikileaks domain.
[ link to this | view in chronology ]
Re: Re:
Usually your system will cache the dns information according to the TTL specified in the domain - which is for "static ip addresses" usually in the range of 48h. By issuing a custom dns query you can circumvent that cache.
[ link to this | view in chronology ]
Re: Re: Re:
Assuming Wikileaks is able to recover its domain name and transfer it elsewhere, hopefully they can find a registrar who wouldn't break so easily under the pressure.
[ link to this | view in chronology ]
Re: Re: Re: Re:
Basically at your domain registrar you tell that the nameservers of EveryDNS are the master zone files pointing the IPs of your mail, web, what-ever servers.
I actually like EveryDNS because up to a while ago (before they were bought by no-ip.com) the offered to host the DNS for free - also if you are on a dynamic ip. They offered clients to update your dns automagically.
So don't worry about recovering the domain name.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: not easyDNS!
[ link to this | view in chronology ]
Re: Re: not easyDNS!
My bad.
It is actually NOT easyDNS who was hosting wikileaks.org and shut them down. It was everydns. A different company and unrelated. But we've sure been taking the rap for their decision today.
[ link to this | view in chronology ]
Wikileaks
[ link to this | view in chronology ]
Reverse Streisand Effect?
[ link to this | view in chronology ]
'Dear Customer;
We have been alerted that your website has come under attack by a DDOS attack. We realize this is an illegal attack upon your site in order to remove you from the internet.
As such, we are going to cancel your account, preventing your website from being accessed. This is to counter the crime of DDOS attacks.
We WILL NOT stand for our members coming under attack by criminals, and WILL cancel your account permanently upon being attacked.
Thank you for your support.'
... Actually that was kind of fun to write in a sort of sick and twisted way. I do get where they are coming from, the needs of the many and all, but it still seems like a sort of a... well, disgusting move. 'You violated the terms of services by being attacked.' And then of course, the effective 'it is your fault if you experience any downtime' there at the end.
(None of the preceeding is accurately quoted, but paraphrased and come from the mind.)
[ link to this | view in chronology ]
Re:
If you're curious about the realities behind dealing with DOS attacks, there's a good article at
http://blog.easydns.org/2010/08/19/dos-attacks-and-dns-how-to-stay-up-if-your-dns-provider-goes- down/
[ link to this | view in chronology ]
Re: Re:
I noticed above that SJ mentioned that you can attack the DNS by doing a DNS Lookup, is that the case here, or is it just a possibility? (I assume doing an attack of that nature posts which website is being looked up, so that there is a way to know who drew the ire of the attacker(s)).
And with the above, does the attack do double damage, hitting both the website and DNS provider, or is it basically an attack on just the provider with a link to why?
I also wonder that if it is an attack on the DNS provider itself, how do you track which website drew the ire? Or, does the fact that they do have one website to blame indicate that it was not an attack on the provider directly?
I am admittedly ignorant on how much of this works, and always glad to learn a bit more. Thank you for your time.
[ link to this | view in chronology ]
Re:
Sometimes you have to wipe out an entire village in order to save it.
[ link to this | view in chronology ]
Re: customer letter
Actually it's not quite like that ...
Dear Customer:
Your website has come under a Distributed Denial of Service Attack (DDOS). This is an attack by multiple systems across the Internet against your DNS service, designed to make it impossible for anyone to reach your website.
Unfortunately the attack has the collateral affect of making it impossible for anyone to reach the websites of all our clients, not just you.
We have the unfortunate choice between shutting down your DNS until the attack subsides, or having all our DNS services shut down for all our clients. To avoid loss of service to all our clients, we've had to make the choice to shut down your DNS service. Doing this is not something we take lightly, but unfortunately there's no other choice; ir we don't take this step your site goes down anyone, and so does everyone else's.
If this is a random DDOS attack it will subside in time, and we'll start hosting your DNS again, and of course we'll let you know. However if you're suffering a continuous DDOS attack it's unlikely we'll be able to continue serving your DNS. In that case we'll be happy to consult with you in setting up a DNS solution just for you (no other clients sharing the same servers) which could be more robust in the event of such an attack.
However, we should warn you that this solution could be significantly more expensive than shared DNS hosting.
Please feel free to contact me by email or by telephone to discuss the issues involved and how to best remedy them.
Of course we'd include some links to our terms of service, some excellent articles on preserving DNS services in the face of DDOS attacks, and the like.
In response to your last paragraph, I can only admit that yes, our TOS allows us to shut you down for DDOS. If we had to build the kind of infrastructure that would uphold any DDOS attack, and pay for all the traffic in a DDOS attack, then we'd have to charge 100 times more for our DNS services than we do now.
And then we most likely wouldn't get your business, you'd go elsewhere and risk getting caught up in exactly the DDOS mitigation we do.
[ link to this | view in chronology ]
Re: customer letter
Actually it's not quite like that ...
Dear Customer:
Your website has come under a Distributed Denial of Service Attack (DDOS). This is an attack by multiple systems across the Internet against your DNS service, designed to make it impossible for anyone to reach your website.
Unfortunately the attack has the collateral affect of making it impossible for anyone to reach the websites of all our clients, not just you.
We have the unfortunate choice between shutting down your DNS until the attack subsides, or having all our DNS services shut down for all our clients. To avoid loss of service to all our clients, we've had to make the choice to shut down your DNS service. Doing this is not something we take lightly, but unfortunately there's no other choice; ir we don't take this step your site goes down anyone, and so does everyone else's.
If this is a random DDOS attack it will subside in time, and we'll start hosting your DNS again, and of course we'll let you know. However if you're suffering a continuous DDOS attack it's unlikely we'll be able to continue serving your DNS. In that case we'll be happy to consult with you in setting up a DNS solution just for you (no other clients sharing the same servers) which could be more robust in the event of such an attack.
However, we should warn you that this solution could be significantly more expensive than shared DNS hosting.
Please feel free to contact me by email or by telephone to discuss the issues involved and how to best remedy them.
Of course we'd include some links to our terms of service, some excellent articles on preserving DNS services in the face of DDOS attacks, and the like.
In response to your last paragraph, I can only admit that yes, our TOS allows us to shut you down for DDOS. If we had to build the kind of infrastructure that would uphold any DDOS attack, and pay for all the traffic in a DDOS attack, then we'd have to charge 100 times more for our DNS services than we do now.
And then we most likely wouldn't get your business, you'd go elsewhere and risk getting caught up in exactly the DDOS mitigation we do.
[ link to this | view in chronology ]
Re: customer letter
Actually it's not quite like that ...
Dear Customer:
Your website has come under a Distributed Denial of Service Attack (DDOS). This is an attack by multiple systems across the Internet against your DNS service, designed to make it impossible for anyone to reach your website.
Unfortunately the attack has the collateral affect of making it impossible for anyone to reach the websites of all our clients, not just you.
We have the unfortunate choice between shutting down your DNS until the attack subsides, or having all our DNS services shut down for all our clients. To avoid loss of service to all our clients, we've had to make the choice to shut down your DNS service. Doing this is not something we take lightly, but unfortunately there's no other choice; ir we don't take this step your site goes down anyone, and so does everyone else's.
If this is a random DDOS attack it will subside in time, and we'll start hosting your DNS again, and of course we'll let you know. However if you're suffering a continuous DDOS attack it's unlikely we'll be able to continue serving your DNS. In that case we'll be happy to consult with you in setting up a DNS solution just for you (no other clients sharing the same servers) which could be more robust in the event of such an attack.
However, we should warn you that this solution could be significantly more expensive than shared DNS hosting.
Please feel free to contact me by email or by telephone to discuss the issues involved and how to best remedy them.
Of course we'd include some links to our terms of service, some excellent articles on preserving DNS services in the face of DDOS attacks, and the like.
In response to your last paragraph, I can only admit that yes, our TOS allows us to shut you down for DDOS. If we had to build the kind of infrastructure that would uphold any DDOS attack, and pay for all the traffic in a DDOS attack, then we'd have to charge 100 times more for our DNS services than we do now.
And then we most likely wouldn't get your business, you'd go elsewhere and risk getting caught up in exactly the DDOS mitigation we do.
[ link to this | view in chronology ]
Betting on the banks
[ link to this | view in chronology ]
Re: Betting on the banks
[ link to this | view in chronology ]
Re: Betting on the banks
[ link to this | view in chronology ]
Re: Betting on the banks
[ link to this | view in chronology ]
Of course, at the rate things are going, Lieberman might very well write an anti-P2PDNS bill.
[ link to this | view in chronology ]
Spoiler alert!
[ link to this | view in chronology ]
Hidden Services Wikileaks
Now this is a bit strange maybe not all servers got synched yet but I can still access Wikileaks.
http://wikileaks.org/
[ link to this | view in chronology ]
Re: Hidden Services Wikileaks
If you still can resolve wikileaks.org, it just means you have a cached result somewhere in your resolve chain. because EveryDNS' DNS servers don't answer if you ask for "wikileaks.org", check it yourself with "dig @ns1.everydns.net wikileaks.org" (according to the WhoIs entry for wikileaks.org you can also try ns2, ns3 and ns4 but that doesn't change the result).
Cheers,
Drizzt
[ link to this | view in chronology ]
or our govt will get behind the 8ball by themselves o much, they'll fold.
[ link to this | view in chronology ]
Killing WikiLeaks doesn't do crap.
[ link to this | view in chronology ]
They need a better server company
"Sir, you're under arrest for being shot."
Those 2 things make roughly the same amount of sense. :P
[ link to this | view in chronology ]
Re: They need a better server company
[ link to this | view in chronology ]
Wikileaks LIVES!
Main site: http://46.59.1.2/
Access to all releases: http://88.80.13.160
[ link to this | view in chronology ]
Re: Wikileaks LIVES!
Lose the DNS and go straight to the IP address! http://46.59.1.2/
Apparently the WikiLeaks domains are down too.
(At lest the ones I know about.)
[ link to this | view in chronology ]
Re: Re: Wikileaks LIVES!
[ link to this | view in chronology ]
Re: Re: Wikileaks LIVES!
Cheers,
Drizzt
[ link to this | view in chronology ]
Re: Wikileaks LIVES!
[ link to this | view in chronology ]
Re: Wikileaks LIVES!
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
Thank god it wasn't the French. That would be embarrassing.
[ link to this | view in chronology ]
Wikileaks moves to Switzerland
[ link to this | view in chronology ]
Re: Wikileaks moves to Switzerland
http://213.251.145.96/ The main home page
http://213.251.145.96/cablegate.html The CableGate Transcripts
http://213.251.145.96/support.html - SUPPORT THEM AND DONATE
[ link to this | view in chronology ]
http://46.59.1.2/
They might kill the domain name, but taking down that server is a completely different challenge...
[ link to this | view in chronology ]
Just wondering
Doesn't what these companies say just sound like the kind of propaganda you could have expected from the Soviet Union? I.e. saying exactly the opposite of the truth. In this case clearly EveryDNS's customers can't have any trust that EveryDNS will try keep their sites up.
[ link to this | view in chronology ]
Re: Just wondering
Office of Open Internet Dept.
[ link to this | view in chronology ]
DNS issues
Second, the root of their DNS is not EveryDNS, it is the .org registry, where they can simply point to another set of DNS servers. They can even host the DNS themselves (it is very easy to do, you just need a couple of servers). Thus, unless the .org registry is involved, that domain name is not permanently down.
Third, to those posting tor addresses (.onion): you can use tor2web to view them without installing tor. However, the site given does not appear to be the official Wikileaks site, but a mirror by someone else, which is probably a bit outdated.
[ link to this | view in chronology ]
Re: DNS issues
The other onion addresses don't work here but maybe you have more luck.
[ link to this | view in chronology ]
But maybe now you understand how the sleeping giant was awakened.
And I hope you know that if you guys could have only kept your fingers out of the cookie jar, this sort of thing never would have been tolerated.
You enabled this.
It's on you.
[ link to this | view in chronology ]
Re:
The sleeping giant bureaucracy.
Doesn't really matter, this helps keep the government on its toes and honest.
[ link to this | view in chronology ]
Who needs domains anyway?
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Next step, build torrents of all the latest backups *sigh* there go's my saturday haha.
[ link to this | view in chronology ]
Not an easy job, but someone has to do it. Don't want the sheep to see how stupid our diplomacy has become.
I'm not surprised at all, given that the TSA and Homeland Security have been hard at work taking down sights without notice on the pretext that they were counterfeiting merchandise.
Remember one thing-the internet was based on the governments' backbone infrastructure. Still is, for the most part, even though we believe otherwise.
The government for the most part owns all of the pipes, and if they don't like the stuff you give out, they can and will take a site down.
[ link to this | view in chronology ]
DNS services shut down you for DDOS since when?
[ link to this | view in chronology ]
How to enter wikileaks
http://213.251.145.96/reldate/2010-12-03_0.html
[ link to this | view in chronology ]
[ link to this | view in chronology ]
script-kiddie hacker claims responsibility
http://twitter.com/th3j35t3r
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Make a (local) copy of the content at this URL
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Notice this happened after they threatened to leak info on China and Russia?
[ link to this | view in chronology ]
New Domain is Down....
[ link to this | view in chronology ]
What has happened in the past isn't what this shutdown is about, media centers already have every document that has been posted. Makes for nice new articles every day.
Why did it get taken down now? What was coming up? It sure wasn't taken down to close the barn door after the horses got out, so just what was coming up to be released? Answer that and you might answer the question of who took it down.
[ link to this | view in chronology ]
wikileaks FTW
[ link to this | view in chronology ]
EveryDNS rationale makes no sense
[ link to this | view in chronology ]