Skip to content

Autonomous System

AS216458 — HardCore - Hardcore Communication Co., Limited(HK)

Last fetched

AS216458 is an Autonomous System operated by HardCore - Hardcore Communication Co., Limited and registered in HK. As of Sun, 06 Sep 2026 18:17:23 GMT, it announces 2 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS216458Routing diversity2.4/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/216458

Routing footprint

AS216458 announces 2 distinct routed prefixes. The 2-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

13 distinct peers via BGP. The first 13 are listed below.

Peer ASNOperatorCountry
AS10099UNICOM-Global - China Unicom GlobalHK
AS132369XIANGAO-AS-AP - XIANGAO INTERNATIONAL TELECOMMUNICATION LIMITEDHK
AS207190Yuhonet - YUHONET INTERNATIONAL LIMITEDHK
AS23764CTGNet - CTGNetHK
AS31972EMGINECONCEPT-01 - Emagine Concept, Inc.US
AS36002GOMAMI - GoMami NetworksUS
AS396856AS-SHARON - Sharon Networks, LLCUS
AS401586SQUIRREL - Squirrel Networks LLCUS
AS402306AS-DATAFORGE - DataForge Technologies LLCUS
AS49304SAKURA-AS - SAKURA LINK LIMITEDHK
AS5068STACKSINC-GLOBAL - STACKS INCUS
AS54994ML-1432-54994 - Meteverse Limited.CA
AS979NETLAB-SDN - NetLab GlobalUS

Blast radius

Count of dependent hostnames if AS216458 disappeared from the routing table.

5 hostnames depend on this network.Exact count across all 2 announced prefixes. Snapshot Fri, 10 Jul 2026 03:01:01 GMT.

MOAS / hijack watch

Prefixes routed by AS216458 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS216458 is unique to AS216458 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS216458.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS216458"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.