AXNETS_HK
Cluster stats
| Netblocks | 4 |
| All fragments | 33 blocks across 20 clusters |
| Cluster ID | 191671184 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a10:ccc6:6662::/48 | AXNETS_HK | RIPE | ASSIGNED | ● low |
| 2a14:7580:fa20::/44 | AXNETS_HK | RIPE | ASSIGNED | ● low |
| 2a14:7580:ff42::/48 | AXNETS_HK | RIPE | ASSIGNED | ● low |
| 2a14:7581:9902::/48 | AXNETS_HK | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
RPKI-inferred operator
Hanxun Xu
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
AXW-MNT
DUMY-RIPE
DUMY-RIPE