Hostname
app.prismsl.net
Last fetched
app.prismsl.net resolves to 16.15.0.37, announced in 16.15.0.0/23 by AMAZON-02 - Amazon.com, Inc. in US. app.prismsl.net 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
- 16.15.0.37
16.15.0.0/23 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 16.15.4.203
16.15.4.0/23 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.112.59
52.219.112.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.113.107
52.219.113.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.113.123
52.219.113.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.117.155
52.219.117.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.117.67
52.219.117.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.120.35
52.219.120.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.121.107
52.219.121.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.193.123
52.219.193.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.194.19
52.219.194.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.194.35
52.219.194.0/24 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.216.211
52.219.216.0/23 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.216.75
52.219.216.0/23 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 52.219.220.243
52.219.220.0/23 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
IPv6 resolution
No AAAA record for app.prismsl.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for app.prismsl.net. 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
Related pages
Pivot from app.prismsl.net 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: "app.prismsl.net"})-[: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.