.onion addresses normally should be made of a base32 string of the first 80 bits of the SHA1 hash of the private key of the server (see .onion address specification).

Today I ran into a service which clearly doesn't have an arbitrary address: http://sms4tor3vcr2geip.onion/

How does that work and is it secure?

  • 1
    It is actually an encoding of a hash of the PUBLIC key, not private, per the spec you linked ("a base32 encoding of a10-octet hash of Bob's service's public key").
    – Ryan Tate
    Apr 22, 2016 at 16:09
  • I don't seem to be able to submit a new answer to this old question, but the current standard for onion addresses has progressed to version 3, which are more secure, and are much longer. An example of the new format would be compasshoptbngkg7yjeur6fl7izfiodsqgfjfdaxccsnpptyvkz2uid.onion and these are generated using the mkp224o utility downloadable from github.com/cathugger/mkp224o. Instructions for compiling and running this on linux (like my Raspberry PI 4) are at reviewer.ablative.website/post/tor-onion-v3-vanity-address Dec 14, 2021 at 23:54

5 Answers 5


Shallot is an older program, there are newer alternatives available now:

Scallion - uses GPU hashing, needs .NET or Mono: http://github.com/lachesis/scallion

Eschalot - uses wordlist search, needs Unix or Linux: http://blacksunhq56imku.onion

Eschalot can find longer human-readable names like seedneedgoldcf6m.onion, hostbathdarkviph.onion, etc.

The performance chart quoted above is a bit obsolete now, 8-10 character long .onions are easy enough to find.

There was a discussion back in the day, when shallot first surfaced, about whether custom names for hidden services are bad or not.

Problem number one: generated keys have a much larger public exponent than the standard keys produced by TOR, which puts a somewhat higher load on the TOR relays.

Answer: it was concluded that the difference is negligible compared to the other encryption tasks the relays perform constantly. In eschalot, the largest public exponent is limited to 4294967295 (4 bytes).

Problem number two: TOR developers can decide to filter and block all the custom names.

Answer: yes, they can, but they have not yet and there is really no reason for them to do so. They can just as easily change the standard for the random names too and cause chaos and mass exodus on the network.

Problem number three: generated names are easily spoofed, since the visitor clicking on a link somewhere out there can be tricked by the seemingly right .onion prefix without checking the whole thing. To demonstrate, which one is the real SilkRoad?


Answer: neither, I generated all of them to demonstrate the problem. If you recognized that those were all fakes, you probably spend more time on the SilkRoad than I care to know about :).

To be fair, completely random addresses are even worse - if somebody edits one of the onion links wikis and replaces one random address with another, the casual visitor using that wiki would not know the difference.

Solution: it's essentially up to the person to pay attention which site he is really visiting, but the site owner can create a human readable address that is easier to remember, even if it's a completely random gibberish. As long as it's long and easy to memorize and identify. Some examples:


I did not spend the time to intentionally generate good names, just picked some from the list I had left after testing eschalot. With a (very) large wordlist, unique looking names are easy to generate, but it will take time to go through the results and manually locate the ones that are decent.

Well, that was my opinion and it could be wrong.

-- Hiro

  • The eschallot link seems to be down... any other place to obtain this program?
    – user9651
    Jul 19, 2013 at 16:07
  • Found eschalot: skunksworkedp2cg.onion It has a link to the eschalot source code, I didn't test it yet.
    – user9651
    Jan 18, 2015 at 20:17
  • @nus: There is also a github clone: github.com/ReclaimYourPrivacy/eschalot
    – serv-inc
    Dec 29, 2015 at 17:39
  • The clone is current, the onion link above is dead, but there is a mirror: nope7beergoa64ih.onion/eschalot
    – serv-inc
    Dec 30, 2015 at 10:10

You can use brute-force to find a key that partly match the hash you want. One tool for this is Shallot. The readme of Shallot says this about the security:

It is sometimes claimed that private keys generated by Shallot are less secure than those generated by Tor. This is false. Although Shallot generates a keypair with an unusually large public exponent e, it performs all of the sanity checks specified by PKCS #1 v2.1 (directly in sane_key), and then performs all of the sanity checks that Tor does when it generates an RSA keypair (by calling the OpenSSL function RSA_check_key).

To get an idea of the time involved in generating with Shallot, also from the readme:

Time to Generate a .onion with a Given Number of Initial Characters on a 1.5Ghz Processor:

characters | time to generate (approx.)
1   | less than 1 second    
2   | less than 1 second    
3   | less than 1 second   
4   | 2 seconds    
5   | 1 minute    
6   | 30 minutes    
7   | 1 day    
8   | 25 days  
9   | 2.5 years  
10 | 40 years  
11 | 640 years  
12 | 10 millenia  
13 | 160 millenia  
14 | 2.6 million years
  • 4
    Possibly a stupid question, but what happens when there are collisions? Jan 31, 2013 at 22:53
  • 1
    someone can imposter your site if they manage to generate the same private key...
    – user9651
    Feb 1, 2013 at 0:49
  • 1
    You can see from the table above that matching all 16 would be quite a feat. Feb 1, 2013 at 3:13
  • 6
    some obscure government agencies have more than one 1.5Ghz processors at their disposal though...
    – user9651
    Apr 20, 2014 at 3:40
  • 7
    >> facebookcorewwwi.onion. It didn't a take millenia to generate
    – balki
    Jun 4, 2015 at 13:25

Adding to Johan Nilsson's answer (as I can't post comments): It seems that even 13-character named .onion URLs have been created, a comment on this Tor blog entry mentions a 13-character onion URL: deeproadworksbwj.onion (don't connect to it, I don't know what it is or if it's good).


I presume that they simply brute-force the private key generation, discarding the ones which do not have the desired properties.

Since it's only 7 characters at the beginning which I guess they wanted, it can't be too computationally expensive?

  • any idea of how computationally expensive?
    – user9651
    Jan 27, 2013 at 21:52
  • 3
    7 Chars in Base32 = 32^7 bits of entropy, so you'd need to search (on average) 32^6 (About 1 billion). So, take your average time to compute a key for TOR and times it by a billion. Jan 28, 2013 at 0:10
  • 2
    These names are generated in almost the same way that novelty tripcodes are generated on image boards like 4chan. Jan 31, 2013 at 4:23

These links for eschalot are current as of this post:

The original link seems dead (as also confirmed by the second eschalot source). If you would rather do the search yourself:

You must log in to answer this question.