Hostname
qni.com
Last fetched
qni.com resolves to 15.197.225.128, announced in 15.197.224.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. qni.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
- 15.197.225.128
15.197.224.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 3.33.251.168
3.33.240.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 47.111.130.122
47.111.0.0/16 · ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd. · Hangzhou, CN
- 115.223.34.53
115.223.32.0/22 · CHINATELECOM-ZHEJIANG-WENZHOU-IDC - WENZHOU, ZHEJIANG Province, P.R.China. · Wenzhou, CN
- 8.230.123.148
IPv6 resolution
No AAAA record for qni.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:120
- Registrant organisation
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
- ********@*****.***, gebinbin@msn.com
Subdomains
| Subdomain |
|---|
| admin.qni.com |
| apptest2.qni.com |
| editor.qni.com |
| editortest2.qni.com |
| file.qni.com |
| huagui.qni.com |
| mp.qni.com |
| rz.qni.com |
| ugc.qni.com |
| www.qni.com |
| zhaoshang.qni.com |
Showing 11 of 11 subdomains (11 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns47.domaincontrol.com
- ns48.domaincontrol.com
- ns11.xincache.com
- ns12.xincache.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mxbiz1.qq.com
- mxbiz2.qq.com
Threat-feed evidence
History
Related pages
Pivot from qni.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: "qni.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.