Tor Relay Operators in End-to-End (E2E) Correlation Position

Tor network data as of: 2025-03-23 17:00 UTC

For each operator the list of running relays is shown (relays are linked to Relay Search). Operators and relays are sorted from more relevant to less relevant. More relevant in terms of guard probability. Guardonly relays have the guard flag but not the exit flag. Since exits are less common than guards their guard probability is usually 0% even when they have the guard flag. The number next to the contactinfo shows the number of relays running with the given ContactInfo (excluding middle-only relays). Middle-only relays (no guard and exit flag) are excluded to reduce the size of this list.

At the end of this page you can find a comma separated list of fingerprints of all guard-only relays on this page.

If your relay is listed here

Please configure MyFamily in your torrc configuration files. This page should help you with debugging your MyFamily configuration. The number in the last column should equal to the number of relays you operate (for every relay).

Once MyFamily is fixed the relays will automatically disappear from this page (within ~1-2 days). If you need help with the MyFamily configuration you can reach out to the tor-relays mailing list. You can also use tools that handle MyFamily automatically (I maintain an ansible role - relayor) If someone else is using your contactInfo please send an email to bad-relays AT lists DOT torproject DOT org.

ContactInfo: email:Quetzalcoatl relays proton.me url:https://q (422)

ContactInfo: 0x9F29C15D42A8B6F3 Nos oignons <adminsys@nos-oigno (47) {#0x9f29c15d42a8b6f3-nos-oignons-adminsysnos-oigno}

ContactInfo: contact@cypher.re (4)

ContactInfo: email:abuse artikel5ev.de url:https://artikel5ev. (25)

ContactInfo: email:denny.obreham a-n-o-n-y-m-e.net url:https:/ (18)

ContactInfo: mentor@palokaj.co (10)

Fingerprint List of Guard-only Relays in E2E Groups

4289936DF5DC722281E1CFBCCC1D47487532D040,20D9D2A69FBE8B3454F6286059F6BD95E74EFD9D,22404A3E87F2D7FE2FC6359FDE71B6DC2D6E730F,4B170481AC4C3EC3603B9F4443C2E24B929D0429,4F5D13F8951A1E18BAE1186F9E7849E3DB5B91AD,F5363557308690DE3F1FB22444FB80DC7703CEBD