DDNET-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 · 526 IPv4 addresses |
| Cluster ID | 209865612 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 13 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 |
|---|---|---|---|---|
| 91.221.216.0/23 | DDNET-NET | RIPE | ASSIGNED PI | ● high |
| 117.239.23.176/28 | DDNET | APNIC | ASSIGNED NON-PORTABLE | ● high |
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 DDNET-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.
| 91.221.216.0/23 /23 | authorized for AS52072 — DD Net Telecommunication d.o.o. |
NIC Handles
AB1061-AP
CDN1-AP
CSD4-AP
DD-NET-MNT
DUMY-RIPE
DUMY-RIPE
MAINT-IN-DOT
NC83-AP
NIR5-AP
ORG-DNTd1-RIPE
ORIONTELEKOM-MNT
RIPE-NCC-END-MNT
+1 more