Keyweb AG
DE-KEYWEB-TRIPEPI
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 238 blocks across 134 clusters |
| Cluster ID | 211281893 |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.118.72.176/28 | DE-KEYWEB-TRIPEPI | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “DE KEYWEB” — 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.
- DE-KEYWEB-AAA 21 blocks
- DE-KEYWEB-UNISTER 6 blocks
- DE-KEYWEB-DMSOLUTIONS 6 blocks
- DE-KEYWEB-XTRAMEDIA 4 blocks
- DE-KEYWEB-INCOWIA 4 blocks
- DE-KEYWEB-LAMPART 4 blocks
- DE-KEYWEB-NEWSHELL 4 blocks
- DE-KEYWEB-PROMAX 4 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Keyweb Haunschmid via Keyweb AG sub-allocation
- Keyweb Poeschek via Keyweb AG sub-allocation
- Keyweb Synapse via Keyweb AG sub-allocation
- Keyweb via Keyweb AG sub-allocation
- Keyweb Draxento1 via Keyweb AG sub-allocation
- Keyweb Draxento2 via Keyweb AG sub-allocation
- Keyweb Rootbash via Keyweb AG sub-allocation
- Keyweb Vpn via Keyweb AG sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KEYWEB-MNT