caizhengju

Registry
Cluster stats
Netblocks10
All fragments 12 blocks across 2 clusters
Cluster ID211859962
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
59.44.214.46/32 CaiZhengJu APNIC ASSIGNED NON-PORTABLE ● low
59.45.244.34/32 CaiZhengJu APNIC ASSIGNED NON-PORTABLE ● low
61.161.92.117 – 61.161.92.121 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
123.157.142.176/30 CAIZHENGJU APNIC ASSIGNED NON-PORTABLE ● low
218.26.56.182/32 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
218.26.57.126/32 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
218.26.59.70/32 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
218.26.71.232/30 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
218.26.183.198/32 caizhengju APNIC ASSIGNED NON-PORTABLE ● low
222.179.93.152/30 caizhengju APNIC ALLOCATED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC2530-AP CC1699-AP CC1699-AP JQ16-AP JQ16-AP LL1125-AP LL1125-AP MAINT-CHINANET-CQ MAINT-CHINANET-LN MAINT-CNCGROUP-SX MAINT-CNCGROUP-ZJ YC1161-AP +3 more