View Relay "Hormuz"

Fingerprint: DFE69F153172111298D39BBBC6DF6D4F5F965EDB | Family: 1 relay | AS24940 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, MiddleOnly, BadExit (4)
BW Verified
5/7 BW Auths Measured 22 Kbit/s Median
Stability
Not Overloaded | UP 2d 6h 41m ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
2d 6h 2m ago
BW Weight
0.00% of Network | 56 Mbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: WFU below threshold : Weighted Fractional Uptime 94.0% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • Guard: Time Known below threshold : Time Known 2.0 days is below 8 days requirement (6.0 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: requires Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
  • 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 because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: WFU below threshold : WFU 94.0% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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.

Connectivity and Location

Addresses
OR Address
static.208.187.76.144.clients.your-server.de
144.76.187.208:9001
[2a01:4f8:173:1763:73da:a392:c19b:9aa3]:9001
Exit Address
144.76.187.208
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 9.93% consensus weight, 257 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, MiddleOnly, BadExit
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 1/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (1/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 56.6 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 1.0d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Uptime Below (0/9 DA) 2.3d (R) ≥6.1d - 6.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 94.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 2.0d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 94.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.8 more days) Median: 2.2d (0/9 DA above threshold)
Min/Max: 2.0d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 56.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (1/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (8/9 DA) 8/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation
BadExit Restriction (by DA) Flagged (4/9 DA) 4/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-10-23 16:00:54).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
56.57 Mbit/s
Advertised Bandwidth
56.57 Mbit/s
Rate Limit
58.72 Mbit/s
Burst Limit
100.66 Mbit/s
Total Data
7.9 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-23 16:00:54

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
22.4 Kbit/s
Min / Max
8 bit/s / 56.6 Kbit/s
Deviation
56.6 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 6h 41m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 6h 2m ago (2026-10-21 10:00:00)
Last Seen
2h 2m 7s ago (2026-10-23 14:00:00)
Last Restarted
2d 6h 41m ago (2026-10-21 09:20:56)
Last Changed Address
2026-10-21 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-23 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
DFE69F153172111298D39BBBC6DF6D4F5F965EDB (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  80-81
  88
  110
  143
  194
  220
  389
  443
  853
  873
  902-904
  993-995
  1194
  1723
  2082-2083
  2086-2087
  2095-2096
  3128
  3389
  5190
  5222-5223
  5900
  8000
  8008
  8080
  8443
  8888
  10000
IPv6 Exit Policy Summary
accept: 
  20-23
  43
  53
  80-81
  88
  110
  143
  194
  220
  389
  443
  853
  873
  902-904
  993-995
  1194
  1723
  2082-2083
  2086-2087
  2095-2096
  3128
  3389
  5190
  5222-5223
  5900
  8000
  8008
  8080
  8443
  8888
  10000
Full 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 144.76.187.208:*
accept *:20-23
accept *:43
accept *:53
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:853
accept *:873
accept *:902-904
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1723
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:3128
accept *:3389
accept *:5190
accept *:5222-5223
accept *:5900
accept *:8000
accept *:8008
accept *:8080
accept *:8443
accept *:8888
accept *:10000
reject *:*

Last fetch was at Fri, 23 Oct 2026 16:01:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-23 16:00:54).

Per-Authority Details

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 v6 Flags Fast (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, MiddleOnly 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 94.0% | 98% 2.0d | 8d 1.0d | 4.8d 2.3d | 6.4d 94.0% | 98.0% 2.0d | 1.0d 2026-10-22 22:21:06 22.4 Kbit/s
dannenberg (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 5.8d 2.3d | 6.5d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 8 bit/s
dizum (NL) Yes Yes No Yes N Yes Yes Running, Valid, Fast, MiddleOnly 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.6d 2.3d | 6.4d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 56.6 Kbit/s
faravahar (US) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 8.0d 2.3d | 6.9d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 56.6 Kbit/s
gabelmoo (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.7d 2.3d | 6.5d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 8 bit/s
longclaw (US) Yes Yes No Yes Y Yes — Running, Valid, Fast, MiddleOnly, BadExit 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.9d 2.3d | 6.4d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 56.6 Kbit/s
maatuska (SE) Yes Yes No Yes N Yes Yes Running, Valid, Fast, MiddleOnly 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.7d 2.3d | 6.4d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 56.6 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 56.6 Mbit/s | 8.4 Mbit/s 56.6 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.2d | 10748.8d 2.3d | 6.1d 100.0% | 98.0% 2.0d | 9.8d 2026-10-22 22:21:06 8 bit/s
tor26 (AT) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 56.6 Mbit/s | 816.0 Kbit/s 56.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.9d 2.3d | 6.7d 100.0% | 98.0% 2.2d | 1.0d 2026-10-22 22:21:06 8 bit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
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.