FERDINAND-BILSTEIN-ENNEPETAL-NET
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 8 blocks across 3 clusters |
| Cluster ID | 204679346 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.159.32.16/28 | FERDINAND-BILSTEIN-ENNEPETAL-NET | RIPE | ASSIGNED PA | ● low |
| 80.150.255.48/28 | FERDINAND-BILSTEIN-ENNEPETAL-NET | RIPE | ASSIGNED PA | ● low |
| 87.190.33.112/28 | FERDINAND-BILSTEIN-ENNEPETAL-NET | RIPE | ASSIGNED PA | ● low |
| 2003:4d:19::/48 | FERDINAND-BILSTEIN-ENNEPETAL-NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “FERDINAND BILSTEIN” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- FERDINAND-BILSTEIN-DURMERSHEIM-NET 2 blocks
- FERDINAND-BILSTEIN-WUPPERTAL-NET 2 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE