Hao De
HAODE
Registry
Cluster stats
| Netblocks | 6 |
| All fragments | 9 blocks across 3 clusters |
| Cluster ID | 208789211 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 18 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 116.246.22.0/30 | HAODE | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 180.168.1.140/30 | HAODE | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.80.212.36/30 | HAODE-CO | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 59.44.194.204/32 | HaoDe | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 112.65.176.196/30 | haode | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.26.221.170/32 | haode | APNIC | ASSIGNED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “HAODE” — 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.
- HAODE-HOSPITAL-TJ 2 blocks
- HAODE-NETBAR 1 blocks
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.
- Hao De Zhuan Xian sub-allocation
- NANJING-HAODEMAI-CORP via No.31,Jin-rong Street sub-allocation
- suzhou-WEIDULI-SHAODE-CORP via China Telecom Next Generation Carrier Network sub-allocation
- CHANGZHOU-HAODE-NETBAR sub-allocation
- MAIHAODENGJX via CNCGROUP IP network of ShangHai IDC sub-allocation
- Ning Bo Hao De Wang Luo Ke Ji You Xian G via CNCGROUP IP network of ShangHai IDC sub-allocation
- Yu Chaode sub-allocation
- Chaodeestarch_2004 via Royal Thai Armed Force Headquarters sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AC1591-AP
AC1718-AP
CC1699-AP
CC1699-AP
MAINT-CHINANET-LN
MAINT-CHINANET-SH
MAINT-CNCGROUP-SH
MAINT-CNCGROUP-SX
QJR7-AP
QJR7-AP
SY2095-AP
SY2095-AP
+6 more