ZRS-TK-NET
Handle
Cluster stats
| Netblocks | 3 · 429 IPv4 addresses |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 208838401 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 92.244.66.224/28 | ZRS-TK-NET | RIPE | ASSIGNED PA | ● low |
| 193.2.210.0/24 | ZRS-TK-NET | RIPE | ASSIGNED PA | ● low |
| 194.249.163.96 – 194.249.163.255 | ZRS-TK-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to ZRS-TK-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 193.2.210.0/24 /24 | authorized for AS2107 — ARNES |
NIC Handles
ARNES-MNT
DUMY-RIPE
DUMY-RIPE