SDMN

BGP inherited
Cluster stats
Netblocks7
Cluster ID209574054
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.4.109.168/29 SDMN RIPE ASSIGNED PA ● low
78.5.67.136/29 SDMN RIPE ASSIGNED PA ● low
78.5.67.144/30 SDMN RIPE ASSIGNED PA ● low
78.6.155.208/29 SDMN RIPE ASSIGNED PA ● low
78.6.158.64/29 SDMN RIPE ASSIGNED PA ● low
78.7.160.16/30 SDMN RIPE ASSIGNED PA ● low
85.20.171.140/30 SDMN 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.
  • Lsdmnetbar 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

ALBACOM-MNT BTI-MNT DUMY-RIPE DUMY-RIPE