07/30/14

Tor Traffic Confirmation Attack

Tor Traffic Confirmation Attack -Roger Dingledine Report
SUMMARY:
  On July 4 2014 we found a group of relays that we assume were trying
  to deanonymize users. They appear to have been targeting people who
  operate or access Tor hidden services. The attack involved modifying
  Tor protocol headers to do traffic confirmation attacks.gato_signal_02

  The attacking relays joined the network on January 30 2014, and we
  removed them from the network on July 4. While we don't know when they
  started doing the attack, users who operated or accessed hidden services
  from early February through July 4 should assume they were affected.

  Unfortunately, it's still unclear what "affected" includes. We know
  the attack looked for users who fetched hidden service descriptors,
  but the attackers likely were not able to see any application-level
  traffic (e.g. what pages were loaded or even whether users visited
  the hidden service they looked up). The attack probably also tried to
  learn who published hidden service descriptors, which would allow the
  attackers to learn the location of that hidden service. In theory the
  attack could also be used to link users to their destinations on normal
  Tor circuits too, but we found no evidence that the attackers operated
  any exit relays, making this attack less likely. And finally, we don't
  know how much data the attackers kept, and due to the way the attack
  was deployed (more details below), their protocol header modifications
  might have aided other attackers in deanonymizing users too.

  Relays should upgrade to a recent Tor release (0.2.4.23 or
  0.2.5.6-alpha), to close the particular protocol vulnerability the
  attackers used -- but remember that preventing traffic confirmation in
  general remains an open research problem. Clients that upgrade (once
  new Tor Browser releases are ready) will take another step towards
  limiting the number of entry guards that are in a position to see
  their traffic, thus reducing the damage from future attacks like this
  one. Hidden service operators should consider changing the location of
  their hidden service.

THE TECHNICAL DETAILS:
  We believe they used a combination of two classes of attacks: a traffic
  confirmation attack and a Sybil attack.

  A traffic confirmation attack is possible when the attacker controls
  or observes the relays on both ends of a Tor circuit and then compares
  traffic timing, volume, or other characteristics to conclude that the
  two relays are indeed on the same circuit. If the first relay in the
  circuit (called the "entry guard") knows the IP address of the user,
  and the last relay in the circuit knows the resource or destination
  she is accessing, then together they can deanonymize her. You can read
  more about traffic confirmation attacks, including pointers to many
  research papers, at this blog post from 2009:
  https://blog.torproject.org/blog/one-cell-enough

  The particular confirmation attack they used was an active attack where
  the relay on one end injects a signal into the Tor protocol headers,
  and then the relay on the other end reads the signal. These attacking
  relays were stable enough to get the HSDir ("suitable for hidden
  service directory") and Guard ("suitable for being an entry guard")
  consensus flags:
  https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt#l1775
  Then they injected the signal whenever they were used as a hidden
  service directory, and looked for an injected signal whenever they
  were used as an entry guard.

  The way they injected the signal was by sending sequences of "relay"
  vs "relay early" commands down the circuit, to encode the message they
  want to send. For background, Tor has two types of cells: link cells,
  which are intended for the adjacent relay in the circuit, and relay
  cells, which are passed to the other end of the circuit.
  https://gitweb.torproject.org/torspec.git/blob/HEAD:/tor-spec.txt#l364
  In 2008 we added a new kind of relay cell, called a "relay early"
  cell, which is used to prevent people from building very long paths
  in the Tor network (very long paths can be used to induce congestion
  and aid in breaking anonymity):
  http://freehaven.net/anonbib/#congestion-longpaths
  https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/110-avoid-infinite-circuits.txt
  But the fix for infinite-length paths introduced a problem with
  accessing hidden services:
  https://trac.torproject.org/projects/tor/ticket/1038
  and one of the side effects of our fix for bug 1038 was that while
  we limit the number of outbound (away from the client) "relay early"
  cells on a circuit, we don't limit the number of inbound (towards the
  client) relay early cells:
  https://lists.torproject.org/pipermail/tor-commits/2009-July/014679.html

  So in summary, when Tor clients contacted an attacking
  relay in its role as a Hidden Service Directory to publish
  or retrieve a hidden service descriptor (steps 2 and 3 on
  https://www.torproject.org/docs/hidden-services), that relay would
  send the hidden service name (encoded as a pattern of relay and
  relay-early cells) back down the circuit. Other attacking relays,
  when they get chosen for the first hop of a circuit, would look for
  inbound relay-early cells (since nobody else sends them) and would
  thus learn which clients requested information about a hidden service.

  There are three important points about this attack:

  A) The attacker encoded the name of the hidden service in the injected
  signal (as opposed to, say, sending a random number and keeping a local
  list mapping random number to hidden service name). The encoded signal
  is encrypted as it is sent over the TLS channel between relays. However,
  this signal would be easy to read and interpret by anybody who runs
  a relay and receives the encoded traffic. And we might also worry
  about a global adversary (e.g. a large intelligence agency) that
  records Internet traffic at the entry guards and then tries to break
  Tor's link encryption. The way this attack was performed weakens Tor's
  anonymity against these other potential attackers too -- either while
  it was happening or after the fact if they have traffic logs. So if
  the attack was a research project (i.e. not intentionally malicious),
  it was deployed in an irresponsible way because it puts users at risk
  indefinitely into the future.

  (This concern is in addition to the general issue that it's probably
  unwise from a legal perspective for researchers to attack real users
  by modifying their traffic on one end and wiretapping it on the
  other. Tools like Shadow are great for testing Tor research ideas out
  in the lab: http://shadow.github.io/ )

  B) This protocol header signal injection attack is actually pretty neat
  from a research perspective, in that it's a bit different from previous
  tagging attacks which targeted the application-level payload. Previous
  tagging attacks modified the payload at the entry guard, and then
  looked for a modified payload at the exit relay (which can see the
  decrypted payload). Those attacks don't work in the other direction
  (from the exit relay back towards the client), because the payload
  is still encrypted at the entry guard. But because this new approach
  modifies ("tags") the cell headers rather than the payload, every
  relay in the path can see the tag.

  C) We should remind readers that while this particular variant of
  the traffic confirmation attack allows high-confidence and efficient
  correlation, the general class of passive (statistical) traffic
  confirmation attacks remains unsolved and would likely have worked
  just fine here. So the good news is traffic confirmation attacks
  aren't new or surprising, but the bad news is that they still work. See
  https://blog.torproject.org/blog/one-cell-enough for more discussion.

  Then the second class of attack they used, in conjunction with their
  traffic confirmation attack, was a standard Sybil attack -- they
  signed up around 115 fast non-exit relays, all running on 50.7.0.0/16
  or 204.45.0.0/16. Together these relays summed to about 6.4% of the
  Guard capacity in the network. Then, in part because of our current
  guard rotation parameters:
  https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
  these relays became entry guards for a significant chunk of users over
  their five months of operation.

  We actually noticed these relays when they joined the network, since
  the DocTor scanner reported them:
  https://lists.torproject.org/pipermail/tor-consensus-health/2014-January/004134.html
  https://gitweb.torproject.org/doctor.git
  We considered the set of new relays at the time, and made a decision
  that it wasn't that large a fraction of the network. It's clear there's
  room for improvement in terms of how to let the Tor network grow while
  also ensuring we maintain social connections with the operators of all
  large groups of relays. (In general having a widely diverse set of relay
  locations and relay operators, yet not allowing any bad relays in,
  seems like a hard problem; on the other hand our detection scripts did
  notice them in this case, so there's hope for a better solution here.)

  In response, we've taken the following short-term steps:

  1) Removed the attacking relays from the network.
  2) Put out a software update for relays to prevent "relay early" cells
     from being used this way.
  3) Put out a software update that will (once enough clients have
     upgraded) let us tell clients to move to using one entry guard
     rather than three, to reduce exposure to relays over time.
  4) Clients can tell whether they've received a relay or relay-cell.
     For expert users, the new Tor version warns you in your logs if
     a relay on your path injects any relay-early cells: look for the
     phrase "Received an inbound RELAY_EARLY cell".

  The following longer-term research areas remain:

  5) Further growing the Tor network and diversity of relay operators,
     which will reduce the impact from an adversary of a given size.
  6) Exploring better mechanisms, e.g. social connections, to limit the
     impact from a malicious set of relays. We've also formed a group to
     pay more attention to suspicious relays in the network:
     https://blog.torproject.org/blog/how-report-bad-relays
  7) Further reducing exposure to guards over time, perhaps by extending
     the guard rotation lifetime:
     https://blog.torproject.org/blog/lifecycle-of-a-new-relay
     https://blog.torproject.org/blog/improving-tors-anonymity-changing-guard-parameters
  8) Better understanding statistical traffic correlation attacks and
     whether padding or other approaches can mitigate them.
  9) Improving the hidden service design, including making it harder
     for relays serving as hidden service directory points to learn what
     hidden service address they're handling:
     https://blog.torproject.org/blog/hidden-services-need-some-love

OPEN QUESTIONS:
  Q1) Was this the Black Hat 2014 talk that got canceled recently?
  Q2) Did we find all the malicious relays?
  Q3) Did the malicious relays inject the signal at any points besides
      the HSDir position?
  Q4) What data did the attackers keep, and are they going to destroy it?
      How have they protected the data (if any) while storing it?

  Great questions. We spent several months trying to extract information
  from the researchers who were going to give the Black Hat talk, and
  eventually we did get some hints from them about how "relay early"
  cells could be used for traffic confirmation attacks, which is how
  we started looking for the attacks in the wild. They haven't answered
  our emails lately, so we don't know for sure, but it seems likely that
  the answer to Q1 is "yes". In fact, we hope they *were* the ones doing
  the attacks, since otherwise it means somebody else was. We don't yet
  know the answers to Q2, Q3, or Q4.
08/28/13

Tor Usage goes UP PirateBay, Iran-Syria and Google-play Orbot

USCyberLabs Stats of the Tor Network Aug-27

USCyberLabs Stats of the Tor Network

gAtO hEaR _UPDATE-

Sudden rise in direct Tor users



On Tuesday 27th, Roger Dingledine drew attention to the huge increase of Tor clients running [14]. It seems that their number has doubled since August 19th according to the count of directly connecting users [15]. According to Roger this is not just a fluke in the metrics data. The extra load on the directory authorities is clearly visible [16], but it does not look that the overall network performance are affected so far [17]. The cause is still unknown, but there are already speculations about the Pirate Browser [18] or the new “anti-piracy” law in Russia which is in force since August, 1st [19]. As Roger pointed out, ?some good solid facts would sure be useful.?

[14] https://lists.torproject.org/pipermail/tor-talk/2013-August/029582.html

[15] https://metrics.torproject.org/users.html?graph=direct-users&start=2013-05-29&end=2013-08-27&country=all&events=off#direct-users

[16] https://metrics.torproject.org/network.html#dirbytes

[17] https://metrics.torproject.org/performance.html

[18] https://lists.torproject.org/pipermail/tor-talk/2013-August/029584.html

[19] https://lists.torproject.org/pipermail/tor-talk/2013-August/029583.html



Ever since the the NSA Prism program came out something else is going on in Tor. People want privacy and they will use anything they can to get it. Tor is one solution that a lot of people know about but there are other factors about the increase.

Piratebay.sx and it’s users are doing a lot more stuff with the new browser – There has not been a sustained increase in search traffic for the Pirate Browser on Google. Tor and “Tor browser” haven’t shown a spike in search, either. Could it be from users in Syria?  Also note that the Google Play Store has been unblocked in Iran, allowing distribution of Orbot/Orweb in that country to phones with the Play Store app installed (partial bootstrapping problem).

Syria had a spike from 1000 to 4000 but that’s a tiny fraction of the recent increase. Iran doubled from 4000 to 8000 which is also only a part of the increase. Is there a page listing each graph by country or overlapping them all?

The Tor Project also pushed out Orbot v12 to Google Play in the last few weeks – 2 separate updates. That would not account for all of the increase, but it could have prodded enough existing users who had not used Orbot in awhile to start the app up again. We have also seen about 75,000 new installs over the last 3 months.

So we have a lot of factors as the Tor network grows larger everyday- gATo oUt

 

08/5/13

Freedom Hosting Tor-WEBSITE List TANGODOWN

gAtO hApPy - Freedom Hosting is down and so with it lot’s of Pedo sites. all with one shot. So I got my little Tor Search Engine and I start to crawl and what do I find but all the sites that went down by the FBI. So here is the list of Sites that went Tango-Down. NEXT – gAtO oUt

Ref: http://www.twitlonger.com/show/n_1rlo0uu

http://www.independent.ie/irish-news/courts/fbi-bids-to-extradite-largest-childporn-dealer-on-planet-29469402.html

https://openwatch.net/i/200/anonymous-web-host-freedom-hosting-owner-arreste

https://blog.torproject.org/blog/hidden-services-current-events-and-freedom-hosting

UPDATE – http://gawker.com/the-attack-on-the-dark-net-took-down-a-lot-more-than-ch-1081274609

 

So gATo has and older sweep of Tor from my search engine Artemis – this information was compile from a crawl I did on – Date: Fri, 29 Mar 2013 01:40:02 GMT - These are some of the Freedom Hosting Websites that went down after the FBI search..

  1. http://javrwyokisx3do7y.onionSite Name – The Dreadful Onion Hunter « Login
  2. http://jd2iqa4yt7vqvu5o.onionSite Name – Simon’s Intel
  3. http://jmbhglerouvy523l.onion  – Site Name – Anon comments only | tornado front end
  4. http://l2zukdb5b2favsfc.onionSite Name – Caravana Brasil • Índice
  5. http://mpfmcnqpsdnkl4xv.onionSite Name – .onion????? ??? – PukiWiki
  6. http://mvvaxvztx5n3eb6o.onion -Site Name – UKetalar | UK Ketamine Vendor
  7. http://n2qxamb4ujm53cas.onionSite Name – Lista polskich stron – PB&M Wiki
  8. http://n2wrix623bp7vvdc.onionSite Description – Hosts a .onion site list and various .pdfs (Library Still Under Construction
  9. http://nb5df7xeas3zl3sf.onionSite Name – Login – Underground Market Board
  10. http://nemlq3kd36frgvzp.onionSite Name – TorLinks | .onion Link List
  11. http://nmzykxx2licxyyzg.onionSite Name – Linki sprawdzone (Strona 1) – Pedo – Polish Board & Market
  12. http://nvgrt5kmuzpl3hnd.onionSite Name – DeepChan – DeepWeb
  13. http://o2rtyxbz7og2deqp.onionSite Name – Collectors • Index page
  14. http://okrm3spsq7nvpfit.onionSite Name – .onion????? ??? – PukiWiki
  15. http://ont6bv4bg7rtgaos.onionSite Name – Lista polskich stron – PB&M Wiki
  16. http://p2uekn2yfvlvpzbu.onionSite Name – The USAHM Archive
  17. http://pdjcu4js2y4azvzt.onionSite Name – BlackBin » 3dcacd
  18. http://pibn3ueheubjxv2z.onionSite Name – Polska Ukryta Wiki
  19. http://pzxqeu6qtp7t3ule.onionSite Name – Fraud Network – Home
  20. http://qdsuildbdofkrhe3.onionSite Name – Simon’s Intel
  21. http://qubsrxat5qsaw5u5.onionSite Name – Lista polskich stron – PB&M Wiki
  22. http://quugalxmtpfwrq3q.onionSite Name – KindzazaChan
  23. http://r33rs4kqbjvdxuk2.onionSite Name – Blue Quarters Infoa kaikesta kivasta
  24. http://r4iayv6nhmuhsrbj.onionSite Name – BlackBin » 3dcacd
  25. http://raybmwtjbor4ohvy.onionSite Name – ???? – Total Sites found retrivied : 4
  26. http://rhhkpum6v7hsqgjr.onionSite Name – Millennium Board • Index page
  27. http://s3dm26yr6kn3bxxl.onionSite Name – OnionCams
  28. http://s4pcptjvqizvpp72.onionSite Name – r/Onions: Welcome to the forum
  29. http://shxdhomhggy3bjrn.onionSite Name – BlackBin » 3dcacd
  30. http://slnlvwr4w6g5hnmw.onionSite Name – Lain Iwakura | Wellcome ;)
  31. http://srf2tcjadsfbat7m.onionSite Name – Extasy 120mg (Strona 1) – [Sprzedam] (N) – Polish Board & Market
  32. http://tgy3onlg42ya3p7d.onionSite Name – ????
  33. http://ttqjkuslnsvcyyoq.onionSite Name – QTL CORNER • Index page
  34. http://u3dqz36dcvhwd7kv.onionSite Name – Area51 Archives – Contact
  35. http://uaga3aoawaj6hohg.onionSite Name – Otwórz oczy – blog dla ludzi z otwartymi umys?ami [light edition and backup for uaga3aoawaj6hohg.onion]
  36. http://vh6o6cl2w5b3owcx.onionSite Name – Lista polskich stron – PB&M Wiki
  37. http://vjelr2xdaqsgslzr.onionSite Name – Lista polskich stron – PB&M Wiki
  38. http://vs5hb2ybldb4gfja.onionSite Name – 3D Boys • Index page
  39. http://w56hjpxn45yzohqa.onionSite Name – Lista polskich stron – PB&M Wiki
  40. http://wcgk6z6zgem7gq2w.onionSite Name – hex space – ./releases
  41. http://wf4df37hrebhwzts.onionSite Name – Web Design Guidelines: Onionland Style
  42. http://wf74ekmmmgg2pe3v.onionSite Name – The TorBack Machine
  43. http://wkwjr7pn7xubtpx5.onionSite Name – TCF • Index page
  44. http://wsqz4lkgroflknik.onionSite Name – NBPP < Narodowy Bank Polski Podziemne
  45. http://wuakd3inzzy5iz4w.onionSite Name – HAPPY BIRTHDAY, PSC (and other animals)
  46. http://wvioni5lrle3z3z7.onionSite Name – Forum of GnoM • ??????? ????????
  47. http://wwth5ym23tqpyu7i.onionSite Name – Acrimonious 2
  48. http://wznf5ffcbr3x62gj.onionSite Name – The Gates To The Clos Network
  49. http://x3zrcuuaa3oryn3h.onionSite Name – Paradise Village • Index page
  50. http:///x4tmhtkin4kumdvl.onionSite Name – Useless – A small lightouse in a sea of shadows
  51. http://x64n42mkjidmy2zr.onionSite Name – Simon’s Intel
  52. http://xc24qhihksrlpocj.onionSite Name – Difference between revisions of “Marketplace Reviews” – The Hidden Wiki
  53. http://xfq5l5p4g3eyrct7.onionSite Name – Aerie
  54. http://xlmg6p4ueely7mhh.onionSite Name – Lista polskich stron – PB&M Wiki
  55. http://xlvbli7pmkw652f6.onionSite Name – Drugs – The Hidden Wiki
  56. http://xnujexyz4hdqsbux.onionSite Name – Image uploader
  57. http://xxieg3mbvoh26pvs.onionSite Name Blue Quarters Infoa kaikesta kivasta
  58. http:///xyjkasecb4ztzq3o.onionSite Name – LEEME
  59. http://yc7be7ylkpb75rwn.onionSite Name – Looking for “Sexual abuse” book
  60. http://ygumyapuudqjnbbm.onionSite Name – Notes // TORtiglione
  61. http://ytjyark4csajcgvv.onion  – Site Name – BlackMarket Reloaded v.3 — Login
  62. http://zgqlqqxvor2jlz6p.onionSite Name – Lista polskich stron – PB&M Wiki
  63. http:///zntpwh6qmsbvek6p.onionSite Name – BlackBin » 3dcacd
  64. http://627kx22vati6uqkw.onionSite Name – SITES DEEP WEB – POR: ANONYMOUS BRASIL DEEP
  65. http://javrwyokisx3do7y.onionSite Name – The Dreadful Onion Hunter « Login
  66. http://tgy3onlg42ya3p7d.onionSite Name – ????
  67. http://uaga3aoawaj6hohg.onionSite Name – Otwórz oczy – blog dla ludzi z otwartymi umys?ami [light edition and backup for uaga3aoawaj6hohg.onion]
  68. http://xxieg3mbvoh26pvs.onionSite Name – Blue Quarters Infoa kaikesta kivasta

 

Artemis Tor Search Engine -uscyberlabs

Total Sites found retrivied : 219

search request : Down for Maintenance

Site URL -http://javrwyokisx3do7y.onion

 Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 00:53:53 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jchlju4s5zi5i425.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 00:54:22 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL  -http://jd2iqa4yt7vqvu5o.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 00:54:27 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jdcbespbl5j7v44x.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 00:55:02 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jhvtsdbtxb36bekb.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 00:55:42 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jm6miyk4tog63kqs.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:00:12 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jmbhglerouvy523l.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:00:16 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://jpjyhljziw2glwfg.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:06:00 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://l2jd3hd3cylog2oo.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:07:10 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -

http://l2zukdb5b2favsfc.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:07:18 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://l4tay4mx3vyjdn4i.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:07:22 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://lh2gj4qukxbsuwc2.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:15:13 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://lhhu2bf6stxpxpy6.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:15:24 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://li4znmlobepdaq4n.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:15:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://ljswg3wnxiaizan5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:16:07 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

 

Site URL -http://lq3d44brvxaqcpxb.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:20:12 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://lrp34bqzebcckrhj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:20:40 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://lttmmicbamgi3bj6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:21:30 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://lucg2zbpvrdwibj4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:21:42 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://mankbysii63gezac.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:24:15 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://mc2wqhlkh6ffgrdi.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:24:39 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://mnnyehhdfz3uxlvl.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:34:08 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://moblogep6k6xtxkv.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:34:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://mpfmcnqpsdnkl4xv.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:35:06 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://mqv7qz5rn3sf5dcx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:35:12 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://mvvaxvztx5n3eb6o.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:42:14 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://mxdcyv6gjs3tvt5u.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:42:19 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://n2bbo2lemmkerbad.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:42:32 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://n2qxamb4ujm53cas.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:42:42 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://n2wrix623bp7vvdc.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:42:45 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://naot2jryja6iyrp5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:44:32 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://nb5df7xeas3zl3sf.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:44:49 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://nemlq3kd36frgvzp.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:45:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://ngippawdykoexqd5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:46:14 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://niqsdvceafthxltd.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:47:35 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://nmzykxx2licxyyzg.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:48:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -http://npzz4sxul5xc3bfs.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:49:47 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://nsurytno7mrou27e.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:50:48 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://nvgrt5kmuzpl3hnd.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:51:03 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://o2kythe72mxejhvc.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:52:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://o2rtyxbz7og2deqp.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:52:46 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://oa54p2fphd4v47la.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:53:53 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://okrm3spsq7nvpfit.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:57:00 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://okx5b2r76olbriil.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:57:06 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://olfr5bg4qeliapk4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:57:20 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://oltdqzgjm45ito7y.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:57:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ont6bv4bg7rtgaos.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:57:54 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://oqgm7fsraxpmxmrg.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 01:59:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://otncjl62vae56kjr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:00:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://oyo4xpwdcqi3756j.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:01:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://p2uekn2yfvlvpzbu.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:02:47 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://p43g3uyr4dhneura.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:03:15 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://p7d2k2xiioailnuu.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:03:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pdjcu4js2y4azvzt.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:05:26 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pdjfyv7v3pn34w4f.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:05:35 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pibn3ueheubjxv2z.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:07:23 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://piuo6r5pdufquf4a.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:07:47 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pjlrfaiaf54udgur.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:08:31 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pm6hsbvjzn465slc.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:09:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pnunpbo4fu3v2z7d.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:09:33 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pnvdkz37btvugjmn.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:09:39 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ps6xx5frz4rrehqf.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:10:35 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pvqxjute5g7pud5y.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:11:42 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pw5odgnkkhsuslol.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:11:53 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pz65gyca5nrafhrf.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:12:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://pzxqeu6qtp7t3ule.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:12:30 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://q2vaheze7cac233x.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:12:57 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://q5p4f5mpdllehuso.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:13:41 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://q6nj2sa6jcey4x5j.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:13:49 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qaxjzemp2fhnwlhk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:14:11 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qcm4dybhodclkxo6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:14:32 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qdsuildbdofkrhe3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:14:41 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qhkt6cqo2dfs2llt.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:15:45 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qjd7zljc7gsj4uzc.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:16:27 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qjhz7mkia4awr27y.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:16:42 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qubsrxat5qsaw5u5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:20:51 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://quugalxmtpfwrq3q.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:21:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://qwzxutjnfqnragyb.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:21:49 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://r2tjckbrme3yeenx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:22:37 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://r33rs4kqbjvdxuk2.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:23:20 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://r4iayv6nhmuhsrbj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:23:52 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://r6fpezhksmtvp6x4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:24:21 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://raybmwtjbor4ohvy.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:24:34 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rfo6jgvvplkusqtj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:26:29 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rhhkpum6v7hsqgjr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:26:52 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rqc3gg6xji6jpovo.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:28:31 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rty45i3444aiu6d5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:30:14 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rwzcxzghu5gkrr5k.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:33:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rxhricqcqxv43kpn.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:33:57 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://s2s2snxbkbrphic2.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:34:28 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://s3dm26yr6kn3bxxl.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:34:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://s4pcptjvqizvpp72.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:35:22 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://s7nbvdbky4xqim7h.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:35:55 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://s7pvraehwqmazmcy.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:36:02 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://shxdhomhggy3bjrn.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:38:07 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://slnlvwr4w6g5hnmw.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:41:29 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://srf2tcjadsfbat7m.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:43:35 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ssx46oqheovkkwda.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:44:37 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://svirqksnu3skilyk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:46:00 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tgy3onlg42ya3p7d.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:55:28 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tjbxptkkgx2qmeqz.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 02:57:54 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://to4fqqlxfxjlyax4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:00:03 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ton5mkxr2for63mk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:00:10 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tovfhccd4sv3kez4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:04:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ttqjkuslnsvcyyoq.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:05:29 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tw2d3sglwcxryv67.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:06:02 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tydgccykixpbu6uz.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:06:29 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://u3dqz36dcvhwd7kv.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:08:10 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://u3rxbq6aeen7fin3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:08:15 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://uaga3aoawaj6hohg.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:09:26 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://uc7d6nma5ysmomzx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:09:47 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ugh6gtz44ifx23e7.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:10:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ukztfcd2vhjzb6o4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:11:09 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://unqs7ahehibxlio6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:11:48 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://uo5y56hp6yi227am.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:12:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://uqtinqynmibpoa2s.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:12:58 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vg7ik2tbrkjr5ooq.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:17:39 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vh6o6cl2w5b3owcx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:17:54 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vi653vmkfowqjpks.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:18:02 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vjelr2xdaqsgslzr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:19:01 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vq4r65jprehynwkz.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:20:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vqub2bfxkicnj2lj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:21:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vqvup2emge47qrzk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:21:10 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vs5hb2ybldb4gfja.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:21:45 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vu5qq342lwg6rwfs.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:21:55 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vzpzbfwsrvhfuzop.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:25:22 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vzugfdoygasghjsf.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:25:30 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://w3s2fbzewxcm6clr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:27:53 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://w4b46jaqe3pgsvnf.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:28:03 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://w56hjpxn45yzohqa.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:28:51 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wanm73tb2t6f3fc3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:30:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wcgk6z6zgem7gq2w.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:31:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wd5pbd4odd7jmm46.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:31:18 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wenw5jzs23nkqo3l.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:32:01 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wf4df37hrebhwzts.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:32:07 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wf74ekmmmgg2pe3v.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:32:14 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wi7o5wxt4ked7soq.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:33:32 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wihwaoykcdzabadd.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:34:13 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wjngphmzk6mr2pt5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:34:20 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wkwjr7pn7xubtpx5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:34:26 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wmuzclidgchmwq5p.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:34:40 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wp5vxuulb7unmv2o.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:37:12 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wsqz4lkgroflknik.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:38:06 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wuakd3inzzy5iz4w.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:38:43 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wvioni5lrle3z3z7.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:38:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wwth5ym23tqpyu7i.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:39:16 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wx7qk7n2jftuzxwq.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:39:35 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wznf5ffcbr3x62gj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:40:53 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://x35jfacrznhhtrfr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:41:43 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://x3zrcuuaa3oryn3h.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:42:03 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://x4tmhtkin4kumdvl.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:42:18 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://x64n42mkjidmy2zr.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:42:24 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xc24qhihksrlpocj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:43:36 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xdevzhvavwf5v5f3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:44:25 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xfq5l5p4g3eyrct7.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:45:38 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ximqy45aat273ha5.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:46:14 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xlmg6p4ueely7mhh.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:47:24 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xlvbli7pmkw652f6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:47:44 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xnujexyz4hdqsbux.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:51:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xqbaxtycj7q3cspa.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:52:03 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xsin4xbme24aatvk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:53:58 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xwap3uv7n4sz6wpt.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:55:17 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xxieg3mbvoh26pvs.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:55:52 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://xyjkasecb4ztzq3o.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:56:28 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://y47ylcppnh3afqk4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:57:55 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://y4bzva6k3l2l7rla.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:58:02 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yc7be7ylkpb75rwn.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 03:59:49 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yebxw62uunkieje6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:00:57 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yewmggktmoycxzsg.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:01:39 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ygumyapuudqjnbbm.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:01:46 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yhngvp3q5h4s7d3e.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:04:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yj2nu2qygzpjcglm.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:06:12 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yj4v76ad3sulvilj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:06:39 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://yl2wafirpac6rtqz.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:10:00 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ylltcdactxddhgd2.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:10:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ysviberpagxmgt7g.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:12:34 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://ytjyark4csajcgvv.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:14:43 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://z6qlj4w4zixfhfcp.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:19:00 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zep6wjf7aanbvcqp.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:22:36 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zgmxllflvb7oza7t.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:22:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zgnbvbgfmoew7uz3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:23:04 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zgqlqqxvor2jlz6p.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:23:24 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zitanihpqsvi2lav.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:23:59 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://zkfe63att7pa3r7i.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:24:30 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://znegstqkxqrdflol.onion

 

       

Site Name – Temporarily Offline

Site URL -http://zntpwh6qmsbvek6p.onion

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:25:24 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://zozc3heiykckew4z.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:26:13 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://zqhu3ynqqbqzsq2c.onion

Site Name – Temporarily Offline

Site URL -http://zx62pqwg3e7ha5x2.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 04:29:47 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://3bqvjtimcrvz4ajo.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.1 503 Service Temporarily Unavailable Server: nginx/1.4.2 Date: Sat, 03 Aug 2013 05:46:05 GMT Content-Type: text/html Content-Length: 447 Connection: keep-alive ETag: “51fb220d-1bf” Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://627kx22vati6uqkw.onion

Site Name – Temporarily Offline

Site URL -http://67ngzk5gmqjhbgy5.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 06:46:16 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://6s3ykalgzmbz4et7.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 06:51:04 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://buxyqg2rset5mmq6.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 07:38:52 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://dhuuinidbshqb2cx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 08:19:24 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://hlufpdgdnvsocgx6.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 09:55:23 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://iimwxobbbdlhobhx.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 10:12:32 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://javrwyokisx3do7y.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 10:29:08 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://q5p4f5mpdllehuso.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 12:48:10 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://rfo6jgvvplkusqtj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 13:07:19 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://tgy3onlg42ya3p7d.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 13:46:12 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://to4fqqlxfxjlyax4.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 13:54:30 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://u3rxbq6aeen7fin3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:04:06 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://uaga3aoawaj6hohg.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:05:53 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vqub2bfxkicnj2lj.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:38:25 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://vqvup2emge47qrzk.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:38:40 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://vu5qq342lwg6rwfs.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:41:51 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://wanm73tb2t6f3fc3.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:46:47 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.         Site URL -

http://wuakd3inzzy5iz4w.onion

 

       

Site Name – Temporarily Offline

 

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 14:59:16 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://wznf5ffcbr3x62gj.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 15:05:57 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://xlvbli7pmkw652f6.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 15:21:10 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://xwap3uv7n4sz6wpt.onion

Site Name – Temporarily Offline

Site URL -http://xxieg3mbvoh26pvs.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 15:32:57 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://yhngvp3q5h4s7d3e.onion

Site Name – Temporarily Offline

 

  Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 15:41:26 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

Site URL -http://zgnbvbgfmoew7uz3.onion

Site Name – Temporarily Offline

Site URL -http://zitanihpqsvi2lav.onion

Site Name – Temporarily Offline

Site URL -http://zqhu3ynqqbqzsq2c.onion

Site Name – Temporarily Offline

Site Data – HTTP/1.0 503 Service Unavailable Date: Sat, 03 Aug 2013 16:06:33 GMT Server: nginx Content-Type: text/html Content-Length: 444 Connection: keep-alive Proxy-Connection: keep-alive Temporarily Offline Down for Maintenance Sorry, This server is currently offline for maintenance. Please try again in a few hours.

®™ Dark Web Project Copyright © amores 2013

http://uscyebrlabs.com -gatomalo -

03/10/13

Finding the Bad Guy’s in Tor -triangulated irregular network

gAtO ThInKiNg - a car GPS works very simple, It takes the delay time from one geo-positioned satellite and compares is to another geo-positional satellite and estimates the position of the GPS in my CAR – I think they call it satellite triangulation or something cool, it’s been done with radios to guide pilots navigate ever since they developed radios. We do it with satellite and we can use networks too.

triangulated irregular network  -So now apply this to the Tor bad guy’s websites- a hidden service!math_clouadTag

With a simple command you can get the time it takes to crawl a website, so you have one server in the U.S one is South America, one in Europe and one in Asia and we run the same command getting the delays from each location. I bet with a little math and some basic network tools we could figure out the geo-location of any given website in Tor. One of my good mentors told me that in my crawls I was capturing timing information, we all see timing information with a simple ping command in the clear web but in Tor – UDP is unsupported so it does not work -//- we must take into account the Tor network thru-put and utilization bit that’s easy to get from a number of Tor tools.

Reverse triangulation of a network server should be easy to find with a little math, just take a good sample and the longer you wait the more data you collect and the better the chance you can find a geo-location of a website. We do this in the clear web all the time we can see bad areas of the world that are bad spammers, and other like mail from Africa Prince Scams offering you millions if you send them some money to cover the transfer, or Russian and Chinese phishing attacks. So we know geo-location and some IP are more prime to bad actors and we can draw a profile, a geo-location of a place and/or  country or an ISP so not having the IP of a Tor server may not be neededto find them we could use network triangulation. “triangulated irregular network  ” So the same thing can be done with networks and timing delays of data back and forth from a // client <–> Tor OR <–>server.

I got a crazy Idea that may or may-not work, but it sounds good—//  so— Now if I can only find a government grant and a good math major to help out and we have a big business model to find the bad guy’s geo-location even in Tor - gAtO oUt…

03/7/13

Mapping Tor Websites

gATo and fRiEnDs- are am now working on the Tor-Directory Project crawling about 2000 Tor-url and getting some new information about Tor and the sites that reside in the Dark Web. Example I got a good crawl from a site and I went to double check it and now it was down, so are the sites going up and down and online just for a period of time? Are the site not available because of the browser I am using -vs- my crawler. These are some of the answers I will find out.

I expected due to the slowness of Tor to spend a lot of time running these crawls. I have now a script that I can run in about 20hr or less and scrape about 2000 sites. I thought that the slowness of Tor-Dark Web would make this a real time eater but I am wrong. Another thing is the secret Tor sites I found, I now have a fingerprint on them and these sites that hide in secret on top of being in Tor are a real interest to me and others.

The main issue is Tor is not socks-http friendly so setting up the infrastructure was a real learning curve and now I can replicate the installation so as I get more servers online this will become a little easier. Right now I am mapping the sites so I can crawl every page, the good part and bad is I am finding more and more URL that I never thought existed, so the discovery of new URL is a good thing but once again the collection becomes a real bear.

I am putting this into a db to make the search of the collected data a little easier but finding that db programing on the web is well not very user friendly but I have a good partner that is fixing all my mistakes. We will house this new Tor-only website search engine in the clear web so we can keep the speed up and well people are scared to go into Tor, so why not keep everything in the clearWeb for now.

I expect the crawls to get much longer since I now have the urls to crawl every site a little better but the information and mapping out Tor will be and invaluable tool for us. You say how about the hidden wiki, and all those sites that have Tor directory wiki sites. Well they are OK for basic stuff but I am finding new sites I never heard of and the pedophiles are all over Tor so you best beware I am putting a light on your websites and the next part will be to stop you from using Tor as a play ground for your sick crap. Tor is meant for real needs of privacy and protection and I hope my work in this will get these sick bastards to run somewhere else — gATO is watching you in Tor so beware!!!

 

11/4/12

FBI and Cyber-Security oxymoron

gAto rEaD -The FBI is planning to have a geek squad to look for the coders of Botnets -WRONG they should go after the Bot’s and c&c already online—

Kevin Mitnick discounted the FBI’s plans to build a “cadre of specially trained computer scientists able to extract hackers’ digital signatures from mountains of malicious code.” – Kevin knows that hackers trade code and pick / slice and dice functions and code in hacker sites.

gAtOmAlO sAy’s

Some sites train n00bs – newbies bot-masters to send them out-/ they get caught and the commercial ones the ones that learned and survived share the knowledge.

“The signal goes everywhere and so do I” -gAtOmAlO -

We can’t stop the knowledge and we can’t stop the coders new ones come and go everyday – new ones quit and new ones start. Code is a function and the same function can be written in so many different ways.

Crunch away FBI scientist while new FUD mask the next wave of Bot-nets with a simple variant of Zeus or SpyEye and you got a new Bank attempt. They are all free in the wild so anyone that wants the code get’s it Free…. check YouTube guy’s “How 2 Zeus”

If you want to go after the Bot-nets you work with the front lines ISP and system admins – If the FBI would only tap into the FREE information that is available from some of the best minds. Just ask us and we will help. I hear Penetta Scream “Cyber 9/11” come on –If we need cyber security people  just go on LinkedIn and pick and ASK US we will help in ways that you have no idea.

Crowd source problems into the web and see who comes up with a solution to a problems- we have so many new ways to use the masses of people in cyberspace and social media to help and protect not just our country but we can help any other country as we learn more about cyber security. We are your biggest problem and your biggest solution to the cyber security problem…

Sorry gATO’s dealing with the FBI and the lack of respect they give people that help them, makes me sick. But keep on- keeping on FBI -and the rest of the White Hats – don’t you see, open your eyes…where here to help -gATO OuT 

FBI cybersecurity shift draws skepticism from experts

Kevin Mitnick, the former hacker turned security consultant, is one who doubts focusing on criminals rather than attacks would slow them

http://www.csoonline.com/article/720331/fbi-cybersecurity-shift-draws-skepticism-from-experts

10/22/12

Diary of a Professional Botmaster

gAtO -found this and had to share with you. If you want to know how a botMaster is created check this out. A simple software engineer becomes a botMaster sounds like “surreal Walter White in Breaking Bad”. First you will noticed that this was written in 2010 and it’s been a model of the botMaster persona. This is a fictional tale now add the Tor onion network to hide the c&c and mobile Android /iApple devices but it comes so close to the real edge, have fun reading -gAtO oUt

Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

 Diary of a Professional Botmaster 

June 20, 2009 

I’ve decided to restart the diary. I used to keep one many years ago, but stopped when I moved down to London and started my MSc in Computing & Security at King’s College – much use that degree ever turned out to be!

I found out yesterday that me and most of the team are going to be made redundant at the end of the month. It appears that the company doesn’t need so many developers after they decided to sell off the Private Banking division to some German brokerage and they ditched those annoying trader guys up on the 18th floor a couple of months back.

Anyhow, I’d better start looking for a new job. The markets pretty tight at the moment. It seems that all the banks are laying off folks and the developers are the first to go. Not surprising really. I’ve been thinking about setting up my own business for a while though. Perhaps it’s time to bite the bullet and just do it. Take that redundancy cheque and invest it in myself?

June 22, 2009 

Was down at the pub for most of the afternoon with Bill & Ted. We were tossing around ideas of businesses I could start – in particular, businesses that could make me a millionaire in a year’s time. Granted, most of the ideas were completely off the wall and would be destined to fail or end in my bankruptcy within weeks of starting them (or would likely land me in prison within short order) but some of the grey areas look like they could be pretty exciting.

Ted was going on about botnets and how they’re not really illegal. Sounds like rubbish to me, but I’ll check it out anyway.

Last year when we had that worm go around the office and the Ops guys spent a couple of weeks chasing it down and cleaning up systems – that was pretty cool, and I can see how the authors of that worm could make quite a bit of money from it with a little banking knowledge. I don’t think they ever got caught either. Ted told me that James – the lardy guy over in second-level helpdesk – said that they were still having outbreaks of that very same worm and uncovering other infected computers almost every day (after an entire year). How cool is that!

June 25, 2009

I’ve been reading up on botnets. The Internet is full of great information about them. YouTube even has tutorials on how to create the malware, deliver the bot agents, manage the Command and Control (CnC) and turn the stolen data into real money.

I did some digging on these hacker forums too. They’re pretty cool. Most are well organized and there are bundles of tutorials, guides and discussion threads on all aspects of the botnet business. There’s even entire forums dedicated to matching buyers with sellers – Craigslist style! Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

June 26, 2009

Had a great session with Demitri over IRC today. He’s been running a handful of botnets over the last couple of years and seems to know what he’s talking about. Came across his advertisement on one of the boards and was offering a free 2-hour test-drive of his botnet CnC console – so I got to play with a couple hundred computers. Some of the functionality was grayed out, but I got a chance to DDoS the companies’ website – from the comfort of my desk ?

I spoke with a couple of the company Internet ops guys afterwards – being careful in what I said of course – to see if they noticed. Apparently they did. It didn’t bring down the site, but they were alerted from their IPS. Supposedly this is a common enough occurrence and happens most weeks. I guess I’m a little disappointed with that. I wonder how many bots I’d need to take down the webserver?

Dimitri said that he normally uses about 5,000 bots to take down big websites – but 200 is more than enough to wipe out corporate VPN appliances. Handy to know!

June 27, 2009

Sat down with Jim the lawyer this afternoon. I wanted to go over the details of setting up my own contracting business. Since I haven’t had much luck on the replacement job front looking for permanent roles, I figured I’d just go down the contracting route – since there are more opportunities going for temporary software engineering positions.

There’s not much to creating your own business. Jim helped me with all the forms – so I just need to mail them off tomorrow, and I’ll be on the way to creating my first business. He also explained some of the nuances to setting up a company in some other countries and the possibilities of “offshore accounts” and tax havens. I took plenty of notes. You never know when that’ll come in useful.

June 28, 2009 

Spent all day harvesting hacker boards for tools and playing with them on a couple of old laptops. This stuff really is easy.

I even came across this guy(?) on one of the chat forums (who can’t have been more than 14 years old) who was selling a botnet of 2,000 computers for $400. The funny part though was when the flame war stated about how overpriced that was. Apparently you can pick up 2,000 computers for as low as a $50 Walmart giftcard.

June 29, 2009

I woke up this morning with an epiphany (or was it just a delayed hangover?). I’m going to start my own botnet – but not just any botnet, I’m going to do it properly and make a business from it! I’ll still pursue any legit consulting roles that crop up – still got to eat and pay the bills – but it’ll make a convenient front while I’m building botnets.

Why the botnet business? Because it’s cool! Well, actually, it’s more than that. I don’t want to work forever in a dull office job and, from what I can tell, botnet building seems to be pretty profitable – and not many people get caught. And, if they do get caught, they basically only get a slap on the wrist. Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

Having read quite a few of the news articles about the folks that got caught, it looks to me that they got caught because they did something stupid and/or they clearly crossed the criminal line – and the police were forced to do something about them.

I’m pretty sure that I’m smarter than that. Didn’t any of these guys ever consider building a business plan first? Plan it all out – have a strategy and stick to it!

I’ve left the computer downloading a few tool collections I found on one of the Argentinean malware blog sites. 4Gb of tools, kits and exploits. Awesome! And it’s all free!!

June 30, 2009

Final pay date from the “old job”, and I’m now officially free of the company. Ended up with a little over £35k after taxes too – so that’ll tide me over the next few months as I pull together my new business(es).

Last night’s download worked out pretty good. There are hundreds of botnet kits in there – complete with CnC interfaces, exploit packs, phishing templates, malware creators and obfuscators. Supposedly there’s a high likelihood that many of them are backdoored, but who cares – it’s time to play! I’m going to try a couple of them out on the corporate laptop before I have to hand it back – preferably one with a good rootkit. I wonder if they’ll ever notice?

July 1, 2009

Woke up this morning having dreamed about what kind of botnet business I want to build. Also figured out a few “rules” that I want to work towards – maybe more of a “guiding principles” perspective really.

1. DON’T GET CAUGHT – which means I’m going to be damned careful in setting up everything and making sure that nothing can be traced back to me personally. Sure, there’ll be layers to the onion, but I’m not going to allow myself to be let down by poor tradecraft and bad habits. Those hackers in France and Spain got caught because they didn’t have enough layers of deniability and mixed the use of their personal systems and their botnet infrastructure.

2. DON’T DO CRIMINAL HARM – While I’m pretty far removed from planning on being a Robin Hood, I’m not going to get mixed in with the Mob or other organized crime. Similarly, I’m not going to get involved with any political or religious drivel. I also don’t want to cause any physical harm – as that’s a sure way of getting the interest of the police – and, besides, it’s not who I really am. The more legit I can make this business, the easier it’ll be to bow out after I’ve made my money.

3. RESILIENCE AND SCALABILITY ARE MY FRIENDS – Since this is going to be a business, based upon the lessons I learned from the Private Banking firm and all I’ve been reading over the last couple of weeks, it should be possible to build pretty big botnets really fast – if I plan it well.

Resilience will be even more important though. Getting back to the “don’t get caught” principle and the layers of deniability (and abstraction), if I plan for making the CnC and distribution systems robust, I’ll endeavor to split things over Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

several hosting providers and geographic regions.

Also spent some time on the hacker portals and responding to some of the threads. Some of the more interesting forums are currently closed to me because I haven’t developed a site reputation – which can be gained by posting 20, 50 and 100 messages. This’ll be pretty easy though. Lots of questions about coding problems which I can answer without too much thought.

July 3, 2009

I think I’ve managed to plan out a few more CnC infrastructure ideas. I found a few more tutorials online – and also some good message threads on domain registration tactics, Dynamic DNS operators and folks that’ll distribute malware for a few cents. It appears that a good rate at the moment is around $100 for 2,000 guaranteed installs. A little pricey if I was buying, but it sounds like good money if I was to become a seller ?

I also realized that I forgot a rather important principle for inclusion – my zero’th principle…

0. I WANT TO BE RICH – but, more to the point I want to retire rich, not be the richest bloke in jail.

Which all means that I need to do some more investigation on how to secure the money. I don’t want the money to be directly traceable to me – nor to the consulting company I’ve just created – but I’m going to need ways to pay for stuff and ways to accept payments. All deniable of course.

Made a few new connections on the hacker forums. Now that I’m posting to some threads I’m getting direct messages from some of the folks there. A couple of the guys that reached out were trying to pimp out their services – both of them malware dropper services. Someone else asked if I was with the FBI.

The USA perspective was interesting. I hadn’t realized that the guys on the forums can see/track my IP address and from there work out where I’m located. I’ll have to do some experimenting with anonymous proxies and TOR networks. I ran across a few video tutorials on the topic yesterday. That’ll be my homework for this evening – getting something setup and hiding my IP address forever more…

July 4, 2009 

Surprise in the snail mail – company papers just came back. I’m now the CEO of Thrull Networks! Cool company name huh! I wonder if anyone will ever figure it out – thought it was apt at the time. Maybe it’s a little too close to the mark. 5% on the dumbness scale I guess. Will have to be smarter in the future. I’m going to keep it though. Even saw that some related .com and .net domain names are available for registering.

Earlier this morning I went out and bought a couple of new laptops. Nothing special, just some small(ish) $800 laptops that I’m dedicating to my botnet business – and will never taint them with the Thrull Networks consulting business. Although I will be claiming them as tax deductable expenditures. Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

Also spent most of today coming up with the rules I’m going to work under for achieving principles (1) and (3)… and maybe a little of (0) too.

So, the new rules…

A) Separate systems for work/pleasure/personal and botnets. The two new laptops are JUST for the botnet business. I’ve already installed a full disk encryption scheme and come up with a 44 character password. I doubt that anyone’ll be breaking that mother anytime soon.

B) Never connect to the botnet CnC or do any botnet-related business from my home network. Given the general availability of free WiFi at Starbucks and McDonald, etc., I’ll use those. A couple of additional rules there though – don’t frequent them in a regular pattern (sounds like a Tom Clancy spy novel), and don’t use stores that have CCTV setups. I was tempted to use some of the unsecured WiFi networks in the neighborhood – but that may be a little too close for comfort. Besides, the coffee will be better than what I have at home.

C) Change the MAC on the laptops regularly. I’ve already downloaded and installed a cool piece of software that does precisely that. I’ve also installed a bundle of different Web browsers – but have deliberately not installed any plug-ins etc. I was reading recently a couple of online projects that showed how they could query your Web browser through JavaScript and the DOM to build a signature of the browser – and how “unique” that became once you started installing plug-ins and how regularly you kept them patched. So I’m planning on keeping the laptops as simple and “dumb” as possible.

D) Never connect directly to the botnet infrastructure. Lesson learned yesterday. TOR and anonymous proxies are now default on all my computers – especially the two new laptops!

E) While encryption is my friend. Asymmetric crypto is going to be my live-in lover. Thanks Bruce for the tips!

July 9, 2009

Been playing around all week with the DIY kits I downloaded a couple of weeks back. The Zeus kit is pretty impressive with its polymorphic malware generator. I was running its output past some of the free online antivirus scanning portals and noting which (if any) antivirus tools detected the samples. On average, only a couple of the AV tools detected anything – and if they did, it was only some kind of generic signature such as w32.suspicious etc.

I was originally using www.virustotal.com, but when I tried to find other AV portals that might have more AV products in them I stumbled over a couple of cool threads that explained why I shouldn’t use that site (and a few others) because they share the malware samples with the AV vendors. Therefore the AV vendors will have detection signatures for the malware out within a few days. That sucks – because I probably just wasted a few dozen cool pieces of Zeus malware. Luckily there were plenty of alternative AV testing portals being recommended and (yet more) tutorials on how to set up your own malware QA testing regimes. Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

I’ve settled on www.virtest.com now. They charge a few dollars for the privilege of testing the malware I submit, but they allow me to upload multiple malware samples simultaneously in bulk format. They also have some other services for checking out the malware delivery websites too – so you can check to see if the exploit packs used by the Zeus kit (and others) are correctly installed and whether the other AV components (e.g. HIPS) detect the infection. Their VIP account is $50 per month. I’ll have to figure out a good way to pay for the service. Something that can’t be traced back to me personally…

July 10, 2009 

I spent the entire morning down at the Starbucks down by the park using their “free” WiFi. Cost me about $26 in coffee for the 4 hours.

Anyway, I set up a handful of free webmail accounts. A couple of Gmail accounts, a couple of Hotmail accounts and a couple of Yahoo accounts. I entered in garbage “personal” information, but gave them all the same password – “Lucky4Me*Unlucky4U”. They’re disposable accounts for trialing out a few new concepts and learning what works.

Next, I created a couple of websites to host the Zeus CnC console pages. I had originally been worried about how I was going to have to pay for the web hosting – but a quick search for “free web hosting” revealed plenty of services – including portals that provide detailed reviews of all the providers. Woohoo.

It took me about an hour to create the sites on 0000free.com. It’s the first website I’ve ever built – and I had to learn some PHP while doing it all. On the job training if you like. The index page is just a copy/paste job from some car-parts website – and the Zeus CnC configuration and bot registration pages are off in a subfolder. They’re accessible if you know the URL, but they’re intentionally not linked to from anywhere. I don’t really want some search engine crawling the sites and flagging the Zeus CnC.

I’ll be spending some time later tonight generating some malware samples that’ll use the two new CnC URLs. That’ll be hard work – should take me all of 10 seconds ?

July 11, 2009 

A botnet is born. I’m a father!

So, this morning I headed off to the Starbucks over by the athletics center to play with my newly minted malware and the CnC services.

I originally set up a VMWare session on the laptop and infected it with the new malware bot agent and watched it reach out to the CnC server. Meanwhile I browsed to the website, logged in to the CnC console, and saw the test victim register itself – so I spent a good half hour testing out all the features of the bot agent. It’s pretty slick. Ugly, but slick. The toughest part of all this was setting up the TOR agent to provide the anonymous web access in reaching the CnC console.

To get the bot malware into play I decided to upload the samples to the Newsgroups – since they don’t require me to host the files directly and also provide anonymous Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

uploading. One file I named “Windows7KeygenCrack.exe” and the other “iTunesDRMRemover.exe”, and included some BS text about how good the tools are. They were both uploaded to a handful of different alt.binaries. groups using different email accounts and source IP addresses.

I hung around Starbuck for another hour, but didn’t see any victims appear on the Zeus console – so paid a visit to Bill & Ted and grabbed lunch with them in town. Ted’s already gotten a new job at some Scottish bank. Chose not to tell them about my botnet research. The ideas may have come from them originally, but I’m not about to share this secret.

Anyhow, I popped in to the McDonalds by the railway station at about 4pm and connected to the Internet to see how my “botnet” was coming along. Surprise, surprise, I had three new members to my botnet. How cool is that! I was well chuffed with that small success and subsequently spent an entire hour connecting to each computer and checking out what I could access on their systems. Just as I was about to pack things up and head off home a fourth computer joined my botnet.

I couldn’t stop smiling on my way home from McDonalds. I think I may have even said “I’ve just fathered my first botnet” somewhere on the walk up the hill. Haha.

Guess where I’ll be tomorrow morning…

July 12, 2009 

Got to Starbucks early this morning and was online with my baby botnet by at least 9:30am. It had swollen over night and the counter had reached 18 computers – but I could only contact 6 of them. The others must have been turned off or something.

For the next hour (and second cup of Java) I created a couple dozen new malware bot agents and configured them to point to the same two Zeus CnC servers I’d set up yesterday. I then went on to use the same Newsgroup tactics – but picking a few other juicy social engineering file names (and descriptions) – e.g. “AcrobatProfessionalKeygen.exe”, “RossettaStoneLanguagePackUnlocker.exe”, etc.

By the time I left the coffee shop the botnet had grown to 23 computers – mostly in the US and the Netherlands, but a couple from Australia and Taiwan.

Went home afterwards to do some more studying and recon, and found some good information on how to automatically pull back account and identity information from Zeus malware clients. There are a number of scripts that you could run automatically on each botnet computer to extract their webmail credentials, anything they’ve told their IE or Firefox web browsers to remember, etc.

I also found some plug-ins for the Zeus CnC console that help to manage the data that comes back from the keylogger and other info-stealer components – which I installed on the web servers later on my return trip to Starbucks – and left CnC commands for the botnet malware to automatically start collecting and uploading the identity information. Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

By 7:30pm my botnet had reached 200 members. It’s no longer a “family unit”; it’s a small village and I’m Pastor of the flock.

July 14, 2009

Had a couple of contract interviews yesterday, and hadn’t managed to check on how my baby was coming along for a couple of days. So, it was with a rather pleasant surprise I noted that the botnet had reached 3,320 computers.

Actually, I’m not so sure about the number and whether it’s a good number to rely upon. The number of computers “active” were about 450 – and I tested that I could control them OK. As for the rest, well, they were “offline” – but I did have files from all 3,000+ computers sitting on the CnC server – so I guess they were successfully compromised with my botnet agent.

I moved all the files off the two CnC servers and copied them to the laptop. When I got home I started doing some analysis.

Brief stats (for posterity)…

942 Facebook accounts

766 Twitter accounts

322 Gmail accounts

318 Hotmail accounts

193 Yahoo accounts

76 Paypal accounts

… and lots of sub-50 accounts – many for services/websites I’ve never heard of before. All told, about 5,500 different accounts.

BTW I’m not sure I like using Starbucks – I’m spending too much money on coffee there ?

July 15, 2009

The botnet’s now reached 4,000 computers.

There was an email from 0000free.com waiting for me from yesterday. Apparently I should be upgrading to a paid account because of all the traffic/hits the site has been receiving. Just as well I moved off all the identity information and files – I was almost over the file quota too!

July 16, 2009

4,300. What’s the population have to be before a village can be called a town?

Created another couple of dozen malware for release on the Newsgroups since the botnet growth appeared to be slowing down.

July 17, 2009 

I think I’m the Mayor of a small town now. I visited the Starbucks down by the strip mall this afternoon and logged in to the botnet. 11,435 computers!

At first I thought it may have been a mistake since the size jump was so large. Introducing a couple new malware downloads didn’t get that much of a leap last time. But I figured it out after about 20 minutes of probing and searching. It would seem that the new file “MichaelJacksonDeath-OfficialAutopsyReport.exe” was more successful. It also managed to make its way on to some Torrent server and plenty of people are downloading it.

New lessons learnt from yesterday’s efforts: Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

1) Tying social engineering to media and entertainment current events results yields more additions to a botnet.

2) Torrent networks can make the botnet malware reach more people faster.

July 18, 2009

Just as well I downloaded all those new files yesterday, because the botnet is dead. I’m no longer the Mayor.

This morning I popped on over at the Library for a bit of their WiFi access and tried to connect to my CnC servers. Nothing – well, more than nothing, the Zeus CnC pages had been deleted and my webserver account had been disabled. There were instructions to phone the helpdesk to discuss reactivation.

Waiting in the inbox of the webmail account I used to register the free websites was an email telling me that my site may have been hacked and was being used for malicious purposes.

A quick Google revealed that both CnC URL’s and configuration files were listed up on ZeusTracker.abuse.ch.

Bugger!

July 19, 2009 

All is not lost. I’ve still got all those identity/account detail files from all my botnet computers. The total – adding the first batch with the batch from the 17th – comes to a little shy of 19,000 unique sets of credentials. I can still access any (if not all) of those stolen accounts anytime in the future.

Better yet – there’s absolutely nothing that can be tracked back to me. Sure, the botnet is now out of my control (and computers are still being compromised with the malware which is still in circulation in the Newsgroups and Torrents), but I’m safe and have learnt a few new lessons.

That said though, it’s about time I started to focus on bringing in the money from the botnets. I’m not going to get that Porsche building botnets for botnets sake. I could easily enough find buyers for the stolen information – the hacker forums are overflowing with buyers and agents. That’s not a problem. The problem lies in converting “Internet money” into cash – and laundering those transactions sufficiently.

With that in mind, I spent all afternoon researching offshore banking and the creation of anonymous accounts. Disappointingly those infamous Swiss Numbered Accounts don’t exist anymore – at least not like they do in the movies.

I managed to narrow it down to three banking accounts and, as my finances grow, I’ll start to bring them on line. I’ve found agents that will allow me to set up Swiss banking accounts online. They require proof of address, but they provide a level of guarantee that personal information will not be supplied to anyone outside of Switzerland. The Cayman Island accounts are easier to set up – and don’t require an agent – but require a higher deposit. They’re a little too rich for my tastes at the moment – but I’ll probably add an account once I break the $100k per month revenue stream (if ever?). Becoming the Six-Million-Dollar Man Blackhat USA 2010 Gunter Ollmann 

No, the account I created online this evening was for a Panama Bearer Share Corporation account. As of an hour ago I’m now CEO of a second company – “Net Wizards LLC.”. I deposited $5,000 into the account. Not only does it provide an anonymous business front and full international banking facilities, but it comes with 4% interest and the credit cards issued against the account should be arriving in 10 days time.

July 20, 2009

I’m back in the botnet business!

I was keeping a couple of my hacker forum accounts live by responding to a few message threads and I stumbled across a couple of reputable botmasters that were in the process of selling off sections of their botnets. They were offering batches of 100 bots with dedicated CnC hosted servers for $200 each.

Most significantly though – there were alternatives to the $200 in Webmoney or PayPal funds – they’d accept hacked webmail accounts, Facebook accounts and Twitter accounts.

After a little back and forth, we agreed on the trade and exchange mode (had to use an agent that was pre-vetted on the forum – one of the administrators – who charges 10% for his time/effort). From X4cker I picked up 600 bots and two CnC servers (in the Ukraine no less) for 3,000 Gmail accounts and 1,000 Hotmail accounts. From Dankar007 I managed to procure 500 bots for the princely sum of 500 PayPal accounts. The site administrator/agent didn’t do too badly out of the deal either. I’m sure that he (or she?) now has his own copies of all those accounts.

After some quick verification and having tested the access to the two botnets, I created a new Zeus botnet agent and pushed it down to all 1,100 bots – and changed the admin credentials on the CnC servers.

Not only am I back in “business” with a brand new botnet, but I’ve still got all those account details from the previous botnet that I can continue trading/reselling to other operators.

— I just realized that this diary is now precisely one month old. In that month I lost my job, founded two companies, become a CEO, built a botnet, lost a botnet, established a reputation in the hacker communities, opened an international banking account, and just purchased my second botnet.

Time to start pulling together the business plan for constructing a profitable money-making botnet! The “march to a million” sounds like a great idea, but I’d prefer to aim for Steve Austin’s The Six Million Dollar Man. I’m pretty confident that I can reach that target over the next 11 months! What would mom say?

Original BlackHat PDF file –

http://media.blackhat.com/bh-us-10/whitepapers/Ollmann/BlackHat-USA-2010-Ollmann-6millionDollarMan-wp.pdf

ZeuS Tracker Statistics – https://zeustracker.abuse.ch/statistic.php

Note: This is a fictitious (and subtly macabre, but hopefully humorous) diary account loosely based upon real investigations of professional botnet operators and the criminal enterprises they created to monetize the data and systems under their control. It does not represent a single botnet operator, rather it represents a concatenation of notable business models, decisions and discussions from a spectrum of criminal operators. Names and places have been deliberately altered. No animals were harmed in the making of this diary.

 

10/13/12

Customized .onion URL Address

gAtO hAs- been looking for this golden grail —how to customize a .onion address  —  but nobody knew how to do it or would never tell. Job security I guess but as I have been in i2p land and not much on Tor but I found this link to Shallot in github.com from and i2p site about Tor and i2p. Well the jig is up. I understand why it may not be a good idea for a custom name – It’s all about math and every custom digit of the 16 digit .onion address takes more time to calculate when your onion ur;l is generated in Tor. I have a new toy for a Saturday night project – Well here it is enjoy it- gAtO out

https://github.com/katmagic/Shallot

Shallot allows you to create customized .onion addresses for Tor’s hidden services. (By customized, it is meant that part of the address can be selected. Choosing an entire address would take far longer than the universe is believed to have been in existence.)

A History of Shallot

Shallot has a long history in Onion Land. In its original incarnation, Shallot was originally written by a mysterious Onion Lander called Bebop, who created its predecessor, onionhash-0.0.1, at some unknown time in the distant past. That quickly(?) evolved into onionhash 0.0.2 and 0.0.3, until Bebop and Bebop’s New Home in Onionspace mysteriously vanished. At this point, it was picked up by `Orum, who gave Shallot its current name, and went through three versions until `Orum’s site, hangman – hidden (in plain) site, went down. I (katmagic) got Shallot’s sources from Tas’s site and put them into a Git repository. I made a few modifications, wrote a new README, and put the whole thing up on GitHub for all to see.

10/1/12

USCyberLabs has a hidden service Tor otwxbdvje5ttplpv.onion

gAtO wAnTeD – to get our USCyberLabs Tor .onion network -hidden service- up and running and after thinking of other future projects we decided to make our Ubuntu -BackTrack 5 machine be our Tor Server running apache2 hidden service  . My BT5 machine is running – Gnone v.2.30.2 Ubuntu build 06/25/2010 ?

Apache/2.2.14 (Ubuntu) Server at otwxbdvje5ttplpv.onion Port 80

1. First problem BT5 is designed to run as root and Tor is not so first thing is to generate a new user:

uscyberlabs - el gatoMalo

gAtO new hidden service otwxbdvje5ttplpv.onion

# adduser gato

# password gato-password

For help go to man adduser for more information

I open up terminal for everything so as SU -(SuperUser)

nano /etc/apache2/apache2.conf > file

nano /etc/apache2/ports.conf > file

nano /lib/tor/torrc -> file

nano /etc/host -> file

2. Before we change users and start to work as gato let’s set up the apache2 service

# apt-get install apache2

whizz, bang ,- wow and it’s installed next we need to modify some configuration files.

The Apache install will install /var/www/index.html <— so modify this file for your web site:

The Apache install will install /etc/apache2 and in it you will find a bunch of the configuration files:

apache2.conf and ports.conf these two files will have to be modified and Tor torrc file.

This is a great guide — from ioerror  —but don’t try the wiki – – https://github.com/ioerror/hs-wiki/tree/master/configs another guide not so good but it helped —http://www.martini.nu/blog/2010/06/tor-vbox.html    —

ports-apache2.conf 

12 NameVirtualHost 127.0.0.1:8080Listen 127.0.0.1:8080

torrc

123

4

5

6

7

8

9

10

11

12

13

14

# some information may be for future projects -# This is a very minimal Tor configuration file to be placed in# /etc/tor/torrc unless you know better.

#

# This configuration file should be used with a wiki Hidden Service on

# 127.0.0.1:8080

#

 

Log notice file /var/log/tor/wiki.log

DataDirectory /var/lib/tor

 

HiddenServiceDir /var/lib/tor/hidden_service/

HiddenServicePort 80 127.0.0.1:8080

Add your hidden Service Tor url to your host file – trust me this really helped during trouble shooting

I added my Hidden service onion ID to the

nano /etc/host -> file

127.0.0.1 otwxbdvje5ttplpv.onion 

I generated a few more hidden service keys to deploy some other sites later -Open up 2 more terminal windows – I can start stuff in background mode but during testing everything has it’s own terminal just in case.

To install Tor on unbuntu linux — https://www.torproject.org/docs/tor-doc-unix.html.en  —

To start Tor

./start-tor-browser

To start Apache web server

sudo /etc/init.d/apache2 start

I’m not going to give you my directory structure but just a heads up :

DataDirectory  /var/lib/tor/

HiddenServiceDir /var/www/web_hidden_service

HiddenServicePort 80:127.0.0.1:8080

Since I’m testing I log to my terminal but a log error file will work better

Log notice stdout

So ok now comes the test – I have a static html website – a hidden service in the Tor .onion network. I did not go to icann for an domain name and pay them- I don’t have to pay InMotion for hosting service – just my cox-internet connection and a spare machine and I have a website in the dark web – This machine will host other websites – hidden services like wordpress, a bb bulletin board- or maybe some other web service – It will host my BotNet for the Tor Directory Project – Oh yeah I want to build a few bot’s for GOOD and map out the Tor Directory and make each Bot an OR (onion Router) so it helps the cause and gives back a bit. I plan to also run OnionOO – Arm – Atlas – mOnionO Compass and Weather.

SO if your out an about in Tor Land come on by and kick the tires and peek and poke my Tor hidden service website – otwxbdvje5ttplpv.onion  if you find any openings let me know.pls As I add new features I will tell you about them -gAtO oUt 

09/28/12

Tor Command syntax

gAtO wAnT’s – just the simple command syntax -from the OG-OR Roger Dingledine -Nick Mathewson the Tor gods.

href=”http://manpages.ubuntu.com/manpages/hardy/man8/tor.8.html#contenttoc6″>

 

NAME

       tor - The second-generation onion router

SYNOPSIS

       tor [OPTION value]...

DESCRIPTION

       tor  is  a connection-oriented anonymizing communication service. Users
       choose a source-routed path through a set of  nodes,  and  negotiate  a
       "virtual  circuit"  through  the  network, in which each node knows its
       predecessor and successor, but no  others.  Traffic  flowing  down  the
       circuit is unwrapped by a symmetric key at each node, which reveals the
       downstream node.

       Basically  tor  provides  a  distributed  network  of  servers  ("onion
       routers"). Users bounce their TCP streams -- web traffic, ftp, ssh, etc
       -- around the routers, and recipients, observers, and even the  routers
       themselves have difficulty tracking the source of the stream.

OPTIONS

       -h, -help Display a short help message and exit.

       -f FILE
              FILE   contains   further   "option   value"   pairs.  (Default:
              /etc/tor/torrc)

       --hash-password
              Generates a hashed password for control port access.

       --list-fingerprint
              Generate your keys and output your nickname and fingerprint.

       --verify-config
              Verify the configuration file is valid.

       --nt-service
              --service [install|remove|start|stop]  Manage  the  Tor  Windows
              NT/2000/XP  service.   Current  instructions  can  be  found  at
              http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#WinNTService

       --list-torrc-options
              List all valid options.

       --version
              Display Tor version.

       Other options can be specified either on the command-line (--option
              value),  or  in  the configuration file (option value).  Options
              are case-insensitive.

       BandwidthRate N bytes|KB|MB|GB|TB
              A token bucket limits the average incoming  bandwidth  usage  on
              this  node  to the specified number of bytes per second, and the
              average outgoing bandwidth usage to that same value. (Default: 3
              MB)

       BandwidthBurst N bytes|KB|MB|GB|TB
              Limit the maximum token bucket size (also known as the burst) to
              the given number of bytes in each direction. This  value  should
              be at least twice your BandwidthRate. (Default: 6 MB)

       MaxAdvertisedBandwidth N bytes|KB|MB|GB|TB
              If set, we will not advertise more than this amount of bandwidth
              for our BandwidthRate. Server operators who want to  reduce  the
              number  of clients who ask to build circuits through them (since
              this is proportional to  advertised  bandwidth  rate)  can  thus
              reduce the CPU demands on their server without impacting network
              performance.

       ConnLimit NUM
              The minimum number of file descriptors that must be available to
              the Tor process before it will start. Tor will ask the OS for as
              many file descriptors as the OS will allow (you can find this by
              "ulimit -H -n"). If this number is less than ConnLimit, then Tor
              will refuse to start.

              You probably don’t need to adjust this.  It  has  no  effect  on
              Windows since that platform lacks getrlimit(). (Default: 1000)

       ControlPort Port
              If set, Tor will accept connections on this port and allow those
              connections to control the Tor process  using  the  Tor  Control
              Protocol (described in control-spec.txt).  Note: unless you also
              specify one of  HashedControlPassword  or  CookieAuthentication,
              setting  this  option will cause Tor to allow any process on the
              local host to control it. This option is required for  many  Tor
              controllers; most use the value of 9051.

       ControlListenAddress IP[:PORT]
              Bind  the  controller listener to this address. If you specify a
              port, bind to  this  port  rather  than  the  one  specified  in
              ControlPort.  We  strongly  recommend  that you leave this alone
              unless you know what you’re doing, since giving attackers access
              to   your   control  listener  is  really  dangerous.  (Default:
              127.0.0.1) This directive can be  specified  multiple  times  to
              bind to multiple addresses/ports.

       HashedControlPassword hashed_password
              Don’t  allow any connections on the control port except when the
              other  process  knows  the  password  whose  one-way   hash   is
              hashed_password.   You  can  compute  the  hash of a password by
              running "tor --hash-password password".

       CookieAuthentication 0|1
              If this option is set to 1, don’t allow any connections  on  the
              control  port  except  when  the  connecting  process  knows the
              contents of a file named "control_auth_cookie", which  Tor  will
              create  in  its  data  directory.   This  authentication methods
              should only be used on systems with  good  filesystem  security.
              (Default: 0)

       DataDirectory DIR
              Store working data in DIR (Default: /var/lib/tor)

       DirServer [nickname] [flags] address:port fingerprint
              Use a nonstandard authoritative directory server at the provided
              address and port, with  the  specified  key  fingerprint.   This
              option  can  be  repeated many times, for multiple authoritative
              directory servers.  Flags are separated by spaces, and determine
              what  kind of an authority this directory is.  By default, every
              authority is authoritative for current ("v2")-style directories,
              unless  the  "no-v2"  flag  is  given.   If  the  "v1"  flags is
              provided, Tor will use this server as an authority for old-style
              (v1)  directories  as  well.  (Only directory mirrors care about
              this.)  Tor will use this server  as  an  authority  for  hidden
              service information if the "hs" flag is set, or if the "v1" flag
              is set and the "no-hs" flag is not set.  If a flag "orport=port"
              is  given,  Tor  will  use the given port when opening encrypted
              tunnels to the dirserver.  If no dirserver line  is  given,  Tor
              will  use  the  default directory servers.  NOTE: this option is
              intended for setting up a  private  Tor  network  with  its  own
              directory   authorities.    If   you   use   it,   you  will  be
              distinguishable from other users, because you won’t believe  the
              same authorities they do.

       FetchHidServDescriptors 0|1
              If set to 0, Tor will never fetch any hidden service descriptors
              from the rendezvous directories. This option is only  useful  if
              you’re  using  a Tor controller that handles hidserv fetches for
              you.  (Default: 1)

       FetchServerDescriptors 0|1
              If set to 0, Tor will never fetch any network  status  summaries
              or server descriptors from the directory servers. This option is
              only useful if  you’re  using  a  Tor  controller  that  handles
              directory fetches for you.  (Default: 1)

       FetchUselessDescriptors 0|1
              If  set  to 1, Tor will fetch every non-obsolete descriptor from
              the authorities that it hears about. Otherwise,  it  will  avoid
              fetching  useless  descriptors, for example for routers that are
              not  running.   This  option  is  useful  if  you’re  using  the
              contributed  "exitlist"  script to enumerate Tor nodes that exit
              to certain addresses.  (Default: 0)

       Group GID
              On startup, setgid to this group.

       HttpProxy host[:port]
              Tor will make all its directory requests through this  host:port
              (or  host:80  if  port is not specified), rather than connecting
              directly to any directory servers.

       HttpProxyAuthenticator username:password
              If defined, Tor will use this username:password for  Basic  Http
              proxy authentication, as in RFC 2617. This is currently the only
              form of Http proxy authentication that Tor supports;  feel  free
              to submit a patch if you want it to support others.

       HttpsProxy host[:port]
              Tor  will  make  all  its  OR  (SSL)  connections  through  this
              host:port (or host:443 if  port  is  not  specified),  via  HTTP
              CONNECT  rather  than  connecting  directly to servers.  You may
              want to set FascistFirewall to restrict the  set  of  ports  you
              might  try  to  connect  to,  if  your  Https  proxy only allows
              connecting to certain ports.

       HttpsProxyAuthenticator username:password
              If defined, Tor will use this username:password for Basic  Https
              proxy authentication, as in RFC 2617. This is currently the only
              form of Https proxy authentication that Tor supports; feel  free
              to submit a patch if you want it to support others.

       KeepalivePeriod NUM
              To  keep  firewalls  from  expiring  connections, send a padding
              keepalive cell every NUM seconds on open connections that are in
              use.  If the connection has no open circuits, it will instead be
              closed after NUM seconds of idleness. (Default: 5 minutes)

       Log minSeverity[-maxSeverity] stderr|stdout|syslog
              Send all messages between minSeverity  and  maxSeverity  to  the
              standard  output  stream,  the  standard error stream, or to the
              system log. (The "syslog" value  is  only  supported  on  Unix.)
              Recognized  severity  levels  are debug, info, notice, warn, and
              err.  We advise using "notice" in  most  cases,  since  anything
              more  verbose  may  provide sensitive information to an attacker
              who obtains the logs.  If only one severity level is given,  all
              messages  of  that  level  or  higher will be sent to the listed
              destination.

       Log minSeverity[-maxSeverity] file FILENAME
              As above, but send log messages to  the  listed  filename.   The
              "Log"  option may appear more than once in a configuration file.
              Messages are sent to all the  logs  that  match  their  severity
              level.

       OutboundBindAddress IP
              Make  all  outbound  connections  originate  from the IP address
              specified.  This is only useful when you have  multiple  network
              interfaces,  and  you  want all of Tor’s outgoing connections to
              use a single one.

       PidFile FILE
              On startup, write our PID to FILE.  On  clean  shutdown,  remove
              FILE.

       ProtocolWarnings 0|1
              If  1,  Tor will log with severity ’warn’ various cases of other
              parties not following the Tor specification. Otherwise, they are
              logged with severity ’info’. (Default: 0)

       RunAsDaemon 0|1
              If  1,  Tor  forks and daemonizes to the background. This option
              has no effect on Windows; instead you should use  the  --service
              command-line option. (Default: 0)

       SafeLogging 0|1
              If  1,  Tor  replaces  potentially sensitive strings in the logs
              (e.g. addresses) with the string [scrubbed]. This way  logs  can
              still   be  useful,  but  they  don’t  leave  behind  personally
              identifying information about  what  sites  a  user  might  have
              visited. (Default: 1)

       User UID
              On startup, setuid to this user.

       HardwareAccel 0|1
              If  non-zero,  try  to  use  crypto  hardware  acceleration when
              available. This is untested and probably buggy. (Default: 0)

       AvoidDiskWrites 0|1
              If non-zero, try to write to disk less frequently than we  would
              otherwise.  This is useful when running on flash memory or other
              media that support only a limited number of  writes.   (Default:
              0)

       TunnelDirConns 0|1
              If  non-zero, when a directory server we contact supports it, we
              will build a one-hop circuit and make  an  encrypted  connection
              via its ORPort. (Default: 0)

       PreferTunneledDirConns 0|1
              If  non-zero, we will avoid directory servers that don’t support
              tunneled directory connections, when possible. (Default: 0)

CLIENT OPTIONS

       The following  options  are  useful  only  for  clients  (that  is,  if
       SocksPort is non-zero):

       AllowInvalidNodes entry|exit|middle|introduction|rendezvous|...
              If  some  Tor  servers  are  obviously  not  working  right, the
              directory authorities can manually mark them as invalid, meaning
              that  it’s  not  recommended  you  use  them  for  entry or exit
              positions in your circuits. You can opt  to  use  them  in  some
              circuit  positions,  though. The default is "middle,rendezvous",
              and other choices are not advised.

       CircuitBuildTimeout NUM
              Try for at most NUM  seconds  when  building  circuits.  If  the
              circuit  isn’t  open  in  that time, give up on it.  (Default: 1
              minute.)

       CircuitIdleTimeout NUM
              If we have keept a clean (never used)  circuit  around  for  NUM
              seconds, then close it. This way when the Tor client is entirely
              idle, it can expire all of its circuits, and then expire its TLS
              connections.  Also,  if  we  end up making a circuit that is not
              useful for exiting any of the requests we’re receiving, it won’t
              forever  take up a slot in the circuit list.  (Default: 1 hour.)

       ClientOnly 0|1
              If set to 1, Tor will under no circumstances run  as  a  server.
              The  default  is to run as a client unless ORPort is configured.
              (Usually, you don’t need to set this; Tor  is  pretty  smart  at
              figuring  out whether you are reliable and high-bandwidth enough
              to be a useful server.)  (Default: 0)

       ExcludeNodes nickname,nickname,...
              A list of nodes to never use when building a circuit.

       EntryNodes nickname,nickname,...
              A list of preferred nodes to  use  for  the  first  hop  in  the
              circuit.    These   are   treated  only  as  preferences  unless
              StrictEntryNodes (see below) is also set.

       ExitNodes nickname,nickname,...
              A list of preferred nodes  to  use  for  the  last  hop  in  the
              circuit.    These   are   treated  only  as  preferences  unless
              StrictExitNodes (see below) is also set.

       StrictEntryNodes 0|1
              If 1, Tor will never use  any  nodes  besides  those  listed  in
              "EntryNodes" for the first hop of a circuit.

       StrictExitNodes 0|1
              If  1,  Tor  will  never  use  any nodes besides those listed in
              "ExitNodes" for the last hop of a circuit.

       FascistFirewall 0|1
              If 1, Tor will only create outgoing connections to  ORs  running
              on  ports that your firewall allows (defaults to 80 and 443; see
              FirewallPorts).  This will allow you to  run  Tor  as  a  client
              behind  a firewall with restrictive policies, but will not allow
              you to run as a server behind such a firewall.  This  option  is
              deprecated; use ReachableAddresses instead.

       FirewallPorts PORTS
              A  list  of  ports  that your firewall allows you to connect to.
              Only  used  when  FascistFirewall  is  set.   This   option   is
              deprecated; use ReachableAddresses instead. (Default: 80, 443)

       ReachableAddresses ADDR[/MASK][:PORT]...
              A  comma-separated  list  of  IP  addresses  and ports that your
              firewall allows you to connect to. The  format  is  as  for  the
              addresses  in  ExitPolicy,  except  that  "accept" is understood
              unless  "reject"   is   explicitly   provided.    For   example,
              ’ReachableAddresses  99.0.0.0/8,  reject  18.0.0.0/8:80,  accept
              *:80’ means that your firewall allows connections to  everything
              inside  net  99,  rejects  port  80  connections  to net 18, and
              accepts connections to port  80  otherwise.   (Default:  ’accept
              *:*’.)

       ReachableDirAddresses ADDR[/MASK][:PORT]...
              Like  ReachableAddresses,  a  list  of addresses and ports.  Tor
              will   obey   these   restrictions   when   fetching   directory
              information,  using  standard  HTTP  GET  requests.  If  not set
              explicitly then the value of  ReachableAddresses  is  used.   If
              HttpProxy  is  set  then  these connections will go through that
              proxy.

       ReachableORAddresses ADDR[/MASK][:PORT]...
              Like ReachableAddresses, a list of  addresses  and  ports.   Tor
              will  obey  these restrictions when connecting to Onion Routers,
              using  TLS/SSL.   If  not  set  explicitly  then  the  value  of
              ReachableAddresses  is  used.  If  HttpsProxy  is set then these
              connections will go through that proxy.

              The     separation     between     ReachableORAddresses      and
              ReachableDirAddresses   is   only   interesting   when  you  are
              connecting through proxies (see HttpProxy and HttpsProxy).  Most
              proxies  limit  TLS  connections  (which  Tor uses to connect to
              Onion Routers) to port 443, and some  limit  HTTP  GET  requests
              (which  Tor uses for fetching directory information) to port 80.

       LongLivedPorts PORTS
              A list of ports for services  that  tend  to  have  long-running
              connections  (e.g.  chat  and  interactive shells). Circuits for
              streams that use  these  ports  will  contain  only  high-uptime
              nodes,  to reduce the chance that a node will go down before the
              stream is finished.  (Default: 21, 22, 706,  1863,  5050,  5190,
              5222, 5223, 6667, 6697, 8300)

       MapAddress address newaddress
              When a request for address arrives to Tor, it will rewrite it to
              newaddress before processing it. For example, if you always want
              connections  to  www.indymedia.org  to exit via torserver (where
              torserver is  the  nickname  of  the  server),  use  "MapAddress
              www.indymedia.org www.indymedia.org.torserver.exit".

       NewCircuitPeriod NUM
              Every  NUM  seconds  consider  whether  to  build a new circuit.
              (Default: 30 seconds)

       MaxCircuitDirtiness NUM
              Feel free to reuse a circuit that was first  used  at  most  NUM
              seconds  ago, but never attach a new stream to a circuit that is
              too old.  (Default: 10 minutes)

       EnforceDistinctSubnets 0|1
              If 1, Tor will not put two servers whose IP addresses  are  "too
              close"  on  the same circuit.  Currently, two addresses are "too
              close" if they lie in the same /16 range. (Default: 1)

       RendNodes nickname,nickname,...
              A list of preferred nodes to use for the  rendezvous  point,  if
              possible.

       RendExcludeNodes nickname,nickname,...
              A list of nodes to never use when choosing a rendezvous point.

       SocksPort PORT
              Advertise  this  port  to  listen  for  connections  from Socks-
              speaking applications.  Set this to 0 if you don’t want to allow
              application connections. (Default: 9050)

       SocksListenAddress IP[:PORT]
              Bind  to  this  address  to  listen  for connections from Socks-
              speaking applications. (Default: 127.0.0.1) You can also specify
              a port (e.g. 192.168.0.1:9100).  This directive can be specified
              multiple times to bind to multiple addresses/ports.

       SocksPolicy policy,policy,...
              Set an entrance policy for this server, to limit who can connect
              to  the  Socks  ports.   The policies have the same form as exit
              policies below.

       SocksTimeout NUM
              Let a socks connection wait NUM  seconds  handshaking,  and  NUM
              seconds unattached waiting for an appropriate circuit, before we
              fail it.  (Default: 2 minutes.)

       TestVia nickname,nickname,...
              A list of nodes to prefer for  your  middle  hop  when  building
              testing   circuits.   This   option   is  mainly  for  debugging
              reachability problems.

       TrackHostExits host,.domain,...
              For each value in the  comma  separated  list,  Tor  will  track
              recent connections to hosts that match this value and attempt to
              reuse the same exit node for each. If  the  value  is  prepended
              with  a  ’.’, it is treated as matching an entire domain. If one
              of the values is just a ’.’, it  means  match  everything.  This
              option  is  useful  if you frequently connect to sites that will
              expire all your authentication cookies (ie log you out) if  your
              IP  address  changes.  Note  that  this  option  does  have  the
              disadvantage of making it more clear that  a  given  history  is
              associated  with  a  single user. However, most people who would
              wish to observe this will observe it through  cookies  or  other
              protocol-specific means anyhow.

       TrackHostExitsExpire NUM
              Since exit servers go up and down, it is desirable to expire the
              association between host and exit server after NUM seconds.  The
              default is 1800 seconds (30 minutes).

       UseEntryGuards 0|1
              If  this  option  is  set  to  1,  we pick a few long-term entry
              servers, and try to stick with them.  This is desirable  because
              constantly changing servers increases the odds that an adversary
              who owns some servers will observe a  fraction  of  your  paths.
              (Defaults to 1.)

       NumEntryGuards NUM
              If  UseEntryGuards  is  set to 1, we will try to pick a total of
              NUM routers as long-term entries for our circuits.  (Defaults to
              3.)

       SafeSocks 0|1
              When  this  option  is  enabled,  Tor  will  reject  application
              connections that use unsafe variants of the  socks  protocol  --
              ones that only provide an IP address, meaning the application is
              doing a DNS resolve first.  Specifically, these are  socks4  and
              socks5 when not doing remote DNS.  (Defaults to 0.)

       TestSocks 0|1
              When  this  option  is enabled, Tor will make a notice-level log
              entry for each connection to the Socks port  indicating  whether
              the  request  used  a  safe socks protocol or an unsafe one (see
              above entry on SafeSocks).  This helps to determine  whether  an
              application   using   Tor  is  possibly  leaking  DNS  requests.
              (Default: 0)

       VirtualAddrNetwork Address/bits
              When a controller asks for a virtual (unused) address  with  the
              MAPADDRESS  command,  Tor  picks an unassigned address from this
              range.  (Default: 127.192.0.0/10)

              When providing proxy server service to a  network  of  computers
              using   a  tool  like  dns-proxy-tor,  change  this  address  to
              "10.192.0.0/10"     or     "172.16.0.0/12".      The     default
              VirtualAddrNetwork   address  range  on  a  properly  configured
              machine will route to the loopback interface.  For local use, no
              change to the default VirtualAddrNetwork setting is needed.

       AllowNonRFC953Hostnames 0|1
              When  this  option  is disabled, Tor blocks hostnames containing
              illegal characters (like @ and :) rather than sending them to an
              exit  node  to be resolved.  This helps trap accidental attempts
              to resolve URLs and so on.  (Default: 0)

       FastFirstHopPK 0|1
              When this option is enabled and we aren’t running as  a  server,
              Tor  skips  the  public  key  step for the first hop of creating
              circuits.  This is safe  since  we  have  already  used  TLS  to
              authenticate  the  server  and to establish forward-secure keys.
              Turning  this  option  off  makes   circuit   building   slower.
              (Default: 1)

       TransPort PORT
              If  non-zero,  enables  transparent  proxy  support  on PORT (by
              convention, 9040).  Requires OS support for transparent proxies,
              such as BSDs’ pf or Linux’s IPTables.  If you’re planning to use
              Tor as a transparent proxy for a network, you’ll want to examine
              and  change  VirtualAddrNetwork from the default setting. You’ll
              also want to set the TransListenAddress option for  the  network
              you’d like to proxy.  (Default: 0).

       TransListenAddress IP[:PORT]
              Bind   to   this   address   to  listen  for  transparent  proxy
              connections.   (Default:  127.0.0.1).   This   is   useful   for
              exporting a transparent proxy server to an entire network.

       NATDPort PORT
              Allow  old  versions  of  ipfw  (as  included in old versions of
              FreeBSD, etc.) to send connections through Tor  using  the  NATD
              protocol.   This  option  is  only  for  people  who  cannot use
              TransPort.

       NATDListenAddress IP[:PORT]
              Bind to this address to listen for NATD connections.   (Default:
              127.0.0.1).

       SERVER OPTIONS

       The  following  options are useful only for servers (that is, if ORPort
       is non-zero):

       Address address
              The IP or fqdn of this  server  (e.g.  moria.mit.edu).  You  can
              leave this unset, and Tor will guess your IP.

       AssumeReachable 0|1
              This option is used when bootstrapping a new Tor network. If set
              to 1, don’t  do  self-reachability  testing;  just  upload  your
              server descriptor immediately. If AuthoritativeDirectory is also
              set, this  option  instructs  the  dirserver  to  bypass  remote
              reachability  testing  too  and  list  all  connected servers as
              running.

       ContactInfo email_address
              Administrative contact information for server. This  line  might
              get picked up by spam harvesters, so you may want to obscure the
              fact that it’s an email address.

       ExitPolicy policy,policy,...
              Set an exit policy for this server. Each policy is of  the  form
              "accept|reject  ADDR[/MASK][:PORT]".   If  /MASK is omitted then
              this policy just applies to the host given.  Instead of giving a
              host  or  network  you  can  also use "*" to denote the universe
              (0.0.0.0/0).  PORT can be a single port number, an  interval  of
              ports  "FROM_PORT-TO_PORT",  or  "*".   If PORT is omitted, that
              means "*".

              For  example,  "accept  18.7.22.69:*,reject  18.0.0.0/8:*,accept
              *:*"  would  reject  any  traffic  destined  for  MIT except for
              web.mit.edu, and accept anything else.

              To specify  all  internal  and  link-local  networks  (including
              0.0.0.0/8,    169.254.0.0/16,    127.0.0.0/8,    192.168.0.0/16,
              10.0.0.0/8, and 172.16.0.0/12), you can use the "private"  alias
              instead  of an address.  These addresses are rejected by default
              (at the beginning of your exit policy), along with  your  public
              IP  address,  unless  you set the ExitPolicyRejectPrivate config
              option to 0. For example, once you’ve done that, you could allow
              HTTP  to  127.0.0.1  and block all other connections to internal
              networks with  "accept  127.0.0.1:80,reject  private:*",  though
              that  may  also  allow connections to your own computer that are
              addressed to its public (external) IP address. See RFC 1918  and
              RFC 3330 for more details about internal and reserved IP address
              space.

              This directive can be specified multiple times so you don’t have
              to put it all on one line.

              Policies are considered first to last, and the first match wins.
              If you want to _replace_ the default exit policy, end your  exit
              policy  with  either  a  reject *:* or an accept *:*. Otherwise,
              you’re _augmenting_ (prepending to) the default exit policy. The
              default exit policy is:
                   reject *:25
                   reject *:119
                   reject *:135-139
                   reject *:445
                   reject *:465
                   reject *:563
                   reject *:587
                   reject *:1214
                   reject *:4661-4666
                   reject *:6346-6429
                   reject *:6699
                   reject *:6881-6999
                   accept *:*

       ExitPolicyRejectPrivate 0|1
              Reject  all private (local) networks, along with your own public
              IP address, at the beginning of  your  exit  policy.  See  above
              entry on ExitPolicy. (Default: 1)

       MaxOnionsPending NUM
              If  you  have  more  than  this  number of onionskins queued for
              decrypt, reject new ones. (Default: 100)

       MyFamily nickname,nickname,...
              Declare that this Tor server is controlled or administered by  a
              group  or organization identical or similar to that of the other
              named servers.  When two servers both declare that they  are  in
              the  same  ’family’,  Tor  clients will not use them in the same
              circuit.  (Each server only needs to list the other  servers  in
              its  family; it doesn’t need to list itself, but it won’t hurt.)

       Nickname name
              Set the server’s nickname to ’name’. Nicknames must be between 1
              and   19   characters  inclusive,  and  must  contain  only  the
              characters [a-zA-Z0-9].

       NumCPUs num
              How many processes to use at  once  for  decrypting  onionskins.
              (Default: 1)

       ORPort PORT
              Advertise  this  port to listen for connections from Tor clients
              and servers.

       ORListenAddress IP[:PORT]
              Bind to this IP address  to  listen  for  connections  from  Tor
              clients  and  servers.  If you specify a port, bind to this port
              rather than the one specified in ORPort. (Default: 0.0.0.0) This
              directive  can  be  specified multiple times to bind to multiple
              addresses/ports.

       PublishServerDescriptor 0|1
              If set to 0, Tor will act as a server  if  you  have  an  ORPort
              defined,   but  it  will  not  publish  its  descriptor  to  the
              dirservers. This option is useful if  you’re  testing  out  your
              server,  or  if  you’re  using  a  Tor  controller  that handles
              directory publishing for you.  (Default: 1)

       RedirectExit pattern target
              Whenever an outgoing connection tries to connect  to  one  of  a
              given set of addresses, connect to target (an address:port pair)
              instead.  The address pattern is given in the same format as for
              an  exit  policy.   The  address  translation applies after exit
              policies are applied.   Multiple  RedirectExit  options  can  be
              used: once any one has matched successfully, no subsequent rules
              are considered.  You can specify that no redirection  is  to  be
              performed  on  a  given  set  of  addresses by using the special
              target string "pass", which prevents subsequent rules from being
              considered.

       ShutdownWaitLength NUM
              When we get a SIGINT and we’re a server, we begin shutting down:
              we close listeners and start refusing new  circuits.  After  NUM
              seconds,   we   exit.  If  we  get  a  second  SIGINT,  we  exit
              immediately.  (Default: 30 seconds)

       AccountingMax N bytes|KB|MB|GB|TB
              Never send more than the specified number of bytes  in  a  given
              accounting  period,  or  receive  more  than  that number in the
              period.  For example, with AccountingMax set to 1 GB,  a  server
              could  send  900  MB and receive 800 MB and continue running. It
              will only hibernate once one of the two reaches 1 GB.  When  the
              number of bytes is exhausted, Tor will hibernate until some time
              in the next accounting period.   To  prevent  all  servers  from
              waking at the same time, Tor will also wait until a random point
              in each period before waking up.  If  you  have  bandwidth  cost
              issues,  enabling  hibernation  is  preferable  to setting a low
              bandwidth, since it provides users with  a  collection  of  fast
              servers  that are up some of the time, which is more useful than
              a set of slow servers that are always "available".

       AccountingStart day|week|month [day] HH:MM
              Specify how long accounting periods last.  If  month  is  given,
              each accounting period runs from the time HH:MM on the dayth day
              of one month to the same day and time of  the  next.   (The  day
              must  be  between  1 and 28.)  If week is given, each accounting
              period runs from the time HH:MM of the dayth day of one week  to
              the same day and time of the next week, with Monday as day 1 and
              Sunday as day 7.  If day is given, each accounting  period  runs
              from  the  time HH:MM each day to the same time on the next day.
              All times are local, and given in 24-hour  time.   (Defaults  to
              "month 1 0:00".)

       ServerDNSResolvConfFile filename
              Overrides  the  default DNS configuration with the configuration
              in filename.  The file format is the same as the  standard  Unix
              "resolv.conf"  file  (7).  This option, like all other ServerDNS
              options, only affects name  lookup  that  your  server  does  on
              behalf  of clients.  Also, it only takes effect if Tor was built
              with  eventdns  support.   (Defaults  to  use  the  system   DNS
              configuration.)

       ServerDNSSearchDomains 0|1
              If  set  to  1,  then  we will search for addresses in the local
              search domain.  For example, if this  system  is  configured  to
              believe it is in "example.com", and a client tries to connect to
              "www", the client will be connected to "www.example.com".   This
              option  only affects name lookup that your server does on behalf
              of clients, and only takes effect if Tor was build with eventdns
              support.  (Defaults to "0".)

       ServerDNSDetectHijacking 0|1
              When  this  option  is  set  to  1, we will test periodically to
              determine whether our local nameservers have been configured  to
              hijack  failing  DNS  requests (usually to an advertising site).
              If they are, we will attempt to correct this.  This option  only
              affects  name lookup that your server does on behalf of clients,
              and only takes effect if Tor was build  with  eventdns  support.
              (Defaults to "1".)

       ServerDNSTestAddresses address,address,...
              When  we’re  detecting DNS hijacking, make sure that these valid
              addresses aren’t getting redirected.  If they are, then our  DNS
              is  completely  useless,  and  we’ll  reset  our  exit policy to
              "reject *:*".  This option only affects name  lookup  that  your
              server  does  on behalf of clients, and only takes effect if Tor
              was build with eventdns support.  (Defaults to  "www.google.com,
              www.mit.edu, www.yahoo.com, www.slashdot.org".)

       ServerDNSAllowNonRFC953Hostnames 0|1
              When  this  option  is  disabled,  Tor  does  not try to resolve
              hostnames containing illegal characters (like @  and  :)  rather
              than  sending  them  to an exit node to be resolved.  This helps
              trap accidental attempts to resolve URLs and so on.  This option
              only  affects  name  lookup  that  your server does on behalf of
              clients, and only takes effect if Tor was  build  with  eventdns
              support.  (Default: 0)

DIRECTORY SERVER OPTIONS

       The  following  options are useful only for directory servers (that is,
       if DirPort is non-zero):

       AuthoritativeDirectory 0|1
              When this option is set to 1, Tor operates as  an  authoritative
              directory   server.    Instead  of  caching  the  directory,  it
              generates its own list of good servers, signs it, and sends that
              to the clients.  Unless the clients already have you listed as a
              trusted directory, you probably do not want to set this  option.
              Please coordinate with the other admins at tor-ops@freehaven.net
              if you think you should be a directory.

       V1AuthoritativeDirectory 0|1
              When this option is set in addition  to  AuthoritativeDirectory,
              Tor  also generates a version 1 directory (for Tor clients up to
              0.1.0.x).   (As  of  Tor  0.1.1.12  every   (v2)   authoritative
              directory still provides most of the v1 directory functionality,
              even without this option set to 1.  This however is expected  to
              change in the future.)

       VersioningAuthoritativeDirectory 0|1
              When  this  option  is  set  to 1, Tor adds information on which
              versions of Tor are still believed safe for use to the published
              directory.    Each   version  1  authority  is  automatically  a
              versioning authority; version 2 authorities provide this service
              optionally.  See RecommendedVersions, RecommendedClientVersions,
              and RecommendedServerVersions.

       NamingAuthoritativeDirectory 0|1
              When this option is set to 1, then the server advertises that it
              has  opinions  about  nickname-to-fingerprint bindings.  It will
              include these opinions in its published network-status pages, by
              listing  servers  with  the  flag  "Named"  if a correct binding
              between that nickname and fingerprint has been  registered  with
              the  dirserver.   Naming  dirservers  will  refuse  to accept or
              publish descriptors that contradict a registered  binding.   See
              approved-routers in the FILES section below.

       HSAuthoritativeDir 0|1
              When  this  option is set in addition to AuthoritativeDirectory,
              Tor  also  accepts  and  serves  hidden   service   descriptors.
              (Default: 0)

       DirPort PORT
              Advertise the directory service on this port.

       DirListenAddress IP[:PORT]
              Bind  the  directory  service  to this address. If you specify a
              port, bind to  this  port  rather  than  the  one  specified  in
              DirPort.  (Default:  0.0.0.0)  This  directive  can be specified
              multiple times to bind to multiple addresses/ports.

       DirPolicy policy,policy,...
              Set an entrance policy for this server, to limit who can connect
              to the directory ports.  The policies have the same form as exit
              policies above.

       RecommendedVersions STRING
              STRING is a  comma-separated  list  of  Tor  versions  currently
              believed to be safe. The list is included in each directory, and
              nodes which pull down the directory learn whether they  need  to
              upgrade.  This option can appear multiple times: the values from
              multiple lines are spliced together.   When  this  is  set  then
              VersioningAuthoritativeDirectory should be set too.

       RecommendedClientVersions STRING
              STRING  is  a  comma-separated  list  of  Tor versions currently
              believed to be safe for clients to  use.   This  information  is
              included  in version 2 directories.  If this is not set then the
              value of RecommendedVersions is used.  When  this  is  set  then
              VersioningAuthoritativeDirectory should be set too.

       RecommendedServerVersions STRING
              STRING  is  a  comma-separated  list  of  Tor versions currently
              believed to be safe for servers to  use.   This  information  is
              included  in version 2 directories.  If this is not set then the
              value of RecommendedVersions is used.  When  this  is  set  then
              VersioningAuthoritativeDirectory should be set too.

       DirAllowPrivateAddresses 0|1
              If  set  to 1, Tor will accept router descriptors with arbitrary
              "Address" elements. Otherwise, if the address is not an IP or is
              a  private IP, it will reject the router descriptor. Defaults to
              0.

       AuthDirBadExit AddressPattern...
              Authoritative directories only.  A set of address  patterns  for
              servers  that  will be listed as bad exits in any network status
              document this authority  publishes,  if  AuthDirListBadExits  is
              set.

       AuthDirInvalid AddressPattern...
              Authoritative  directories  only.  A set of address patterns for
              servers that will never be listed  as  "valid"  in  any  network
              status document that this authority publishes.

       AuthDirReject AddressPattern...
              Authoritative  directories  only.  A set of address patterns for
              servers that will never be listed at all in any  network  status
              document  that  this  authority  publishes, or accepted as an OR
              address in any descriptor  submitted  for  publication  by  this
              authority.

       AuthDirListBadExits 0|1
              Authoritative directories only.  If set to 1, this directory has
              some opinion about which nodes are  unsuitable  as  exit  nodes.
              (Do  not  set  this  to 1 unless you plan to list nonfunctioning
              exits as bad; otherwise, you are effectively voting in favor  of
              every declared exit as an exit.)

       AuthDirRejectUnlisted 0|1
              Authoritative  directories  only.   If  set  to 1, the directory
              server rejects  all  uploaded  server  descriptors  that  aren’t
              explicitly  listed  in  the  fingerprints  file.  This acts as a
              "panic button" if we get Sybiled. (Default: 0)

HIDDEN SERVICE OPTIONS

       The following options are used to configure a hidden service.

       HiddenServiceDir DIRECTORY
              Store data files for  a  hidden  service  in  DIRECTORY.   Every
              hidden service must have a separate directory.  You may use this
              option multiple times to specify multiple services.

       HiddenServicePort VIRTPORT [TARGET]
              Configure a virtual port VIRTPORT for a hidden service.  You may
              use this option multiple times; each time applies to the service
              using the most recent hiddenservicedir.  By default, this option
              maps  the  virtual  port to the same port on 127.0.0.1.  You may
              override the target port,  address,  or  both  by  specifying  a
              target of addr, port, or addr:port.

       HiddenServiceNodes nickname,nickname,...
              If  possible, use the specified nodes as introduction points for
              the hidden service. If this is left unset, Tor will be smart and
              pick some reasonable ones; most people can leave this unset.

       HiddenServiceExcludeNodes nickname,nickname,...
              Do  not  use  the specified nodes as introduction points for the
              hidden service. In normal use there is no reason to set this.

       PublishHidServDescriptors 0|1
              If set to 0, Tor will run any hidden services you configure, but
              it won’t advertise them to the rendezvous directory. This option
              is only useful if you’re using a  Tor  controller  that  handles
              hidserv publishing for you.  (Default: 1)

       RendPostPeriod N seconds|minutes|hours|days|weeks
              Every  time  the  specified  period  elapses,  Tor  uploads  any
              rendezvous service descriptors to the directory  servers.   This
              information  is also uploaded whenever it changes.  (Default: 20
              minutes)

SIGNALS

       Tor catches the following signals:

       SIGTERM
              Tor will catch this, clean up and sync to disk if necessary, and
              exit.

       SIGINT Tor  clients  behave  as with SIGTERM; but Tor servers will do a
              controlled slow  shutdown,  closing  listeners  and  waiting  30
              seconds  before  exiting.  (The delay can be configured with the
              ShutdownWaitLength config option.)

       SIGHUP The signal instructs Tor to reload its configuration  (including
              closing and reopening logs), fetch a new directory, and kill and
              restart its helper processes if applicable.

       SIGUSR1
              Log statistics about current connections, past connections,  and
              throughput.

       SIGUSR2
              Switch  all  logs  to loglevel debug. You can go back to the old
              loglevels by sending a SIGHUP.

       SIGCHLD
              Tor receives this signal when one of its  helper  processes  has
              exited, so it can clean up.

       SIGPIPE
              Tor catches this signal and ignores it.

       SIGXFSZ
              If  this signal exists on your platform, Tor catches and ignores
              it.

FILES

       /etc/tor/torrc
              The configuration file, which contains "option value" pairs.

       /var/lib/tor/
              The tor process stores keys and other data here.

       DataDirectory/cached-status/*
              The most recently downloaded network status  document  for  each
              authority.  Each file holds one such document; the filenames are
              the hexadecimal  identity  key  fingerprints  of  the  directory
              authorities.

       DataDirectory/cached-routers and cached-routers.new
              These  files  hold downloaded router statuses.  Some routers may
              appear more than  once;  if  so,  the  most  recently  published
              descriptor  is used.  The ".new" file is an append-only journal;
              when it gets too large,  all  entries  are  merged  into  a  new
              cached-routers file.

       DataDirectory/state
              A set of persistent key-value mappings.  These are documented in
              the file.  These include:
            - The current entry guards and their status.
            - The current bandwidth accounting  values  (unused  so  far;  see
            below).
            - When the file was last written
            - What version of Tor generated the state file
            - A short history of bandwidth usage, as produced  in  the  router
            descriptors.

       DataDirectory/bw_accounting
              Used to track bandwidth  accounting  values  (when  the  current
              period  starts  and  ends; how much has been read and written so
              far this period).  This file is obsolete, and the  data  is  now
              stored  in  the  ’state’ file as well.  Only used when bandwidth
              accounting is enabled.

       DataDirectory/control_auth_cookie
              Used for cookie authentication with the controller.  Regenerated
              on  startup.   See control-spec.txt for details.  Only used when
              cookie authentication is enabled.

       DataDirectory/keys/*
              Only used by servers.  Holds identity keys and onion keys.

       DataDirectory/fingerprint
              Only used by servers.  Holds the  fingerprint  of  the  server’s
              identity key.

       DataDirectory/approved-routers
              Only   for   naming   authoritative   directory   servers   (see
              NamingAuthoritativeDirectory).   This  file  lists  nickname  to
              identity bindings.  Each line lists a nickname and a fingerprint
              separated by whitespace.   See  your  fingerprint  file  in  the
              DataDirectory  for  an example line.  If the nickname is !reject
              then descriptors  from  the  given  identity  (fingerprint)  are
              rejected  by this server. If it is !invalid then descriptors are
              accepted but marked in the directory as not valid, that is,  not
              recommended.

       HiddenServiceDirectory/hostname
              The  <base32-encoded-fingerprint>.onion  domain  name  for  this
              hidden service.

       HiddenServiceDirectory/private_key
              The private key for this hidden service.

SEE ALSO

       privoxy(1), tsocks(1), torify(1)

       https://www.torproject.org/

BUGS

       Plenty, probably. Tor is still in development. Please report them.

AUTHORS

       Roger Dingledine <arma@mit.edu>, Nick Mathewson <nickm@alum.mit.edu>.