Hostname
tradegate.direct
Last fetched
tradegate.direct resolves to 13.227.192.106, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. tradegate.direct 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
- 13.227.192.106
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.30
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.62
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.96
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.33.187.11
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.4
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.41
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.94
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.164.124.115
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.18
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.39
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.124.7
18.164.124.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for tradegate.direct is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-175.awsdns-21.com
- ns-700.awsdns-23.net
- ns-1503.awsdns-59.org
- ns-1825.awsdns-36.co.uk
MX records
- tradegate-direct.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- include: spf.sendinblue.com
- mx: tradegate.direct
- include: _spf.atlassian.net
- include: spf.smtp.net
Threat-feed evidence
History
Related pages
Pivot from tradegate.direct 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: "tradegate.direct"})-[: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.