Hostname
ebank.com.eg
Last fetched
ebank.com.eg resolves to 213.212.206.193, announced in 213.212.204.0/22 by Vodafone Data - Vodafone Data in EG. ebank.com.eg 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
IPv6 resolution
No AAAA record for ebank.com.eg is recorded in WhisperGraph.
Attribution
vodafone
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ebank.com.eg. 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 |
|---|
| cmdm.ebank.com.eg |
| live.ebank.com.eg |
| mail.ebank.com.eg |
| mail2.ebank.com.eg |
| mail3.ebank.com.eg |
| ns1.ebank.com.eg |
| ns2.ebank.com.eg |
| ns3.ebank.com.eg |
| onlinebanking.ebank.com.eg |
Showing 9 of 9 subdomains (9 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
- ns1.ebank.com.eg
- ns2.ebank.com.eg
- ns3.ebank.com.eg
- 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
- mail.ebank.com.eg
- mail2.ebank.com.eg
- mail3.ebank.com.eg
SPF policy
- ip: 213.212.206.133/32
- ip: 196.219.38.220/32
- ip: 41.33.38.227/32
- mx: ebank.com.eg
- a: mail.ebank.com.eg
- a: mail2.ebank.com.eg
- a: mail3.ebank.com.eg
Threat-feed evidence
History
Related pages
Pivot from ebank.com.eg 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: "ebank.com.eg"})-[: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.