Tor ContactInfo Generator

This page aims to make it easy to create a ContactInfo string which is in accordance with this specification. The generator creates a single output line that can easily be copied into your relay's torrc configuration file. After changing your torrc you have to reload your tor daemon.

Contact Info
This field contains the email address of the technical contact managing this Tor relay.
This field contains an URL (or hostname) pointing to the website (or domain) of the entity (organization or person) responsible for this Tor relay.
uri-rsa (recommended)     dns-rsa     None The proof field allows operators to make their URL value (previous field) verifyable (protected against spoofing) by placing their relay fingerprints in a text file located on their website. If no website is available DNS TXT records can be used instead.
Abuse email address where abuse emails should be send
0x
PGP key fingerprint (40 characters long) without spaces. This key should be available on keys.openpgp.org.
@
URL pointing to the Mastodon profile.
OTR v3 key fingerprint without spaces. Case in-sensitive. This key fingerprint relates to the xmpp address given in the xmpp field.

Hoster Information
Commercial hoster domain where this server has been ordered. This is supposed to help other relay operators and future relay operators to find hosting providers.
USD EUR GBP AUD CHF
Logical network interface speed in Mbit/s (1Mbit/s = 1 000 000 Bit/s) or the value of RelayBandwidthRate in your torrc setting (whatever is smaller). For asymetrical uplinks specify the lower of up- and download bandwidth.
Unmetered     Metered     Don't know States if this is an unmetered or metered offering. In case of metered bandwidth the monthly included outbound (TX) traffic in GiB (GibiByte) MUST be provided. If no bandwidth is included, this value MUST be set to 0. If the hoster meters in+outbound the hoster provided value must be divided by two.

On a server with multiple tor instances the total available monthly traffic of the server MUST be divided by the number of tor relay instances running on it.
Non-persistent memory (RAM) available on this server - measured in MB (Mebibytes). (this is the output of 'free -m' on most Unix-based systems.)
Only relevant for relays running on bare metal. String without spaces describing the used CPU model. Example: i5-8400
States the underlying virtualization technology used on which the OS is running. Use "baremetal" for bare-metal servers (not virtualized). Example: kvm

Donation Information
Bitcoin or OpenAlias address where people can send donations to support the operation of this Tor relay.
Zcash address where people are expected send donations to support the operation of this tor relay.
Monero or OpenAlias address where people can send donations to support the operation of this Tor relay.
URL pointing to a website that contains donation information to support this tor relay. This MUST be an HTTPS url.

Tor Configuration
Yes     No     Don't know / Don't want to say Single character stating whether the OfflineMasterKey feature is enabled on this tor instance or not
Integer stating the signing key renewal interval in days
Yes     No     Don't know / Don't want to say Single character stating whether this instance runs with Sandbox enabled

OS Information
String stating which OS distribution and version is used. Distribution and version is separated with a "/" sign. On platforms where the file /etc/os-release is available os is created by taking the ID and VERSION_ID values. The version identifier is optional and may be omitted. The string is case-insensitive. For example: OpenBSD/6.1 or debian/9
String stating which tls library is used. For example: openssl
Yes     No     Don't know / Don't want to say States whether AES-NI is available and used (checked) or not available/not used (unchecked)
Yes     No     Don't know / Don't want to say Single character stating whether automatic (unnattended) updates are enabled or not
States what configuration managment system is used. Set to "manual" for no configuration management. For example: ansible,chef,puppet

Relay Type
Exit     Non-exit relay

DNS Information
This field is only relevant for exit relays, non-exit relays SHOULD NOT set this field. String describing the location of the used DNS resolver in relation to the exit relay.
  • local means the resolver is running on the same host as the tor process.
  • sameas means the resolver is running on the same autonomous system as the exit relay and queries to the resolver do not cross another AS before reaching the resolver.
  • remote means the resolver is running on a system outside the exit relay's autonomous system
Multiple options may apply and MUST be separated using a comma. The order is relevant, the primary resolver MUST appear first followed by fallback resolvers.
Yes     No     Don't know / Don't want to say This field is only relevant for exit relays, non-exit relays SHOULD NOT set this field. Character stating whether this exit relay is performing DNS QNAME minimization ("y") or not ("n"). QNAME minimization is defined in RFC7816
Yes     No     Don't know / Don't want to say States if this relay performs DNSSEC validation.
Yes     No     Don't know / Don't want to say This field is only relevant for exit relays, non-exit relays SHOULD NOT set this field. States whether this exit relay is running the DNS root zone on loopback (checked) to avoid latency and information disclosure to DNS root servers or not (unchecked). This is defined in RFC7706.



Copy the following line into your torrc configuration file and reload your tor daemon:

© 2018 | Based on a specification by nusenu | Created by Eran Sandler | Code repo