RASCOM-INET
Cluster stats
| Netblocks | 18 |
| All fragments | 23 blocks across 2 clusters |
| Cluster ID | 191929589 |
| 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 (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.64.96.0/22 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.100.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.101.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.102.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.103.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.104.96/28 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.108.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.110.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 80.64.111.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 81.27.241.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 81.27.242.0/26 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 81.27.242.128/27 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 81.27.252.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 185.5.160.128/25 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 185.5.161.0/26 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 185.5.161.128/25 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 185.5.162.0/24 | RASCOM-INET | RIPE | ASSIGNED PA | ● low |
| 185.5.163.0/24 | RASCOM-INET | 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
(18 of 18)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
RASCOM-MNT