View Contact tor.redlabsdevelopment.de Details
📋 Contact & Network Overview
- AROI: tor.redlabsdevelopment.de⚠ Misconfigured
- 1 relay, 0% valid, 100% v3
- Contact: email:tor[]redlabsdevelopment.de url:https://tor.redlabsdevelopment.de proof:uri-familyid-ed25519 offlinemasterkey:y ciissversion:3 pgp:B549C91B7C50E91C8FEDEEFA45D5AE6A61D54573
- ⚠ Self-asserted
url:claims (unverified): 1 relay publishurl:tor.redlabsdevelopment.dein their ContactInfo but are NOT in any of this operator's validated relays'effective_family. Allium does not authenticate these claims — they are surfaced here so the operator has visibility. They could be the operator's own additional relays that forgot BOTHfamilyandciissversiondeclarations (fix both in their ContactInfo + torrc to merge them under this operator), OR third-party operators spoofing this domain (in which case the operator should investigate / report). These relays do not contribute to this operator's validated metrics, bandwidth totals, or relay counts anywhere on the site. - Hash: ad127ec2606eb9fe1a534b4c364c37ef
- Countries:
Germany (1)
Network Summary:
- Bandwidth Capacity: ~17.90 Mbit/s (17.90 Mbit/s middle)
- Total Data Transferred: 144 GB
- Network Influence: 0.00% of overall consensus weight (0.00% middle)
- Network Position: Middle-only (1 total relay, 1 middle)
📊 Operator Intelligence
- Network Diversity: , 1 network (rare)
- Geographic Diversity: , 1 country
- Infrastructure Diversity: , 1 platform
- Bandwidth Capacity Measurements: 1/1 relays measured by authorities
- Performance Insights: Overall CW/BW: . -59% lower than 1070 network average. 23th percentile with 842 median.
- Operational Maturity: Operating since 2026-06-26 (all deployed together)
- Version Compliance: , 1 (100%) compliant
- Version Status: , 1 (100%) recommended
- Family Support: 1 None (100%)
⏰ Relay Reliability
- Overall Uptime:
30d 98.7% (1 relays)
- ✅ No statistical outliers detected - consistent performance across all relays
- Offline: 0 relays
Reliability data available for 1/1 relays, from 2026-07-03 01:00:00 UTC
🏷️ Flag Reliability
Flag-specific uptime percentages (1M):
⚡ Fast Relay:
98.6%
🟢 Running Operation:
98.7%
📁 Directory Services:
98.7%
Excellent (>99%),
Below average (<μ of network),
Poor (≥2σ from network μ)
, from 2026-07-03 01:00:00 UTC
🚀 Flag Bandwidth Performance
Flag-specific bandwidth averages:
No flag bandwidth data available for this operator.
High performance (>1.5x μ),
Below average (<μ of network),
Poor (≥2σ from network μ)
Last updated: Fri, 03 Jul 2026 03:11:23 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.
⏳ PENDING ONIONOO REFRESH (1)
| Nickname | BW Cap (17.90 Mbit/s) | Total Data | Uptime/Downtime | Uptime (1M/6M/1Y/5Y) | Flag Uptime (1M/6M/1Y/5Y) | IPv4 | Flags | DNS | Family | Country | AS Number | AS Name | Platform | First Seen | Last Restarted | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ⏳ v3 | TorHostingByRedLabs | 17.90 Mbit/s ✓ | 144 GB | UP 4h 54m 31s ago | 98.7%/0.0%/0.0%/0.0% | Match | 87.135.158.205 |     |
NA | None |
DE
|
AS3320 | Deutsche Telekom AG | Linux | 6d 11h 13m ago | 4h 56m 43s ago |
⏳ WAITING FOR ONIONOO TO REFRESH
These relays declared ciissversion:3 but Onionoo hasn't picked up family_ids yet. This is transient — Onionoo refreshes hourly; expect resolution within 24 hours of restarting Tor with the happy-family directive.
Validation data last updated: 2026-07-02 19:00 UTC
-
TorHostingByRedLabs v3
•
URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof
• Proof: uri-familyid-ed25519
• FP:
83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B💡 Fix:Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).📋 Paste:curl "https://onionoo.torproject.org/details?lookup=83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor
💡 No action needed if you recently changed torrc; wait < 24h. If still pending after 24h: verify FamilyId line in torrc and that .secret_family_key is in Tor KeyDir.
📖 See the AROI Specification for guidance.
⚠ MISCONFIGURED RELAYS (1)
| Nickname | BW Cap (17.90 Mbit/s) | Total Data | Uptime/Downtime | Uptime (1M/6M/1Y/5Y) | Flag Uptime (1M/6M/1Y/5Y) | IPv4 | Flags | DNS | Family | Country | AS Number | AS Name | Platform | First Seen | Last Restarted | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ⚠ | TorHostingByRedLabs | 17.90 Mbit/s ✓ | 144 GB | UP 4h 54m 31s ago | 98.7%/0.0%/0.0%/0.0% | Match | 87.135.158.205 | |
NA | None |
DE
|
AS3320 | Deutsche Telekom AG | Linux | 6d 11h 13m ago | 4h 56m 43s ago |
⚠️ MISCONFIGURED RELAY DETAILS
These relays have AROI configured but validation failed due to errors.
Validation data last updated: 2026-07-02 19:00 UTC
-
TorHostingByRedLabs v3
•
URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof
• Proof: uri-familyid-ed25519
• FP:
83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B💡 Fix:Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).📋 Paste:curl "https://onionoo.torproject.org/details?lookup=83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor
💡 Fix: Check DNS records, renew SSL certificates, or verify server connectivity.
📖 See the AROI Specification for guidance.