H Lkomm
HLkomm
Cluster stats
| Netblocks | 20 |
| Cluster ID | 193381756 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.192.91/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 80.81.195.164/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.184/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 185.0.21.25/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 185.1.208.12/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 185.1.245.5/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 193.178.185.41/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 193.178.185.241/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 194.59.190.86/32 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::3ee1:0:1/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::3ee1:0:2/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:19:1::3ee1:1/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:19:1::3ee1:2/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:2c:1000:0:3ee1:0:1/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:44::3ee1:0:1/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::c:25/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:df::3ee1:0:1/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:184/128 | HLkomm | PEERINGDB | ASSIGNED | ● high |
| 212.122.40.0/29 | HLKOMM | RIPE | ASSIGNED PA | ● low |
| 217.69.226.96/29 | HLKOMM | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(15 of 20)
No discrepancies found among checked blocks.
NIC Handles
AS16097
DUMY-RIPE
DUMY-RIPE
HL-KOMM-MNT