Skip to content

Hostname

rtk-cd.ru

Last fetched

rtk-cd.ru resolves to 91.189.114.17, announced in 91.189.114.0/23 by RU-CENTER - JSC "RU-CENTER" in RU. rtk-cd.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 · rtk-cd.ruRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/rtk-cd.ru

Resolution chain

IPv6 resolution

No AAAA record for rtk-cd.ru is recorded in WhisperGraph.

Attribution

jsc ru center

ORIGIN_AS

WHOIS identity

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

Mail and authentication

Nameservers

  • ns3-l2.nic.ru
  • ns4-cloud.nic.ru
  • ns4-l2.nic.ru
  • ns8-cloud.nic.ru
  • ns8-l2.nic.ru

MX records

  • post.rtk-cd.ru

Threat-feed evidence

History

Related pages

Pivot from rtk-cd.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: "rtk-cd.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.