Hostname
satya9.com
Last fetched
satya9.com resolves to 108.138.7.113, announced in 108.138.0.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. satya9.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
- 108.138.7.113
108.138.0.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.7.122
108.138.0.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.7.43
108.138.0.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.7.54
108.138.0.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.224.106.120
13.224.106.0/24 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.224.106.13
13.224.106.0/24 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.224.106.72
13.224.106.0/24 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.224.106.75
13.224.106.0/24 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.227.192.65
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.88
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.93
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.94
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 3.171.38.16
- 3.171.38.37
- 3.171.38.61
- 3.171.38.91
IPv6 resolution
No AAAA record for satya9.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- 36a6586f82644cf5a3167e0625e64de2.protect@withheldforprivacy.com
Subdomains
| Subdomain |
|---|
| www.satya9.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-183.awsdns-22.com
- ns-842.awsdns-41.net
- ns-1283.awsdns-32.org
- ns-1753.awsdns-27.co.uk
Threat-feed evidence
History
Related pages
Pivot from satya9.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: "satya9.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.