View Family nikolov.cz Details
Relays with effective family member
D7078D13C7799B2A1D788CCF1D43E06DEA67BF2D summary:
- Bandwidth Capacity: ~4.62 Gbit/s (4.62 Gbit/s guard capacity)
- Network Influence: 0.55% of overall consensus weight (1.15% guard)
- Network Position: Guard-only (12 total relays, 12 guards)
- Family Support: 12 Happy Families (100%)
- Total Data Transferred: 27 PB (0.53% of 5yr network data)
- Overloaded: 33.3% (4 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, 12 Nov 2026 18:49:51 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 (9 affected)
| Issue | Affected relays |
|---|---|
| Transport error | 9 |
See per-relay details with pasteable fix examples in the sections below.
✓ VALIDATED RELAYS (3)
| Nickname | BW Cap (4.62 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ✓ | TorZoner4 (12) | 434.21 Mbit/s ✓ | 950 TB | UP 6d 1h 45m ago | 98.9%/99.5%/99.7%/0.0% | 57.2%/91.2%/93.0%/— | 37.46.208.212 |       |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 9mo 2w 6d ago | 6d 1h 45m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 OK |
| ✓ | TorHet2 (12) | 367.33 Mbit/s ✓ | 4.4 PB | UP 5d 23h 31m ago | 99.2%/99.4%/99.7%/99.3% | 63.0%/89.2%/94.6%/95.9% | 5.9.14.25 |  |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 4y 1mo 2w ago | 5d 23h 32m ago | 2a01:4f8:160:8410::2 OK |
| ✓ ⚡︎ | TorHet3 (12) | 334.65 Mbit/s ✓ | 4.4 PB | UP 5d 23h 31m ago | 98.7%/99.3%/99.7%/99.3% | 81.3%/95.0%/97.8%/96.9% | 5.9.14.30 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 4y 1mo 4d ago | 5d 23h 32m ago | 2a01:4f8:160:8410::3 OK |
⚠ MISCONFIGURED RELAYS (9)
| Nickname | BW Cap (4.62 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ⚠ | TorZoner2 (12) | 526.35 Mbit/s ✓ | 1.0 PB | UP 2d 19h 27m ago | 98.7%/99.4%/99.6%/0.0% | 67.6%/93.1%/94.2%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 9mo 2w 6d ago | 2d 19h 27m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 OK |
| ⚠ | TorZoner3 (12) | 465.32 Mbit/s ✓ | 957 TB | UP 4d 6h 33m ago | 99.2%/99.4%/99.6%/0.0% | 88.2%/94.0%/94.8%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 9mo 2w 6d ago | 4d 6h 34m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 OK |
| ⚠ | TorScale (12) | 436.38 Mbit/s ✓ | 4.9 PB | UP 5d 23h 29m ago | 98.8%/99.2%/99.5%/99.0% | 55.5%/82.8%/91.3%/92.9% | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 3y 8mo 1w ago | 5d 23h 30m ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 OK |
| ⚠ ⚡︎ | TorZoner (12) | 429.91 Mbit/s ✓ | 1.2 PB | UP 6d 1h 45m ago | 99.1%/99.6%/99.7%/0.0% | —/—/98.4%/— | 37.46.208.212 | |
NA | Happy Families |
CZ
|
AS34222 | ZONER a.s. | Linux | 9mo 2w 6d ago | 6d 1h 45m ago | 2a00:19a0:3:d0:0:252e:d0d4:1 OK |
| ⚠ | TorScale4 (12) | 422.08 Mbit/s ✓ | 1.1 PB | UP 5d 23h 29m ago | 99.3%/99.2%/99.5%/0.0% | —/89.3%/89.3%/— | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 10mo 4w 1d ago | 5d 23h 30m ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 OK |
| ⚠ | TorScale3 (12) | 346.99 Mbit/s ✓ | 1.0 PB | UP 5d 23h 29m ago | 98.4%/99.1%/99.4%/0.0% | 66.3%/85.6%/86.9%/— | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 10mo 4w 1d ago | 5d 23h 30m ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 OK |
| ⚠ ⚡︎ | TorHet4 (12) | 324.57 Mbit/s ✓ | 4.4 PB | UP 5d 23h 31m ago | 98.8%/99.2%/99.6%/99.7% | 49.0%/89.2%/94.6%/97.6% | 5.9.14.30 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 2y 10mo 2w ago | 5d 23h 32m ago | 2a01:4f8:160:8410::3 OK |
| ⚠ | TorScale2 (12) | 293.90 Mbit/s ✓ | 4.9 PB | UP 5d 23h 29m ago | 99.3%/99.1%/99.5%/99.5% | 56.7%/79.6%/89.6%/92.7% | 51.159.195.41 | |
NA | Happy Families |
FR
|
AS12876 | Scaleway SAS | Linux | 2y 10mo 2w ago | 5d 23h 30m ago | 2001:bc8:1201:512:da5e:d3ff:fe6c:8241 OK |
| ⚠ ⚡︎ | TorHet (12) | 238.54 Mbit/s ✓ | 4.2 PB | UP 5d 23h 31m ago | 99.1%/99.3%/99.7%/99.3% | 61.7%/92.7%/96.5%/94.7% | 5.9.14.25 | |
NA | Happy Families |
DE
|
AS24940 | Hetzner Online GmbH | Linux | 4y 1mo 2w ago | 5d 23h 32m ago | 2a01:4f8:160:8410::2 OK |
⚠️ MISCONFIGURED RELAY DETAILS
These relays have AROI configured but validation failed due to errors.
Validation data last updated: 2026-11-12 09:05 UTC
-
TorZoner2 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:
3A56376BB965825539D9BBF2E409F316CE57A22E📋 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 4 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 -
TorScale 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 4 attempts.
• Proof: dns-rsa
• FP:
B7B35AFD69A1F8C0453A45FDC92B28824F34F402📋 Paste:curl -v https://nikolov.cz/.well-known/tor-relay/rsa-fingerprint.txt # check for SSL/timeout/refused/HTTP errors -
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 4 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 4 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 -
TorScale3 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 4 attempts.
• Proof: dns-rsa
• FP:
B95A8A85310362945DD0F2D184CC2A50AC875492📋 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 4 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 -
TorScale2 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 4 attempts.
• Proof: dns-rsa
• FP:
56909EDCDFFC04AA38593466F51F3FB2AC63414C📋 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.. Used domain cache after 4 attempts.
• 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
💡 Fix: Check DNS records, renew SSL certificates, or verify server connectivity.
📖 See the AROI Specification for guidance.