WUXI SECURITY CORP

WUXI-SECURITY-CORP
Registry
Cluster stats
Netblocks7
All fragments 9 blocks across 2 clusters
Cluster ID211906418
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
58.214.9.12/30 WUXI-SECURITY-CORP APNIC ASSIGNED NON-PORTABLE ● high
218.90.169.72/29 WUXI-SECURITY-CORP APNIC ASSIGNED NON-PORTABLE ● high
58.214.25.88/30 WUXI-SECURITY-CORP APNIC ASSIGNED NON-PORTABLE ● low
58.214.25.116/30 WUXI-SECURITY-CORP APNIC ASSIGNED NON-PORTABLE ● low
58.214.25.120/30 WUXI-SECURITY-CORP APNIC ASSIGNED NON-PORTABLE ● low
58.214.36.208/29 wuxi-security-corp APNIC ASSIGNED NON-PORTABLE ● low
218.90.146.12/30 wuxi-security-corp APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “WUXI SECURITY” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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.

Network trust

what's this?
RPKI hygiene: D how networks compare →
42.9% of checked blocks have valid RPKI ROA coverage (3 of 7)
No discrepancies found among checked blocks.

NIC Handles

CH456-AP CH456-AP MAINT-CHINANET-JS QJ129-AP WW1075-AP