Hostname
app.minware.com
Last fetched
app.minware.com resolves to 18.155.107.115, announced in 18.155.107.0/24 by AMAZON-02 - Amazon.com, Inc. in IN. app.minware.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
- 18.155.107.115
18.155.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 18.155.107.22
18.155.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 18.155.107.45
18.155.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 18.155.107.55
18.155.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 3.171.153.104
3.171.152.0/22 · AMAZON-02 - Amazon.com, Inc. · Houston, US
- 3.171.153.114
3.171.152.0/22 · AMAZON-02 - Amazon.com, Inc. · Houston, US
- 3.171.153.74
3.171.152.0/22 · AMAZON-02 - Amazon.com, Inc. · Houston, US
- 3.171.153.8
3.171.152.0/22 · AMAZON-02 - Amazon.com, Inc. · Houston, US
- 52.85.78.119
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.124
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.41
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.86
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
IPv6 resolution
No AAAA record for app.minware.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for app.minware.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.
Subdomains
| Subdomain |
|---|
| preview.app.minware.com |
Showing 1 of 2. View all subdomains →
Mail and authentication
Nameservers
- ns-164.awsdns-20.com
- ns-680.awsdns-21.net
- ns-1268.awsdns-30.org
- ns-2035.awsdns-62.co.uk
Threat-feed evidence
History
Related pages
Pivot from app.minware.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: "app.minware.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.