Hostname
satrans.com.sa
Last fetched
satrans.com.sa resolves to 15.185.95.215, announced in 15.185.0.0/16 by AMAZON-02 - Amazon.com, Inc. in BH. satrans.com.sa 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
- 15.185.95.215
15.185.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Manama, BH
- 3.122.148.65
3.120.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 77.30.172.26
77.30.168.0/21 · SAUDINETSTC-AS - Saudi Telecom Company JSC · Riyadh, SA
IPv6 resolution
No AAAA record for satrans.com.sa is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for satrans.com.sa. 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.
Subdomains
Showing 2 of 2 subdomains (2 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.
Mail and authentication
Nameservers
- ns20.digicertdns.com
- ns10.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns14.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
- 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
MX records
- satrans-com-sa.mail.protection.outlook.com
SPF policy
- include: spf.ess.de.barracudanetworks.com
- include: spf-uae.emailsignatures365.com
- include: spf.protection.outlook.com
- include: spf.zohomail360.com
Threat-feed evidence
History
Related pages
Pivot from satrans.com.sa 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: "satrans.com.sa"})-[: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.