Hostname
blue.wane.com
Last fetched
blue.wane.com resolves to 18.66.102.113, announced in 18.66.102.0/24 by AMAZON-02 - Amazon.com, Inc. in DE. blue.wane.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.66.102.113
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.44
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.79
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.85
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.164.240.16
3.164.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 3.164.240.48
3.164.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 3.164.240.54
3.164.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 3.164.240.7
3.164.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 3.168.178.110
3.168.178.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.178.121
3.168.178.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.178.41
3.168.178.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.178.67
3.168.178.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
IPv6 resolution
No AAAA record for blue.wane.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for blue.wane.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 |
|---|
| c.blue.wane.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-386.awsdns-48.com
- ns-582.awsdns-08.net
- ns-1030.awsdns-00.org
- ns-1953.awsdns-52.co.uk
Threat-feed evidence
History
Related pages
Pivot from blue.wane.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: "blue.wane.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.