MAI-DGIPI-net
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| Cluster ID | 211215784 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 |
|---|---|---|---|---|
| 89.42.116.32/28 | MAI-DGIPI-net | RIPE | ASSIGNED PA | ● low |
| 2a00:5dc2:d::/48 | MAI-DGiPI-net | RIPE | ALLOCATED-BY-LIR | ● 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 MAI-DGIPI-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.
| 2a00:5dc2:d::/48 /48 | authorized for AS31313 — Serviciul de Telecomunicatii Speciale |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTS-MNT