Skip to content

Hostname

rtcomm.ru

Last fetched

rtcomm.ru resolves to 195.161.13.245, announced in 195.161.0.0/16 by RTCOMM-AS - JSC RTComm.RU in RU. rtcomm.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 · rtcomm.ruRouting diversity1.5/10Peering density4.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.0/10canon.whisper.security/host/rtcomm.ru

Resolution chain

IPv6 resolution

No AAAA record for rtcomm.ru is recorded in WhisperGraph.

Attribution

jsc rtcomm ru

ORIGIN_AS

WHOIS identity

Registrar
registrar:ru-center-ru
Registrant organisation
rtcomm.ru jsc

Subdomains

Showing 1 of 1 subdomain (1 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

  • ns01.rtcomm.ru
  • ns02.rtcomm.ru
  • ns03.rtcomm.ru

MX records

  • mx1.atmosphere.facct.ru
  • mx2.atmosphere.facct.ru

Threat-feed evidence

History

Related pages

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