If you have questions about using Tor:
- Read through the FAQ and the documentation.
- See if your question is asked or answered on our StackExchange page. If it isn't, please consider asking it there! Then everybody else can benefit from your question and the answer to it.
- Join the #tor irc channel, state the issue, and wait patiently for help.
- Read through the archives of the mailing lists to see if anybody else has raised your issue recently. Note that you need to subscribe to the mailing lists before you can post.
If you find your answer, please stick around to contribute back and help others who were once in your position.
Tor users and developers can also be found in the following channels on OFTC:
- #tor - For questions about using Tor (as a client, as a relay, as an onion service). Having trouble running Tor or have a question for other Tor users? Then this is the spot for you.
- #tor-dev - Channel for people who want to do development. Discussions about Tor-related coding, protocols, and project ideas are all welcome.
- #tor-project - Organization discussions unrelated to software development. A great place to discuss Tor community events, outreach, translation, or website improvements.
Follow us on Twitter:
If you have Tor questions, please try to help yourself via the above support venues. Please don't use these contact addresses for helpdesk or user requests — we all get too much mail and we won't be able to help you there.
- firstname.lastname@example.org is for questions and comments about getting money to the developers. More donations means more Tor. We're happy to help think about creative ways for you to contribute.
- email@example.com is for questions and comments about Tor the non-profit corporation: trademark questions, affiliation and coordination, major gifts, contract inquiries, licensing and certification, etc.
Should you need to reach us via old reliable mail, our mailing address is:
The Tor Project, Inc
7 Temple Street, Suite A
Cambridge, MA 02139-2403 USA
If you found a security issue in one of our projects or our infrastructure, please email the respective maintainer. You can find their GPG fingerprint/key on our developer ldap search page. Due to the many different projects we have, we do not offer a single list for security issues.