View Relay "HandsofGoldSpa"
Fingerprint: 0082C49022C0811D45620D408E068835E2BABA71 |
Family: 1 relay
|
kgonza@tutanota.com |
AS44486
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 56 Kbit/s Median
- Stability
- Not Overloaded | UP 1d 5h 32m ago | UP 100% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 1 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 4/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 40.0 Kbit/s – 128.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 56.0 Kbit/s.
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next. -
Guard: requires Fast flag
: Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
Guard: bandwidth below threshold
: 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 40.0 Kbit/s – 128.0 Kbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 1.1 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx. -
HSDir: requires Fast flag
: HSDir flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
HSDir: requires V2Dir (tunnelled-dir-server)
: HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include
tunnelled-dir-server, usually becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
High consensus weight deviation
: Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability. -
BadExit flag assigned
: This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue. -
MiddleOnly restriction active
: This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.
Addresses
- OR Address
- 176.118.193.106:443
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (9/9 DA) | 9/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| Valid | Descriptor | Meets (9/9 DA) | 9/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (4/9 DA) | 40.0 Kbit/s – 128.0 Kbit/s (5 DA measured) 1.1 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Partial (8/9 DA) | Median: 106.7d (9/9 DA above threshold) Min/Max: 9.5d / 352.2d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 40.0 Kbit/s – 128.0 Kbit/s (5 DA measured) 1.1 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (9/9 DA) | 9/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 40.0 Kbit/s – 128.0 Kbit/s (5 DA measured) 1.1 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (9/9 DA) | 9/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Median: 100.0% (9/9 DA above threshold) Min/Med/Max: 99.7% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 85.5d (9/9 DA above threshold) Min/Max: 9.7d / 351.9d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 40.0 Kbit/s – 128.0 Kbit/s (5 DA measured) 1.1 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Partial (0/9 DA) (only port 80) | Port 80: Yes | Port 443: Yes (R) | Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA) |
| MiddleOnly | Restriction (by DA) | Flagged (9/9 DA) | 9/9 authorities assigned MiddleOnly | Suspicious behavior, Sybil risk, or policy violation |
| BadExit | Restriction (by DA) | Flagged (5/9 DA) | 5/9 authorities assigned BadExit | Exit traffic manipulation, SSL stripping, or policy violation |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 1.07 Mbit/s
- Advertised Bandwidth
- 1.07 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
13 TB
(5 years)
1mo: 7.5 GB | 6mo: 454 GB | 1y: 531 GB | 5y: 13 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 56.0 Kbit/s (median of 5 measurements)
- Measured Min / Max
- 40.0 Kbit/s / 128.0 Kbit/s
- Deviation
- 88.0 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0000% of network
(2th pctl)
|
Guard:
N/A |
Middle:
0.0000% (2th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 1d 5h 32m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 100.0%/100.0%/100.0%/99.4%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (100.0%/100.0%/100.0%/99.4%)
- Hibernating
- No
Timestamps
- First Seen
- 3y 7mo 3w ago (2023-03-19 00:00:00)
- Last Seen
- 2h 45m 40s ago (2026-11-04 11:00:00)
- Last Restarted
- 1d 5h 32m ago (2026-11-03 08:13:10)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- kgonza@tutanota.com
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
0082C49022C0811D45620D408E068835E2BABA71 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.IPv4 Exit Policy Summary
accept: 20-21 43 53 80-81 443 5222-5223 6667-7000 8008 8082 8332-8333 8888 9418 18080-18081 50002 64738
IPv6 Exit Policy Summary
NoneFull Exit Policy
reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 176.118.193.106:* accept *:20-21 accept *:43 accept *:53 accept *:80-81 accept *:443 accept *:5222-5223 accept *:6667-7000 accept *:8008 accept *:8082 accept *:8332-8333 accept *:8888 accept *:9418 accept *:18080-18081 accept *:50002 accept *:64738 reject *:*
Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.
| Authority | Running | Valid | Exit | MiddleOnly | BW Scan (Authority) |
v4 | Flags | Fast (BW|T) | Guard BW (BW|Threshold) | Guard WFU (M|T) | Guard TK (M|T) | Stable MTBF (M|T) | Stable Uptime (Relay|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Stable, MiddleOnly | 112.0 Kbit/s (M) | 816.0 Kbit/s | 112.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 33.2d | 8d | 26.3d | 8.4d | 1.2d | 5.2d | 2026-11-04 02:13:17 | 112.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Stable, MiddleOnly | 48.0 Kbit/s (M) | 816.0 Kbit/s | 48.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 124.5d | 8d | 124.5d | 9.3d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 48.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | No | Yes | N | Yes | Running, Valid, Fast, Stable, MiddleOnly | 1.1 Mbit/s (R) | 816.0 Kbit/s | 1.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 85.5d | 8d | 58.3d | 6.7d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 1.1 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Fast, Stable, MiddleOnly, BadExit | 1.1 Mbit/s (R) | 816.0 Kbit/s | 1.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 24.9d | 8d | 14.8d | 6.5d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 1.1 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Stable, MiddleOnly, BadExit | 40.0 Kbit/s (M) | 816.0 Kbit/s | 40.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 106.7d | 8d | 106.7d | 10.8d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 40.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Fast, Stable, MiddleOnly, BadExit | 1.1 Mbit/s (R) | 816.0 Kbit/s | 1.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 335.8d | 8d | 335.8d | 10.9d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 1.1 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | Yes | N | Yes | Running, Valid, Fast, Stable, MiddleOnly | 1.1 Mbit/s (R) | 816.0 Kbit/s | 1.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 48.3d | 8d | 9.5d | 2.4d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 1.1 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Stable, MiddleOnly, BadExit | 128.0 Kbit/s (M) | 8.4 Mbit/s | 128.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 9.7d | 8d | 352.2d | 7607.5d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 128.0 Kbit/s (M) |
| tor26 (AT) | Yes | Yes | No | Yes | Y | Yes | Running, Valid, Stable, MiddleOnly, BadExit | 56.0 Kbit/s (M) | 816.0 Kbit/s | 56.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 351.9d | 8d | 351.9d | 10.6d | 1.2d | 5.3d | 2026-11-04 02:13:17 | 56.0 Kbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0
Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.