Hostname
eda.yandex
Last fetched
eda.yandex resolves to 87.250.251.213, announced in 87.250.224.0/19 by TELETECH - Edge Technology Plus d.o.o. Beograd in RU. eda.yandex 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
Attribution
edge plus beograd
ORIGIN_AS
WHOIS identity
- Registrar
- iana:447
Subdomains
| Subdomain |
|---|
| adjust-provider.eda.yandex |
| courier.eda.yandex |
| openkitchen.eda.yandex |
| reg.eda.yandex |
| sup.eda.yandex |
| ultima.eda.yandex |
| vendor.eda.yandex |
| www.eda.yandex |
Showing 8 of 8 subdomains (8 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.
Sample inbound links
Mail and authentication
Nameservers
- ns3.yandex.ru
- ns4.yandex.ru
MX records
- mx.yandex.net
SPF policy
- ip: 82.202.245.24/29
- ip: 95.213.157.80/29
- include: mxsmtp.sendpulse.com
- include: _spf.yandex.net
- redirect: _spf.yandex.net
- include: spf.mindbox.ru
- a: eda.yandex
- mx: eda.yandex
- ip: 5.178.85.58
Threat-feed evidence
History
Related pages
Pivot from eda.yandex 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: "eda.yandex"})-[: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.