Tor relies on the support of users and volunteers around the world to help us improve our software and resources, so your feedback is extremely valuable to us (and to all Tor users).
When sending us feedback or reporting a bug, please include as many of these as possible:
- Operating System you are using
- Tor Browser version
- Tor Browser Security Level
- Step by step of how you got to the issue, so we can reproduce it (e.g. I opened the browser, typed a url, clicked on (i) icon, then my browser crashed)
- A screenshot of the problem
- The log
How to Reach Us
There are several ways to reach us, so please use what works best for you.
We recommend asking for help on the Tor Forum.
You will need to create an account to submit a new topic.
Before you ask, please review our discussion guidelines.
At the moment, for the fastest response, please write in English.
If you found a bug, please use GitLab.
First, check if the bug is already known.
You can search and read all the issues at https://gitlab.torproject.org/.
To create a new issue, please request a new account to access Tor Project's GitLab instance and find the right repository to report your issue.
We track all Tor Browser related issues at Tor Browser issue tracker.
Issues related to our websites should be filed under the Web issue tracker.
If you need help installing or troubleshooting Tor Browser and the Tor Forum is blocked or censored where you are, you can reach out to us on Telegram https://t.me/TorProjectSupportBot.
A Tor support specialist will assist you.
At the moment, the Telegram support channel is available in two languages: English and Russian.
Send us an email to email@example.com
In the subject line of your email, please tell us what you're reporting.
The more specific your subject line is (e.g. "Connection failure", "feedback on website", "feedback on Tor Browser, "I need a bridge"), the easier it will be for us to understand and follow up.
Sometimes when we receive emails without subject lines, they're marked as spam and we don't see them.
For the fastest response, please write in English, Spanish, and/or Portuguese if you can.
If none of these languages works for you, please write in any language you feel comfortable with, but keep in mind it will take us a bit longer to answer as we will need help with translation to understand it.
Blog post comments
You can always leave comments on the blog post related to the issue or feedback you want to report.
If there is not a blog post related to your issue, please contact us another way.
You can find us in the #tor channel on OFTC to give us feedback or report bugs/issues.
We may not respond right away, but we do check the backlog and will get back to you when we can.
Learn how to connect to OFTC servers.
For reporting issues or feedback using email lists, we recommend that you do so on the one that is related to what you would like to report. A complete directory of our mailing lists can be found here.
For feedback or issues related to Tor Browser, Tor network or other projects developed by Tor: tor-talk
For feedback or issues related to our websites: ux
For feedback or issues related to running a Tor relay: tor-relays
For feedback on content related to Tor Browser Manual or Support website: tor-community-team
Report a security issue
If you've found a security issue in one of our projects or in our infrastructure, please email firstname.lastname@example.org.
If you've found a security bug in Tor or Tor Browser, feel free to submit it for our bug bounty program.
If you want to encrypt your mail, you can get the GPG public key for the list by contacting email@example.com or from pool.sks-keyservers.net. Here is the fingerprint:
gpg --fingerprint firstname.lastname@example.org
pub 4096R/1A7BF184 2017-03-13
Key fingerprint = 8B90 4624 C5A2 8654 E453 9BC2 E135 A8B4 1A7B F184
sub 4096R/C00942E4 2017-03-13