Hostname
api.uu361.app
Last fetched
api.uu361.app resolves to 149.88.68.166, announced in 149.88.68.0/24 by COGNETCLOUD-2 - cognetcloud INC in HK. api.uu361.app 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
- 149.88.68.166
- 149.88.68.17
- 149.88.68.234
- 149.88.68.26
- 149.88.68.42
- 149.88.68.61
- 149.88.68.64
- 154.12.50.79
154.12.50.0/24 · NETLAB-SDN - NetLab Global · Los Angeles, US
- 154.36.173.102
- 154.40.35.132
- 154.44.29.172
154.44.29.0/24 · NETLAB-SDN - NetLab Global · Hong Kong, HK
- 154.44.29.177
154.44.29.0/24 · NETLAB-SDN - NetLab Global · Hong Kong, HK
- 154.44.29.215
154.44.29.0/24 · NETLAB-SDN - NetLab Global · Hong Kong, HK
- 154.44.30.253
154.44.30.0/24 · NETLAB-SDN - NetLab Global · Hong Kong, HK
- 198.44.185.200
198.44.185.0/24 · HKCLOUDX - VpsQuan L.L.C. · Hong Kong, HK
- 198.44.187.100
198.44.187.0/24 · HKCLOUDX - VpsQuan L.L.C. · Hong Kong, HK
- 198.44.187.101
198.44.187.0/24 · HKCLOUDX - VpsQuan L.L.C. · Hong Kong, HK
- 83.229.126.159
83.229.126.0/24 · LUCID-AS-AP - LUCIDACLOUD LIMITED · Mong Kok, HK
IPv6 resolution
No AAAA record for api.uu361.app is recorded in WhisperGraph.
Attribution
cognetcloud
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.uu361.app. 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
- 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
Threat-feed evidence
History
Related pages
Pivot from api.uu361.app 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.uu361.app"})-[: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.