View Family nikolov.cz Details
Relays with effective family member
1045C64A7591B985AEAA2650CEE3DBD38B19CF73 summary:
- Bandwidth Capacity: ~4.52 Gbit/s (4.52 Gbit/s guard capacity)
- Network Influence: 0.32% of overall consensus weight (0.61% guard)
- Network Position: Guard-only (12 total relays, 12 guards)
- Family Support: 12 Happy Families (100%)
- Total Data Transferred: 25 PB (0.40% of 5yr network data)
- Overloaded: 41.7% (5 of 12 relays)
- AROI: nikolov.cz ✓ Validated
- Contact: Viktor Nikolov email:vnikolov[]vnikolov.cz url:nikolov.cz proof:dns-rsa ciissversion:2
Last updated: Thu, 06 Aug 2026 09:16:10 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.
💡 Want to upgrade to ciissversion:3?
All 12 of your relays validate cleanly on CIISS v2 (RSA fingerprint proofs). The new CIISS v3 spec replaces per-relay RSA proofs with a single shared ed25519 family-id proof — same url, one published file for the whole family.
To migrate, change torrc ContactInfo to:
ciissversion:3 url:nikolov.cz proof:uri-familyid-ed25519
And on a secure host, generate the happy-family key:
tor --keygen-family /path/to/myfamily # then deploy myfamily.secret_family_key to every relay's KeyDir
Publish .public_family_id at /.well-known/tor-relay/ed25519-family-id.txt.
Allow ~24h after restarting Tor for Onionoo to refresh family_ids.
Full guide: aroivalidator setup guide.
📋 Issues Across This Operator's Relays (5 affected)
| Issue | Affected relays |
|---|---|
| Transport error | 5 |
See per-relay details with pasteable fix examples in the sections below.
✓ VALIDATED RELAYS (7)
| Nickname | BW Cap (4.52 Gbit/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 | IPv6 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ✓ | TorScale (12) | 575.68 Mbit/s ✓ | 4.6 PB | UP 1mo 1w 2d ago | 99.5%/99.9%/99.8%/99.0% | —/—/—/94.9% | 51.159.195.41 |       |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 3y 5mo 1d ago | 1mo 1w 2d ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 |
| ✓ ⚡︎ | TorZoner2 (12) | 409.51 Mbit/s ✓ | 538 TB | UP 4d 11h 8m ago | 99.1%/99.8%/99.8%/0.0% | —/—/97.8%/— | 37.46.208.212 |  |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 6mo 1w 4d ago | 4d 11h 9m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 |
| ✓ | TorScale3 (12) | 382.33 Mbit/s ✓ | 663 TB | UP 5d 20h 59m ago | 99.5%/99.9%/99.7%/0.0% | —/—/92.9%/— | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 7mo 3w 14h ago | 5d 21h 52s ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 |
| ✓ | TorScale2 (12) | 323.65 Mbit/s ✓ | 4.6 PB | UP 1mo 1w 2d ago | 99.2%/99.8%/99.8%/99.6% | —/—/—/96.5% | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 2y 7mo 1w ago | 1mo 1w 2d ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 |
| ✓ | TorHet3 (12) | 321.20 Mbit/s ✓ | 4.1 PB | UP 1mo 1w 2d ago | 99.2%/99.9%/99.9%/99.3% | —/—/—/97.2% | 5.9.14.30 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 3y 10mo 1d ago | 1mo 1w 2d ago | 2a01:4f8:160:8410::3 |
| ✓ ⚡︎ | TorHet2 (12) | 318.50 Mbit/s ✓ | 4.1 PB | UP 1mo 1w 2d ago | 98.7%/99.7%/99.8%/99.3% | —/—/—/97.0% | 5.9.14.25 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 3y 10mo 1w ago | 1mo 1w 2d ago | 2a01:4f8:160:8410::2 |
| ✓ | TorZoner4 (12) | 301.80 Mbit/s ✓ | 452 TB | UP 1w 6d 7h ago | 99.6%/99.9%/99.9%/0.0% | —/—/97.9%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 6mo 1w 4d ago | 1w 6d 7h ago | 2a00:19a0:3:d0:0:252e:d0d4:1 |
⚠ MISCONFIGURED RELAYS (5)
| Nickname | BW Cap (4.52 Gbit/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 | IPv6 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ⚠ ⚡︎ | TorZoner (12) | 570.74 Mbit/s ✓ | 583 TB | UP 2w 1d 14h ago | 99.3%/99.9%/99.9%/0.0% | —/—/97.9%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 6mo 1w 4d ago | 2w 1d 14h ago | 2a00:19a0:3:d0:0:252e:d0d4:1 |
| ⚠ ⚡︎ | TorScale4 (12) | 413.04 Mbit/s ✓ | 766 TB | UP 1mo 1w 2d ago | 98.9%/99.8%/99.7%/0.0% | —/—/93.1%/— | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 7mo 3w 14h ago | 1mo 1w 2d ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 |
| ⚠ ⚡︎ | TorZoner3 (12) | 400.65 Mbit/s ✓ | 441 TB | UP 1w 3d 2m ago | 99.5%/99.9%/99.9%/0.0% | —/—/97.9%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 6mo 1w 4d ago | 1w 3d 3m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 |
| ⚠ | TorHet (12) | 273.67 Mbit/s ✓ | 3.9 PB | UP 1mo 1w 2d ago | 98.5%/99.7%/99.8%/99.3% | —/—/—/95.2% | 5.9.14.25 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 3y 10mo 1w ago | 1mo 1w 2d ago | 2a01:4f8:160:8410::2 |
| ⚠ | TorHet4 (12) | 225.54 Mbit/s ✓ | 4.1 PB | UP 1mo 1w 2d ago | 99.2%/99.7%/99.8%/99.8% | Match | 5.9.14.30 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 2y 7mo 1w ago | 1mo 1w 2d ago | 2a01:4f8:160:8410::3 |
⚠️ MISCONFIGURED RELAY DETAILS
These relays have AROI configured but validation failed due to errors.
Validation data last updated: 2026-08-06 01:00 UTC
-
TorZoner v2
•
DNS-RSA: Lookup failed: The resolution lifetime expired after 5.002 seconds: Server Do53:8.8.8.8@53 answered The DNS operation timed out.; Server Do53:1.1.1.1@53 answered The DNS operation timed out.; Server Do53:8.8.8.8@53 answered The DNS operation timed out.. Used domain cache after 6 attempts.
• Proof: dns-rsa
• FP:
F4ADC09DDE6768ECBF701612469142EABE7AFCC6📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors -
TorScale4 v2
•
DNS-RSA: Lookup failed: The resolution lifetime expired after 5.002 seconds: Server Do53:8.8.8.8@53 answered The DNS operation timed out.; Server Do53:1.1.1.1@53 answered The DNS operation timed out.; Server Do53:8.8.8.8@53 answered The DNS operation timed out.. Used domain cache after 6 attempts.
• Proof: dns-rsa
• FP:
D7078D13C7799B2A1D788CCF1D43E06DEA67BF2D📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors -
TorZoner3 v2
•
DNS-RSA: Lookup failed: The resolution lifetime expired after 5.002 seconds: Server Do53:8.8.8.8@53 answered The DNS operation timed out.; Server Do53:1.1.1.1@53 answered The DNS operation timed out.; Server Do53:8.8.8.8@53 answered The DNS operation timed out.. Used domain cache after 6 attempts.
• Proof: dns-rsa
• FP:
CF6DBE7694EDD7216612EA9CA3F1169E7D2A837F📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors -
TorHet v2
•
DNS-RSA: Lookup failed: The resolution lifetime expired after 5.002 seconds: Server Do53:8.8.8.8@53 answered The DNS operation timed out.; Server Do53:1.1.1.1@53 answered The DNS operation timed out.; Server Do53:8.8.8.8@53 answered The DNS operation timed out.
• Proof: dns-rsa
• FP:
778DCB9DB6CDD5FF2F1A85571308B492D6DFF962📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors -
TorHet4 v2
•
DNS-RSA: Lookup failed: The resolution lifetime expired after 5.002 seconds: Server Do53:8.8.8.8@53 answered The DNS operation timed out.; Server Do53:1.1.1.1@53 answered The DNS operation timed out.; Server Do53:8.8.8.8@53 answered The DNS operation timed out.. Used domain cache after 6 attempts.
• Proof: dns-rsa
• FP:
D245932673168094C492D5155F64699E251703E9📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors
💡 Fix: Check DNS records, renew SSL certificates, or verify server connectivity.
📖 See the AROI Specification for guidance.