Skip to content
Install MCP

Hostname

59i.ru

Last fetched

59i.ru resolves to 62.109.11.66, announced in 62.109.8.0/21 by RU-JSCIOT - JSC IOT in RU. 59i.ru 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 · 59i.ruRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/59i.ru

Resolution chain

IPv6 resolution

No AAAA record for 59i.ru is recorded in WhisperGraph.

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

Registrar
registrar:regtime-ru
Registrant organisation
private person

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

Sample outbound links

Mail and authentication

Nameservers

  • dns1.yandex.net
  • dns2.yandex.net

MX records

  • mx.yandex.net

Threat-feed evidence

History

Related pages

Pivot from 59i.ru 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: "59i.ru"})-[: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.