Currently http://WikiLeakS.org is either having technical Domain Name System problems, or, there has indeed been a Temporary Restraining Order granted by the California Northern District Court in San Francisco, against Wikileaks et al, on behalf of Bank Julius Baer.
See the previous blog article:- "WikiLeakS.org and their Domain Name Registrar are being sued in California by Bank Julius Baer"for more details
This lack of a working WikiLeakS.org domain name also affects the URL
and the the SSL encrypted version at
However the WikiLeaks front end servers, currently hosted in Sweden, are still working, and can still be accessed via some, but not all of the published list of Public Cover Names:
Why are Bank Julius Baer and their Hollywood celebrity media spin lawyers Lavely & Singer, trying to abuse the US legal system, to censor WikiiLeakS.org, over some alleged documents which have nothing to do with the USA ? The alleged documents which WikilLeakS.org have published, involve dubious financial transactions in the Cayman Islands and Switzerland, whilst the WikiLeakS,org copies of these alleged documents appear to be located in Sweden
Here is a list of Wikileaks Cover Name URL links which worked ok for us in the last few hours:
http://wikileaks.la/
https://secure.wikileaks.la/
http://home.e.co.za/
https://secure.home.e.co.za/
http://joburg.e.co.za/
https://secure.joburg.e.co.za/
http://new.alain.co.za/
https://secure.new.alain.co.za/
http://wikileaks.be/
https://secure.wikileaks.be/
http://stockholm.divx.se/
https://secure.stockholm.divx.se/
http://jwdc.org/
https://secure.jwdc.org/
http://ljsf.org/
https://secure.ljsf.org/
http://freedomsbell.org/
https://secure.freedomsbell.org/
http://freedomspen.org/
https://secure.freedomspen.org/
http://libertypen.org/
https://secure.libertypen.org/
http://sunshinepress.org/
https://secure.sunshinepress.org/
http://new.1.vg/
https://secure.new.1.vg/
http://zurich.base-v.ch/
https://secure.zurich.base-v.ch/
http://bratislava.iypt.sk/
https://secure.bratislava.iypt.sk/
http://new.iypt.sk/
https://secure.new.iypt.sk/
http://wikileaks.org.uk/
https://secure.wikileaks.org.uk/
http://new.ilex.cl/
https://secure.new.ilex.cl/
http://wikileaks.tl/
https://secure.wikileaks.tl/
http://freedomsbell.com/
https://secure.freedomsbell.com/
http://wikileaks.in/
https://secure.wikileaks.in/
http://bucharest.roxi.ro/
https://secure.bucharest.roxi.ro/
http://wikileaks.es/
https://secure.wikileaks.es/
http://wikileaks.ws/
https://secure.wikileaks.ws/
http://riga.ax.lt/
https://secure.riga.ax.lt/
http://special.k.vu/
https://secure.special.k.vu/
http://wikileaks.cx/
https://secure.wikileaks.cx/
http://new.it.cx/
https://secure.new.it.cx/
Some of the Cover Names presumably just re-direct traffic to the now missing www.wikileaks.org and so are effectively not working either i.e.
http://wikileaks.org.au/
https://secure.wikileaks.org.au/
http://wikileaks.de/
https://secure.wikileaks.de/
http://wikileaks.org.nz/
https://secure.wikileaks.org.nz/
Some are more peculiar in that unencrypted URLs either time out or are not working,
However, the corresponding SSL URLs work ok e.g.:
https://secure.smoke.ganja.nl/
https://secure.moskva.orts.ru/
Remember to check the Digital Certificate of any "https://" website you connect to (you may not always get a warning pop-up in your browser).
We may write a future blog article about the pros and cons of accessing WikiLeakS.org via an SSL encrypted page, with or without the use of proxy servers, especially with regard to anonymity and to evading censorship.
There are different trade-offs for website readers of leaked articles, for people who choose to comment on the Talk pages, for document and intelligence analysts and annotators (if the public is ever allowed to do this in proper Wiki mode), and, of course, for genuine whistleblowers (or fake propaganda spinners) who upload leaked documents.
None of the links seem to be working out of Hungary. Including your link to Wikileaks cover pages. Any ideas??
@ James - same problem occurs from the USA or the UK
The list of what were working Cover Names pointed to
a13-160-n20.cust.prq.se [88.80.13.160]
in Sweden, but traceroute to that address gives the same problem.
It is hard to say if this is a technical problem, perhaps bandwidth related, like WikiLeakS.org suffered but did not bother to explain or apologise for, when they published the first Guantanamo Bay concentration camp manual.
Alternatively, it could be the result of the Bank Julius Baer court case.
Since all the WikiLeakS.org web and mail servers were essentially
sharing the one public IP address (there may be other machines behind this), that is a Single Point of Failure for technical problems, deliberate technical Denial of Service attacks, or litigation based legal threats or Court orders.
Since WikiLeaKs.org seem to have abandoned the use of rgwir published PGP Public Encryption and Signing keys (which expired in November last year), they cannot even publish an authenticated Press Release about the situation, on other websites or email lists etc.
Perhaps the backup site, which popped up in Germany, during the Guantanamo Bay document traffic surge might be hauled into action, but there is no sign of such a backup plan in action , as yet.
Global scale resilient webhosting costs a lot of money, which, the WikiLeakS.org project presumably does not yet have. .
UPS fire at Swedish hosting company PRQ Inet, which may explain some of the Single Point of Failure problems:
www.prq.net / www.prqinet.net now says
PRQ Inet was where The Pirate Bay was hosted, until recently, so they have experience of being raided by the Police and having their serves and and logfiles (if anmy) taken away as a result of cvil legal action by corportate lawyers.
So some of the list of Wikileaks Cover Names above, pointing directly to 88.80.13.160 are working again.
N.B. http://WikiLeakS.org is still not resolving, (no domain name servers) so that may well be the result of the legal case in California.
Yes. Wikileaks has been hit by a surprise (less than 24 hours notice, "served by email" TRO on its registrar). The order was granted Thursday afternoon. Wikileaks was NOT notified of the order except through our former council who lives in San Francisco and present for the start of the hearing (then removed from the hearing and its outcome). Dynadot, the Californian domain registrar acted in breach of Wikileaks and ICANN contract by blocking transfer of the domain BEFORE the hearing (and order).
Wikileaks.cn (China) has also been seized (illegally), we were expecting that.
However for the land of the free and the brave, we certainly were not were not expecting an attack on the registrar, justified by prior publishing restraint (!) and backed by a bunch of Cayman Islands money launderers and Hollywood lawyers trying to cover up the true structures of trusts and shell companies.
Then today there was a fire in our Swedish data center.
Backups are on-line.
ps. The judge in Thursday's hearing was a Bush appointee and former prosecutor, "not noted" as they say, in legal circles for his love of the First Amendment.
All I have to say is go for it. "When" the US gov't declares martial law rather than "if" it'll be interesting if I won't die under torture and having named every person I've ever know handsomely maimed as well. I just hope I have the presence of mind to go thru the 25% of the population which are fascist in and of themselves unable to be anything else, that I know first.
I don't know what HTML tags are.
Please keep up the good work.
I think of East Timor in light of my 25% and think well if they killed 33% and didn't get the 25% that leaves a pretty poor balance of the remainder.
I notice the (If you...for waiting.) the message ain't jes for you.
Grant Cramond,
too old to matter
The following are not working when accessed from Essex, UK. I'm getting a 'cannot find server' message.
home.e.co.za
joburg.e.co.za
new.alain.co.za
stockholm.divx.se
new.iypt.sk
new.ilex.cl
bucharest.roxi.ro
special.k.vu
new.it.cs
secure.smoke.ganja.nl
secure.moskva.orts.ru
Have not checked any of the secure.whatever sites other than the last two.
I have added a subdomain that points directly to their IP address at 88.80.13.160 - https://wikileaks.libertynews.org
Your not the only one with DNS issues :( Glad to see you back up and running.
Love "Light" and Energy
_Don