zhijian

Registry
Cluster stats
Netblocks9
All fragments 11 blocks across 3 clusters
Cluster ID211935961
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 7 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
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
116.228.239.8/29 ZHIJIAN-CO APNIC ASSIGNED NON-PORTABLE ● high
58.252.72.55/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.57/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.58/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.59/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.60/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.61/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
58.252.72.62/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low
221.4.148.168/32 zhijian APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “zhijian” — 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: F how networks compare →
11.1% of checked blocks have valid RPKI ROA coverage (1 of 9)
No discrepancies found among checked blocks.

NIC Handles

AC1718-AP CG272-AP CG272-AP LH1067-AP LH1067-AP MAINT-CHINANET-SH MAINT-CNCGROUP-GD