View Relay "Aatrox"

Fingerprint: 3791D12AFD71DFE3BF643BFF3D9A2B739D160E19 | Operator: exitnode.dk v3 (8 relays) ✓ Validated | Family: 8 relays | url:https://exitnode.dk... | AS213693 | Denmark | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (15.7s, 53rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 25 Kbit/s Median
Stability
Not Overloaded | UP 1d 6h 33m ago
Reachability
IPv4: 8/9 | v6: 7/8 (Directory Auths)
First Seen
1d 6h 7m ago
BW Weight
0.00% of Network | 50 Mbit/s Observed By Relay
Version
0.4.9.15 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: Time Known below threshold : Time Known 1.2 days is below 8 days requirement (6.8 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.
  • 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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
31.56.4.49:443
[2a0f:85c1:b36:16f::1]:443
Exit Address
31.56.4.49
Reachability (Directory Authorities)
IPv4
8/9
IPv6
7/8 (1 don't test)
Location
Country
Denmark Denmark
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS213693
AS Name
Imad Nabil Daher (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (7/8 DA) 7/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 50.1 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: 1.2d (0/9 DA above threshold)
Min/Max: 1.2d / 1.2d (8/9 DA, Voting / Total Eligible)		 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Uptime Below (0/9 DA) 1.3d (R) ≥3.3d - 3.3d (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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 1.2d (0/9 DA above threshold)
Min/Max: 1.2d / 1.2d (8/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.8 more days) Median: 1.2d (0/9 DA above threshold)
Min/Max: 1.2d / 1.2d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 50.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (8/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
50.09 Mbit/s
Advertised Bandwidth
50.09 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-08 08:01:41

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

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 6h 33m 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
1d 6h 7m ago (2026-11-07 02:00:00)
Last Seen
2h 7m 1s ago (2026-11-08 06:00:00)
Last Restarted
1d 6h 33m ago (2026-11-07 01:33:10)
Last Changed Address
2026-11-07 02:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-07 23:00 UTC

AROI Domain (?)
exitnode.dk
Operator Validation
Validated (8/8 relays)
This Relay
Validated (uri-familyid-ed25519)
Contact
url:https://exitnode.dk proof:uri-familyid-ed25519 ciissversion:3
Family Configuration
Family Support
Happy Families (8) — Has family-cert in server descriptor (guide) | View Full Family (8)
MyFamily (legacy declarations) — none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.7s, 53rd percentile)
Query Domain
a15f83f0e0c441f2b179d3305b2b7f6c.3791d12a.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
NeelTorExit6B (US) ED90B337FE236C0A5D8EEF5AB08DCF31BC07DBD2
Exit Address Used
31.56.4.49
Per-Instance Results
Cross Validation Attempt 1: Success, 13.6s (cv1_w1)
Cross Validation Attempt 2: Success, 15.8s (cv3_w1)
Cross Validation Attempt 3: Success, 17.6s (cv4_w1)
Tested: 2026-11-07 20:05:56 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
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 31.56.4.49:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sun, 08 Nov 2026 08:06:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

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) No — — — Y No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 11.2d 1.3d | 3.4d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 8 bit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 8.6d 1.3d | 3.4d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 50.1 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 8.0d 1.3d | 3.3d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 50.1 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 12.9d 1.3d | 3.3d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 13.2d 1.3d | 3.3d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 50.1 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 3.2d 1.3d | 3.3d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 50.1 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 50.1 Mbit/s | 8.4 Mbit/s 50.1 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 6577.2d 1.3d | 3.3d 100.0% | 98.0% 1.2d | 9.9d 2026-11-08 01:11:15 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 50.1 Mbit/s | 816.0 Kbit/s 50.1 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.2d | 8d 1.2d | 13.0d 1.3d | 3.4d 100.0% | 98.0% 1.2d | 1.0d 2026-11-08 01:11:15 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.