Hostname
api.qttunion.com
Last fetched
api.qttunion.com resolves to 120.53.94.110, announced in 120.53.64.0/18 by TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited in CN. api.qttunion.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 120.53.94.110
120.53.64.0/18 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 152.136.165.32
152.136.164.0/22 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 152.136.62.118
152.136.32.0/19 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 154.8.196.27
154.8.192.0/21 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 211.159.174.153
211.159.174.0/23 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Shenzhen, CN
- 49.232.246.38
49.232.240.0/20 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 49.233.244.218
49.233.192.0/18 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 62.234.191.224
62.234.176.0/20 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 62.234.207.62
62.234.192.0/20 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
- 81.70.71.54
81.70.64.0/18 · TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited · Beijing, CN
IPv6 resolution
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.qttunion.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.
Mail and authentication
Nameservers
- vip3.alidns.com
- vip4.alidns.com
Threat-feed evidence
History
Related pages
Pivot from api.qttunion.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: "api.qttunion.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.