Hostname
dashboard.transax.com
Last fetched
dashboard.transax.com resolves to 13.226.69.108, announced in 13.226.69.0/24 by AMAZON-02 - Amazon.com, Inc. in HK. dashboard.transax.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
- 13.226.69.108
13.226.69.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.111
13.226.69.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.114
13.226.69.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 13.226.69.53
13.226.69.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 18.66.233.34
18.66.232.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.66.233.67
18.66.232.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.66.233.70
18.66.232.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.66.233.95
18.66.232.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for dashboard.transax.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dashboard.transax.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-89.awsdns-11.com
- ns-624.awsdns-14.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1057.awsdns-04.org
- ns-1723.awsdns-23.co.uk
Threat-feed evidence
History
Related pages
Pivot from dashboard.transax.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: "dashboard.transax.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.