Tor Project website
  • العربية (ar)
  • Deutsch (de)
  • English (en)
  • Español (es)
  • فارسي (fa)
  • Magyar nyelv (hu)
  • 日本語 (ja)
  • Русский (ru)
  • Turkish (tr)
  • українська (uk)
  • 简体中文 (zh-CN)
  • About
  • Support
  • Community
  • Blog
Download Donate
  • About
  • Support
  • Community
  • Blog
  1. Support
  2. About Tor

Topics

  • Introduction

  • Security

  • How Tor works

  • Using and sharing

  • Alternate Designs

  • Onion Services

Topics

  • Introduction

  • Security

  • How Tor works

  • Using and sharing

  • Alternate Designs

  • Onion Services

About Tor

This section explains Tor's design choices, security protections, entry guards, key management, and how Tor differs from other proxies.

Introduction

  • What is Tor?
  • Why is it called Tor?
  • What protections does Tor provide?
  • How is Tor different from other proxies?
  • Funding the Tor Project

Security

  • What attacks remain against onion routing?
  • Is there a backdoor in Tor?
  • HTTPS encryption and Tor

How Tor works

  • Overview
  • What are Entry Guards?
  • Tor path selection
  • Tor cryptographic keys

Using and sharing

  • Distributing Tor
  • Using Tor
  • Tor with Torrent
  • Changing the number of Tor hops
  • Sharing files with OnionShare
  • Does Tor Project keep logs?
  • About our services

Alternate Designs

  • You should make every Tor user be a relay
  • You should transport all IP packets, not just TCP packets
  • Exit policies should be able to block websites, not just IP addresses
  • You should let the network pick the path, not the client.
  • You should hide the list of Tor relays, so people can't block the exits.

Onion Services

  • What are .onion sites and onion services?
  • Jobs
  • Press
  • Contact
  • Newsletter
  • Forum
Mastodon
X
Facebook
Instagram
LinkedIn
Telegram
GitLab
GitHub
Bluesky
Copyleft icon Tor Project Inc.
  • Trademark and licenses