Hostname

api2.qiecdn.com

Last fetched Wed, 23 Sep 2026 06:57:01 GMT

api2.qiecdn.com resolves to 113.142.212.35, announced in 113.142.128.0/17 by CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network in CN. api2.qiecdn.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

113.142.212.35
113.142.128.0/17 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
115.152.219.35
115.152.0.0/15 · CHINANET-BACKBONE - No.31,Jin-rong Street
117.33.185.35
117.33.128.0/18 · CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network
120.41.32.35
120.40.0.0/14 · CHINANET-BACKBONE - No.31,Jin-rong Street
121.14.9.35
121.8.0.0/13 · CHINANET-BACKBONE - No.31,Jin-rong Street · Guangzhou, CN
123.244.92.35
123.244.0.0/14 · CHINANET-BACKBONE - No.31,Jin-rong Street
182.106.158.35
182.106.152.0/21 · CHINANET-Jiangxi-Jiujiang-IDC - Jiangxi Jiujiang IDC
182.61.128.134
182.61.128.0/23 · CHINATELECOM-SHANDONG-JINAN-IDC - Jinan,250000
183.131.185.35
183.131.185.0/24 · CT-HangZhou-IDC - No.288,Fu-chun Road · Huzhou, CN
183.6.224.65
183.6.224.0/20 · CT-DongGuan-IDC - CHINANET Guangdong province network · Guangzhou, CN
218.94.231.35
218.94.231.0/24 · CHINANET-JIANGSU-SUZHOU-TAIHU-IDC - CHINANET Jiangsu province Suzhou taihu IDC network · Nanjing, CN

IPv6 resolution

No AAAA record for api2.qiecdn.com is recorded in WhisperGraph.

Attribution

chinanet shaanxi province base

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api2.qiecdn.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 api2.qiecdn.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: "api2.qiecdn.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.