Skip to content

Hostname

esw.et

Last fetched

esw.et resolves to 196.188.93.253, announced in 196.188.64.0/19 by Ethio Telecom - Ethio Telecom in ET. esw.et is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · esw.etRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/esw.et

Resolution chain

IPv6 resolution

No AAAA record for esw.et is recorded in WhisperGraph.

Attribution

ethio

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for esw.et. 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

Subdomain
aibcms.esw.et
aiblms.esw.et
auth-cms.esw.et
cms-api.esw.et
cms-storage.esw.et
ns.esw.et
smtp.esw.et
taibcms.esw.et
taiblms.esw.et
tauth-cms.esw.et
tcms-api.esw.et
tcms-storage.esw.et

Showing 12 of 33. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns.esw.et
  • ns1.telecom.net.et
  • ns2.telecom.net.et
  • 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

  • mail1.ethionet.et
  • mail2.ethionet.et
  • mail3.ethionet.et
  • mail4.ethionet.et

SPF policy

  • ip: 196.189.189.1
  • ip: 196.189.189.2
  • ip: 196.189.93.65
  • ip: 196.189.93.66

Threat-feed evidence

History

Related pages

Pivot from esw.et 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: "esw.et"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.