Hostname
network.yamaha.com
Last fetched
network.yamaha.com resolves to 18.154.63.101, announced in 18.154.62.0/23 by AMAZON-02 - Amazon.com, Inc. in DE. network.yamaha.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.154.63.101
18.154.62.0/23 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.154.63.16
18.154.62.0/23 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.154.63.66
18.154.62.0/23 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 18.154.63.99
18.154.62.0/23 · AMAZON-02 - Amazon.com, Inc. · Düsseldorf, DE
- 99.84.160.43
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.48
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.87
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.95
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for network.yamaha.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for network.yamaha.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 |
|---|
| inquiry.network.yamaha.com |
| store.network.yamaha.com |
| utx.network.yamaha.com |
| yne.network.yamaha.com |
Showing 4 of 4 subdomains (4 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
- ns-503.awsdns-62.com
- ns-708.awsdns-24.net
- ns-1456.awsdns-54.org
- ns-1572.awsdns-04.co.uk
Threat-feed evidence
History
Related pages
Pivot from network.yamaha.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: "network.yamaha.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.