MIZARPROJECT-NET_K-T
Cluster stats
| Netblocks | 6 |
| Cluster ID | 193795407 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.43.133.0/24 | MIZARPROJECT-NET_K-T | RIPE | ASSIGNED PA | ● low |
| 5.43.142.0/23 | MIZARPROJECT-NET_K-T | RIPE | ASSIGNED PA | ● low |
| 5.43.148.0/24 | MIZARPROJECT-NET_K-T | RIPE | ASSIGNED PA | ● low |
| 5.43.154.0/24 | MIZARPROJECT-NET_K-T | RIPE | ASSIGNED PA | ● low |
| 5.199.194.0/23 | MIZARPROJECT-NET_K-T | RIPE | ASSIGNED PA | ● low |
| 134.255.132.0/23 | MIZARPROJECT-NET_K-T | 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
(6 of 6)
RPKI-inferred operator
Joint stock company "For"
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KTEL-MNT