rE-Bo0t.bx1 🧅 Shinobi Relays

Supporting Privacy & Internet Freedom Worldwide

4 Bridges -- Guards -- Middles 1 Exit
📊 METRICS DASHBOARD
metrics.1AEO.com
💚 Network: Checking...
📡 Bandwidth: Loading...
🕐 Updated: --

📈 Network Overview

🌐
0
Total Relays
🗺️
0
Countries
🔄
0
Relay Types
🛰️
0/15
IPv6 Enabled
🌐
This diagram illustrates the flow of a Tor circuit. A user connects via a Bridge or Guard, continues through Middle relays, and exits to the public internet.

📊 Network Flow

👤
User
Origin
Bridge
Obfuscation
🌉
🛡️
Guard
Ingress
🔄
Middle
Decoupling
🚪
Exit
Egress
🌐
Destination
Target

🌉 Bridge Relays

Bridges are unlisted entry points that do not appear in the public Tor directory. They use transport obfuscation to make traffic blend in and evade censorship.

ShinobiKage 👤
Hidden Bridge
Active
FD986C182E6F2797E2B87A31401866FAC8DD5B0F
💾 Purpose Stealth Entry
👁️ Visibility Unlisted
🛡️ Transport Obfs4
💚 Status Check →
ShinobiBoshin 🐲
Hidden Bridge
Active
52BA0AFE63B44BEEB855E714212624409A539FE3
💾 Purpose Stealth Entry
👁️ Visibility Unlisted
🛡️ Transport Obfs4
💚 Status Check →
ShinobiKasumi 🌫️
Hidden Bridge
Active
61EB69AC435D0C33EF5FB33FDBB47E8692F139DF
💾 Purpose Stealth Entry
👁️ Visibility Unlisted
🛡️ Transport Obfs4
💚 Status Check →
ShinobiYami 🌘
Hidden Bridge
Active
C523B28E0E6BE86E472A957A2F7FCD5864ACA18F
💾 Purpose Stealth Entry
👁️ Visibility Unlisted
🛡️ Transport Obfs4
💚 Status Check →

🥷 Primary Relays

Primary relays handle public traffic. The Guard is your long‑term entry point into the Tor network, and the Exit relay is where traffic leaves Tor towards its final destination.

🌏 Asia-Oceania 10 relays
ShinobiMamori 🛡️
jp-relay.brokenbotnet.com
Guard
7F28C3E41DA9FD4A2B8143CB6038304634EDC396
📡 IPv4 158.51.109.143
🛰️ IPv6 2602:fd6f:100:1f::1337:c0de ...:1337:c0de
📍 Location Tokyo, Japan 🇯🇵
📊 Metrics View →
ShinobiKenshin ⚔️
tor-exit.brokenbotnet.com
Exit
64CE119D87F0A28F31D74280FB9675D880CA4BFA
📡 IPv4 172.234.92.148
🛰️ IPv6 2400:8905:e001:10f::1337:c0de ...:1337:c0de
📍 Location Osaka, Japan 🇯🇵
📊 Metrics View →
ShinobiTora 🐯
kr-relay.brokenbotnet.com
Middle
A6A2A807338167A5E58F4DD2D4CD0817AF3DD562
📡 IPv4 158.247.199.231
🛰️ IPv6 2401:c080:1c01:68e::1337:c0de ...:1337:c0de
📍 Location Seoul, South Korea 🇰🇷
📊 Metrics View →
ShinobiKaimon ⛩️
sg-relay.brokenbotnet.com
Middle
0EEE0B1EED5E35E1E3F2575CD0AFF160925FA63F
📡 IPv4 149.28.132.118
🛰️ IPv6 2401:c080:1400:10fa::1337:c0de ...:1337:c0de
📍 Location Singapore, Singapore 🇸🇬
📊 Metrics View →
ShinobiBusouge 🌺
my-relay.brokenbotnet.com
Middle
CA7E23C44E6D6F1D8A52A4E1F6CAA11F18108A02
📡 IPv4 124.217.248.240
🛰️ IPv6 N/A N/A
📍 Location Kuala Lumpur, Malaysia 🇲🇾
📊 Metrics View →
ShinobiHasu 🪷
vn-relay.brokenbotnet.com
Middle
586AD06CB8BCE3625D6CC88772CDE4FE56477EE2
📡 IPv4 103.70.115.20
🛰️ IPv6 2401:5b60:0:1::68 ...60:0:1::68
📍 Location Hanoi, Vietnam 🇻🇳
📊 Metrics View →
ShinobiKyuuryuu 🐉
hk-relay.brokenbotnet.com
Guard
D184F8140F3357F84E64BCF51094EA13B18FDD25
📡 IPv4 216.250.97.105
🛰️ IPv6 2406:ef80:1:14a7::1337:c0de ...:1337:c0de
📍 Location Hong Kong, China 🇭🇰
📊 Metrics View →
ShinobiHishoken 🪃
au-relay.brokenbotnet.com
Middle
5F926760730D0229C2F2D16D0DE0E8A3C2682ED1
📡 IPv4 103.73.65.146
🛰️ IPv6 2406:ef80:3:9bc6::1337:c0de ...:1337:c0de
📍 Location Sydney, Australia 🇦🇺
📊 Metrics View →
ShinobiKuma 🐻
ru-relay.brokenbotnet.com
Guard
576E77EE584906041FF504592E5C51EE471707A2
📡 IPv4 176.32.34.179
🛰️ IPv6 2a00:b700:5::fb ...b700:5::fb
📍 Location St.-Petersburg, Russia 🇷🇺
📊 Metrics View →
ShinobiOkami 🐺
tr-relay.brokenbotnet.com
Middle
38FF19F5014E110F196D4AEB81189B375EDA4530
📡 IPv4 45.141.148.185
🛰️ IPv6 2602:fa5d::322 ...:fa5d::322
📍 Location Istanbul, Türkiye 🇹🇷
📊 Metrics View →
🌍 Africa 1 relay
ShinobiShishi 🦁
za-relay.brokenbotnet.com
Middle
A24D263E817AA29F4E1F210AC519EF590DB443CD
📡 IPv4 139.84.241.19
🛰️ IPv6 2a05:f480:3000:2fa6::1337:c0de ...:1337:c0de
📍 Location Johannesburg, South Africa 🇿🇦
📊 Metrics View →

📧 Contact & Abuse Info

Maintained by rE-Bo0t.bx1. We operate with a strict No Logs policy and treat this infrastructure as a Common Carrier.

📧 Operator Email r3bo0tbx1@brokenbotnet.com
🔑 PGP Public Key 0xB3BD6196E1CFBFB4
🪵 Logs Policy 🚫 No Logs Stored
📜 Network Policy ✅ Common Carrier

Abuse Notice: If you've received traffic from exit IPs listed here, this originates from a Tor Exit Node. We cannot identify the originating user or source system.

📖 Glossary

Quick reference for Tor network terminology used throughout this dashboard.

🌉

Bridge

Unlisted entry relay not in the public directory. Uses obfuscation to bypass censorship and help users in restricted regions.

🛡️

Guard

High-stability entry node that clients use for 2-3 months to prevent profiling attacks. Must have proven uptime and bandwidth.

🔀

Middle Relay

Relay that passes traffic between entry and exit nodes. Never sees both source and destination, ensuring anonymity.

🚪

Exit Node

Final relay that connects to the destination. Handles the highest legal risk as traffic appears to originate from it.

🔐

Pluggable Transport

Obfuscation technique that disguises Tor traffic to evade detection and blocking by DPI (Deep Packet Inspection) systems.

🔑

Fingerprint

Unique 40-character identifier (SHA-1 hash) of a relay's public key. Used to verify and reference specific relays.

📊

Bandwidth

Amount of data a relay can transfer per second. Higher bandwidth relays handle more traffic and improve network speed.

🟢

Running Flag

Status flag indicating the relay is currently reachable and operational according to the directory authorities.

Fast Flag

Given to relays in the top 7/8 by bandwidth. Indicates the relay has sufficient speed to handle circuit traffic.

🎯

Stable Flag

Awarded to relays with high uptime. Indicates reliability and makes the relay suitable for long-lived circuits.

📁

HSDir Flag

Hidden Service Directory - stores descriptors for onion services. Requires stable, long-running relays.

Valid Flag

Indicates the relay is recognized by directory authorities and is part of the legitimate Tor network.

StaleDesc Flag

Indicates the relay has an outdated descriptor that hasn't been updated recently. May signal connectivity or configuration issues.

🛡️

Guard Flag

Assigned to high-performance relays suitable for use as entry guards. Requires high bandwidth, stable uptime, and Guard probability.

BadExit Flag

Assigned to exit relays suspected of tampering with traffic or behaving maliciously. Not recommended and should be avoided.

🔱

Authority

Directory authority server that maintains the consensus about which relays are valid, assigns flags, and monitors network health.

🔄

Exit Policy

Configuration that defines which ports and destinations an exit relay will allow. Some exits restrict certain ports or only allow specific traffic.

🌍

Consensus

Agreement among directory authorities about the current state of the Tor network, including which relays are running and their flags.

Frequently Asked Questions

A Bridge is an unlisted Tor relay that doesn't appear in the public directory. It uses obfuscation techniques (like Obfs4) to disguise Tor traffic, helping users bypass censorship in countries where Tor is blocked.
Guard relays are your first hop with proven stability and uptime, protecting against timing attacks by maintaining long-term connections. Middle relays are intermediate hops that can't see both source and destination, providing additional anonymity layers without special requirements.
Exit nodes are the final hop before traffic reaches the internet. They're critical for network health but require careful management, proper abuse handling, and legal understanding. Running an exit provides maximum impact for internet freedom but comes with higher responsibility.
Tor uses onion routing with exactly three hops: either Guard → Middle → Exit, or Bridge → Middle → Exit for censored users. Each relay only knows the previous and next hop, never the full path. All traffic between relays is encrypted, and we maintain a strict no-logs policy. We cannot and do not track user activity.
Obfs4 (Obfuscation 4) is a pluggable transport that makes Tor traffic look like random data instead of identifiable Tor connections. It helps users bypass Deep Packet Inspection (DPI) and censorship systems that block Tor.
No. Guard and Middle relays see encrypted traffic they cannot decrypt. Only Exit nodes see unencrypted traffic to final destinations (use HTTPS!), but never the original source. We maintain zero logs, even if compelled, we have nothing to provide.

🐋 AIO Tor Bridge & Relay Stack

Support Internet Privacy.

Deploy a hardened Tor relays (Guard, Exit, or Bridge) with built-in diagnostics using our all-in-one script.