HEPINGLU-COM
Cluster stats
| Netblocks | 19 |
| All fragments | 21 blocks across 2 clusters |
| Cluster ID | 193229607 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 122.194.138.0/23 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.144.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.145.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.146.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.147.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.156.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.163.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.164.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.167.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.172.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.174.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.175.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.184.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.185.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.196.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.197.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.202.0/26 | hepinglu-com | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.203.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.194.204.0/24 | HEPINGLU-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
RPKI-inferred operator
CNCGROUP IP network of ShangHai IDC
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
LL58-AP
LL58-AP
MAINT-CNCGROUP-JS