Zetcon Ingenieure GmbH
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 22 |
| IPv6 | 10 prefixes (largest 2003:100:6017::/48) |
| Cluster ID | 213424731 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 11 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
3 weekly snapshots · JSON
22
0 netblocks since 2026-07-13
2026-07-13
peak 22
2026-07-26
IP Ranges (22)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.109.206.96/28 | Zetcon Ingenieure GmbH | RIPE | ASSIGNED PA | ● high |
| 80.155.142.200/29 | ZETCON-INGENIEURE-DUESSELDORF-NET | RIPE | ASSIGNED PA | ● low |
| 87.130.100.176/29 | ZETCON-INGENIEURE-AUGSBURG-NET | RIPE | ASSIGNED PA | ● low |
| 91.24.3.208/29 | ZETCON-INGENIEURE-PFORZHEIM-NET | RIPE | ASSIGNED PA | ● low |
| 91.25.180.168/29 | ZETCON-INGENIEURE-BERLIN-NET | RIPE | ASSIGNED PA | ● low |
| 91.25.221.192/29 | ZETCON-INGENIEURE-DRESDEN-NET | RIPE | ASSIGNED PA | ● low |
| 93.240.193.24/29 | ZETCON-INGENIEURE-HANNOVER-NET | RIPE | ASSIGNED PA | ● low |
| 93.241.47.88/29 | ZETCON-INGENIEURE-ESSEN-NET | RIPE | ASSIGNED PA | ● low |
| 193.218.19.168/29 | ZETCON-INGENIEURE-GMBH-NET | RIPE | ASSIGNED PA | ● low |
| 217.239.153.8/29 | ZETCON-INGENIEURE-BERLIN-NET | RIPE | ASSIGNED PA | ● low |
| 217.239.195.144/29 | ZETCON-INGENIEURE-MUENCHEN-NET | RIPE | ASSIGNED PA | ● low |
| 217.239.232.224/29 | ZETCON-INGENIEURE-HAMBURG-NET | RIPE | ASSIGNED PA | ● low |
| 2003:e7:8812::/48 | ZETCON-INGENIEURE-ESSEN-NET | RIPE | ASSIGNED | ● low |
| 2003:e7:901e::/48 | ZETCON-INGENIEURE-HANNOVER-NET | RIPE | ASSIGNED | ● low |
| 2003:ee:381f::/48 | ZETCON-INGENIEURE-DUESSELDORF-NET | RIPE | ASSIGNED | ● low |
| 2003:f1:1023::/48 | ZETCON-INGENIEURE-BERLIN-NET | RIPE | ASSIGNED | ● low |
| 2003:fc:9813::/48 | ZETCON-INGENIEURE-AUGSBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:fc:a821::/48 | ZETCON-INGENIEURE-HAMBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:fc:f019::/48 | ZETCON-INGENIEURE-PFORZHEIM-NET | RIPE | ASSIGNED | ● low |
| 2003:fe:7011::/48 | ZETCON-INGENIEURE-MUENCHEN-NET | RIPE | ASSIGNED | ● low |
| 2003:100:6017::/48 | ZETCON-INGENIEURE-BERLIN-NET | RIPE | ASSIGNED | ● low |
| 2003:101:5833::/48 | ZETCON-INGENIEURE-DRESDEN-NET | RIPE | ASSIGNED | ● low |
IPv6 ranges (10)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(22 of 22)
Possible discrepancies (10)
These blocks are registered to Zetcon Ingenieure GmbH 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.
| 2003:ee:381f::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:e7:8812::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:e7:901e::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:fc:9813::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:fe:7011::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:fc:a821::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:100:6017::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:f1:1023::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:fc:f019::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:101:5833::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE
NORDERSTEDT-MNT
ORG-ZIG4-RIPE
TXX-MNT