Hostname
cloudapp.picooapps.com
Last fetched
cloudapp.picooapps.com resolves to 184.169.157.113, announced in 184.169.128.0/17 by AMAZON-02 - Amazon.com, Inc. in US. cloudapp.picooapps.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
- 184.169.157.113
184.169.128.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 184.72.35.5
184.72.0.0/18 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 204.236.168.202
204.236.128.0/18 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.8.216.48
52.8.0.0/16 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 54.183.31.74
54.183.0.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 54.193.232.241
54.193.128.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 54.193.53.2
54.193.0.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 54.219.157.228
54.219.128.0/18 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 54.219.87.49
54.219.0.0/17 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
IPv6 resolution
No AAAA record for cloudapp.picooapps.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cloudapp.picooapps.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
- ns-467.awsdns-58.com
- ns-699.awsdns-23.net
- 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
- ns-1036.awsdns-01.org
- ns-1850.awsdns-39.co.uk
Threat-feed evidence
History
Related pages
Pivot from cloudapp.picooapps.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: "cloudapp.picooapps.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.