HMSL

BGP inherited
Cluster stats
Netblocks9
Cluster ID210778354
RegistryRIPE
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
194.179.120.144/29 HMSL RIPE ASSIGNED PA ● low
194.179.120.168/29 HMSL RIPE ASSIGNED PA ● low
194.179.120.184/29 HMSL RIPE ASSIGNED PA ● low
195.53.59.128/29 HMSL RIPE ASSIGNED PA ● low
195.53.83.208/29 HMSL RIPE ASSIGNED PA ● low
195.235.183.80/29 HMSL RIPE ASSIGNED PA ● low
195.235.190.24/29 HMSL RIPE ASSIGNED PA ● low
195.235.190.32/29 HMSL RIPE ASSIGNED PA ● low
195.235.190.144/29 HMSL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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.
  • Hmslegal Ba via SWAN, a.s. sub-allocation
  • jzhmsl via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MAINT-AS3352