Hostname
shosti.org
Last fetched
shosti.org resolves to 13.126.175.9, announced in 13.126.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IN. shosti.org 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.126.175.9
13.126.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.205.201.122
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.234.197.228
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.108.48.243
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.109.251.47
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 35.154.143.191
35.154.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 43.204.91.137
43.204.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.203.144.181
IPv6 resolution
No AAAA record for shosti.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- dr. shamim hayder talukder
- Contact emails
- tipu@eminence-bd.org
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns-329.awsdns-41.com
- dns1.registrar-servers.com
- dns2.registrar-servers.com
- ns-836.awsdns-40.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-1498.awsdns-59.org
- ns-1568.awsdns-04.co.uk
MX records
- eforward1.registrar-servers.com
- eforward2.registrar-servers.com
- eforward3.registrar-servers.com
- eforward4.registrar-servers.com
- eforward5.registrar-servers.com
SPF policy
- include: spf.efwd.registrar-servers.com
Threat-feed evidence
History
Related pages
Pivot from shosti.org 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: "shosti.org"})-[: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.