LEXCOM TELECOM
Cluster stats
| Netblocks | 15 |
| Cluster ID | 191314838 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.168.88.0/22 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.88.0/23 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.88.0/24 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.89.0/24 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.90.0/24 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.90.0/23 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.91.0/24 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 2804:5748::/32 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 2804:5748::/33 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 2804:5748:8000::/33 | LEXCOM TELECOM | BGP | ANNOUNCED | ● high |
| 45.168.89.36/30 | UNKNOWN | LACNIC | reassigned | ● medium |
| 2804:5748::/32 | UNKNOWN | LACNIC | allocated | ● medium |
| 80.152.44.152/29 | LEXCOM-IS | RIPE | ASSIGNED PA | ● low |
| 87.130.120.176/28 | LEXCOM-MUENCHEN-NET | RIPE | ASSIGNED PA | ● low |
| 2003:fd:810::/48 | LEXCOM-MUENCHEN-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(15 of 15)
Possible discrepancies (1)
These blocks are registered to LEXCOM TELECOM 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:fd:810::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
NIC Handles
AS268056
DTAG-NIC
DUMY-RIPE
DUMY-RIPE