HLNET
Unresolved
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| Cluster ID | 191845017 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.241.160.0/22 | HLNET | APNIC | ALLOCATED PORTABLE | ● low |
| 211.158.9.80/28 | HLNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 211.165.182.0/24 | HLNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to HLNET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 211.165.182.0/24 /24 | authorized for AS9389 — BEIJING SHENZHOU GREATWALL COMMUNICATION |
NIC Handles
AC1601-AP
LN11-AP
MAINT-CNNIC-AP
XP17-AP
XP17-AP
ZF31-AP
ZM891-AP
ZM891-AP