IMT-Systems GmbH
DE-IMT-SYSTEMS
Cluster stats
| Netblocks | 14 |
| All fragments | 16,500 blocks across 9,941 clusters |
| Cluster ID | 191635365 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (14)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.98.70.192/26 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 82.98.73.0/24 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 82.98.89.216/29 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 82.98.89.224/29 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 185.236.50.0/27 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 212.224.83.160/27 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 212.224.108.128/25 | DE-IMT-SYSTEMS | RIPE | ASSIGNED PA | ● low |
| 2a01:7e0:0:201::/64 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a02:2e0:300::/64 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a02:2e0:3ec::/48 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a02:2e0:3ed::/48 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a13:9d40::/48 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a13:9d40:700::/48 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
| 2a13:9d40:710::/48 | DE-IMT-SYSTEMS | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(14 of 14)
Possible discrepancies (1)
These blocks are registered to DE-IMT-SYSTEMS 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.
| 2a02:2e0:3ed::/48 /48 | authorized for AS12306 — Plus.line AG |
NIC Handles
DUMY-RIPE
DUMY-RIPE
IMT-SYSTEMS-MNT
MNT-FIRSTCOLO
PLUSLINE-MNT