Hostname
amperwave.net
Last fetched
amperwave.net resolves to 108.156.22.127, announced in 108.156.16.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. amperwave.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
- 108.156.22.127
108.156.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.22.86
108.156.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.22.94
108.156.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.22.99
108.156.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 13.227.192.118
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.20
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.4
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.66
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 18.245.162.12
18.245.160.0/22 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 18.245.162.41
18.245.160.0/22 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 18.245.162.49
18.245.160.0/22 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 18.245.162.75
18.245.160.0/22 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 3.161.82.13
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.29
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.34
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.80
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for amperwave.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Showing 12 of 20. View all subdomains →
Mail and authentication
Nameservers
- ns-332.awsdns-41.com
- ns-561.awsdns-06.net
- ns-1237.awsdns-26.org
- ns-1575.awsdns-04.co.uk
Threat-feed evidence
History
Related pages
Pivot from amperwave.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: "amperwave.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.