Hostname
extended.exchange
Last fetched
extended.exchange resolves to 18.64.141.110, announced in 18.64.141.0/24 by AMAZON-02 - Amazon.com, Inc. in BH. extended.exchange 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.64.141.110
- 18.64.141.32
- 18.64.141.35
- 18.64.141.70
- 3.168.122.105
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.126
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.14
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.63
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.174.46.117
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.119
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.40
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.90
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 31.43.160.6
31.43.160.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 31.43.161.6
31.43.161.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
No AAAA record for extended.exchange is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:895
- Registrant organisation
- privacy protection
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-302.awsdns-37.com
- ns-742.awsdns-28.net
- ns-1372.awsdns-43.org
- ns-1863.awsdns-40.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from extended.exchange 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: "extended.exchange"})-[: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.