Hostname

akapi.eduhxh.com

Last fetched Wed, 23 Sep 2026 00:19:20 GMT

akapi.eduhxh.com resolves to 106.225.194.41, announced in 106.225.192.0/18 by CT-Jiangxi-IDC - CHINANET Jiangx province IDC network in CN. akapi.eduhxh.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

106.225.194.41
106.225.192.0/18 · CT-Jiangxi-IDC - CHINANET Jiangx province IDC network
113.142.207.41
113.142.128.0/17 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
117.68.56.41
117.68.56.0/22 · CHINANET-HEFEI-QIMENLU-IDC - China Telecom · Hefei, CN
124.226.72.41
124.226.72.0/22 · CHINATELECOM-Guangxi-Nanning-IDC - CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.
150.138.101.41
150.138.96.0/19 · CHINATELECOM-SHANDONG-QINGDAO-IDC - Qingdao,266000 · Jinan, CN
150.138.253.41
150.138.224.0/19 · CHINATELECOM-SHANDONG-JINAN-IDC - Jinan,250000 · Jinan, CN
171.107.86.41
171.107.84.0/22 · ASEAN-INTERNATIONAL-INFORMATION-GARDEN-IDC - China Telecom
27.128.217.41
27.128.208.0/20 · CHINATELECOM-Hebei-Langfang-IDC - Langfang,Hebei province, P.R.China · Shijiazhuang, CN
42.101.56.41
42.101.56.0/22 · CHINATELECOM-HEILONGJIANG-HANAN-IDC - Haerbing , Heilongjiang Province, P.R.China. · Harbin, CN
58.221.32.41
58.208.0.0/12 · CHINANET-BACKBONE - No.31,Jin-rong Street · Nanjing, CN

IPv6 resolution

No AAAA record for akapi.eduhxh.com is recorded in WhisperGraph.

Attribution

chinanet jiangx province idc

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for akapi.eduhxh.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Threat-feed evidence

History

Pivot from akapi.eduhxh.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "akapi.eduhxh.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

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