It'd be funny if hns.to got taken down for providing a path to Sci-Hub. At the root, the problem is trying to use the highly centralized legacy DNS system for

It'd be funny if hns.to got taken down for providing a path to Sci-Hub. At the root, the problem is trying to use the highly centralized legacy DNS system for purposes contrary to the wishes of those who control that system. To be "uncensorable", you need to change clients to use something other than DNS to resolve names. Anyway, the property you usually want to abandon for global names is "human-meaningful". Just use key hashes as names. "Human-meaningful" strings should be reserved for local nicknames, for the simple reason that the same string will often have different meanings to different humans, for reasons predating your system and entirely outside of its control. You have no way to guarantee that what you list as "Sci-Hub" is actually what the user thinks she's looking for as "Sci-Hub", and you have even less certainty of that for any less famous name.