If/when will LE support .onion addresses?

Increasingly we can envisage more practical use cases for .onion certificates.

  • https://emerproxy.xyz - (with Let’s Encrypt 4096-bit SSL), allows resolution of ’ new ’ TLD’s using OpenNIC project DNS

We consider allowing access via a .onion / SSL enabled Tor hidden_service for resolution of OpenNIC TLD’s (through Tor Browser) including;

Emercoin - .emc, .coin, .lib, .bazar - http://emercoin.com/EMCDNS_and_NVS

Namecoin - .bit

New Nations - .uu, .ti, .te, .ku

Open NIC - .bbs, .dyn, .free, .fur, .geek, .gopher, .indy, .ing, .micro, .neo, .null, .oss, .oz, .parody

It is infeasible for every Tor .exit to resolve the above domains. Thus, the only realistic solution (for increased anonymity, privacy and security for the user) is to provide an SSL enabled Tor hidden_service proxy.

However, said encrypted hidden_service, as a web proxy, also effectively provides access to clearnet i.e. a ‘hidden_service’ that is not hidden and a Tor .exit node that is not listed as a Tor network .exit node.

Something towards the new ’ Internet of things ’ – Let’s ’ Encrypt all the things ’ …

and thank you for the existing domain certificate. :sunglasses: