---
title: "WikiLeaks.ORG DNS is NOT with easyDNS (so far)"
type: "post"
post_id: "1171"
slug: "wikileaks-org-dns-is-not-with-easydns-so-far"
canonical: "https://easydns.com/blog/2010/12/13/wikileaks-org-dns-is-not-with-easydns-so-far/"
markdown_url: "https://easydns.com/blog/2010/12/13/wikileaks-org-dns-is-not-with-easydns-so-far.md"
json_url: "https://easydns.com/blog/2010/12/13/wikileaks-org-dns-is-not-with-easydns-so-far.json"
txt_url: "https://easydns.com/blog/2010/12/13/wikileaks-org-dns-is-not-with-easydns-so-far.txt"
published: "2010-12-13T15:36:16+00:00"
modified: "2024-11-13T17:06:18+00:00"
author: "Mark E. Jeftovic"
categories:
  - "Of Interest"
tags:
  - "wikileaks"
site_name: "easyDNS"
publisher: ""
language: "en-US"
generator: "easyPress Markdown"
generator_version: "1.0.3"
---
Just in case you were not **confused enough** as to whether we unplugged wikileaks, helped them get back online; or had unprotected “relations” with Julian Assange (we didn’t),[ the story “broke” this morning](http://thenextweb.com/media/2010/12/13/wikileaks-org-domain-comes-back-online-with-the-help-of-new-dns-providers/) that WikiLeaks.org was back, due to help from easyDNS:

> Access to Wikileaks.org has returned after members of its consortium worked with Mark Jeftovic, founder of EasyDNS, to help them get their domains back online.

Which is not the case, not today. A little over a week ago, we *were* contacted by an independent group attempting to revive DNS for wikileaks.org and wikileaks.ch, which were both unplugged by our evil twin: EveryDNS (just kidding guys). Last sunday we were added to the delegation for the wikileaks fallback domain **wikileaks.ch,** and on monday **wikileaks.nl** came on (see “Further Reading” at end of this post) – and while we were originally told to prepare for .org, it never materialized.

Today when wikileaks.org came back online, it was on the nameservers of their Registrar, dynadot. This is clearly visible in [a whois lookup for wikileaks.org](http://www.easywhois.com/?domain=wikileaks.org&mode=whois&S=mozsearch), which is something I encourage any reporter or blogger attempting to comment intelligently on this situation to do, lest they run the risk of looking foolish or worse, ending up on my list of “people to kill” when I finally snap and go on a shooting spree.

On a brigher note there was [a good article in the New York Times this morning](http://www.nytimes.com/2010/12/13/business/global/13wiki.html?hp) about the entire situation which was accurate (imagine that) – thank you.

Further Reading
---------------

- [Wikileaks “takedown” fiasco underscores pathetic state of internet “journalism”](https://www.easydns.com/blog/2010/12/03/wikileaks-takedown-fiasco-underscores-pathetic-state-of-internet-journalism/)
- [Thank you to all, I would like this to stop now.](https://easydns.com/../2010/12/04/thank-you-to-all-i-would-like-this-to-stop-now/)
- [Ok Would We Take On DNS FOr Wikileaks](https://easydns.com/../2010/12/03/ok-so-would-we-take-on-wikileaks-dns-at-this-point/)?
- [easyDNS added to Wikileaks.ch DNS delegation](https://easydns.com/../2010/12/03/2010/12/05/easydns-added-to-wikileaks-dns-delegation/ "Permanent Link to easyDNS added to Wikileaks.ch DNS delegation")
- [Concerns around Wikileaks DNS for easyDNS Members](https://easydns.com/../2010/12/06/the-implications-of-wikileaks-dns-for-easydns-members/)
- [Timeline of an Epic #FAIL: The Wikileaks Takedown Fiasco](https://easydns.com/../2010/12/07/timeline-of-an-epic-fail-the-wikileaks-takedown-fiasco/)