Hostname
trade.com
Last fetched
trade.com resolves to 162.13.209.4, announced in 162.13.0.0/16 by RACKSPACE-LON - Rackspace Ltd. in GB. trade.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
- 162.13.209.4
162.13.0.0/16 · RACKSPACE-LON - Rackspace Ltd. · London, GB
- 65.8.131.106
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.127
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.19
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.59
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.91.20
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.51
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.57
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.62
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- ******** ********
- Contact emails
- ********@*****.***, admin@trade.com, trade.com@domainsbyproxy.com, trade.com@pointa.org
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
- pdns103.ultradns.biz
- pdns103.ultradns.com
- pdns103.ultradns.net
- pdns103.ultradns.org
MX records
- trade-com.mail.protection.outlook.com
SPF policy
- include: spf1.extsrv.com
- include: spf.protection.outlook.com
- mx: trade.com
- include: spf1.trade.com
- include: spf2.trade.com
Threat-feed evidence
History
Related pages
Pivot from trade.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: "trade.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.