Hostname
xrex.exchange
Last fetched
xrex.exchange resolves to 108.156.201.110, announced in 108.156.200.0/22 by AMAZON-02 - Amazon.com, Inc. in US. xrex.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
- 108.156.201.110
108.156.200.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.201.119
108.156.200.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.201.4
108.156.200.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.201.65
108.156.200.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.171.214.101
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.126
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.17
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.89
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.85.31.103
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.41
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.58
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.86
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.175.246.117
- 3.175.246.21
- 3.175.246.29
- 3.175.246.52
IPv6 resolution
No AAAA record for xrex.exchange is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
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.
Sample inbound links
Mail and authentication
Nameservers
- ns-450.awsdns-56.com
- ns-587.awsdns-09.net
- ns-1205.awsdns-22.org
- ns-1687.awsdns-18.co.uk
MX records
- inbound-smtp.us-east-1.amazonaws.com
Threat-feed evidence
History
Related pages
Pivot from xrex.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: "xrex.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.