HEIDELBERGCEMENT-GESEKE-NET
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2003:c1:d022::/48) |
| Cluster ID | 213835843 |
| 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 · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.25.79.96/29 | HEIDELBERGCEMENT-GESEKE-NET | RIPE | ASSIGNED PA | ● low |
| 93.241.43.64/29 | HEIDELBERGCEMENT-GESEKE-NET | RIPE | ASSIGNED PA | ● low |
| 2003:c1:d022::/48 | HEIDELBERGCEMENT-GESEKE-NET | RIPE | ASSIGNED | ● low |
| 2003:f6:1815::/48 | HEIDELBERGCEMENT-GESEKE-NET | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
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