MD-RISCOM
Cluster stats
| Netblocks | 2 |
| All fragments | 636 blocks across 142 clusters |
| Cluster ID | 192860725 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.138.105.0/24 | MD-RISCOM | RIPE | ASSIGNED PA | ● low |
| 195.138.108.0/24 | MD-RISCOM-ITNS | 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
(2 of 2)
Possible discrepancies (1)
These blocks are registered to MD-RISCOM 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.
| 195.138.108.0/24 /24 | authorized for AS35346 — SC ITNS.NET SRL |
NIC Handles
DUMY-RIPE
DUMY-RIPE
RISCOM-NOC