AXNETS_HK

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks6
IPv6 6 prefixes (largest 2a06:a004:2000::/40)
Cluster ID228032805
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a06:a004:2000::/40 AXNETS_HK RIPE ASSIGNED ● low
2a06:a004:f200::/44 AXNETS_HK RIPE ASSIGNED ● low
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

IPv6 ranges (6)

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
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