Hostname
rt-dc.ru
Last fetched
rt-dc.ru resolves to 195.209.66.193, announced in 195.209.66.0/24 by CCT-AS - OOO "Sovremennye setevye tekhnologii" in RU. rt-dc.ru 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
- 195.209.66.193
195.209.66.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 195.209.66.128
195.209.66.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 195.209.66.106
195.209.66.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 46.235.184.80
46.235.184.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 195.209.67.81
195.209.67.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 195.209.82.115
195.209.82.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 37.220.163.31
37.220.163.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.157.187
212.193.157.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii"
IPv6 resolution
No AAAA record for rt-dc.ru is recorded in WhisperGraph.
Attribution
ooo sovremennye setevye tekhnologii
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:ru-center-ru
- Registrant organisation
- safedata jsc
Subdomains
| Subdomain |
|---|
| cloud.rt-dc.ru |
| mxfront01.rt-dc.ru |
Showing 2 of 8. View all subdomains →
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.ngenix-dns.net
- ns2.ngenix-dns.net
MX records
- mxfront01.rt-dc.ru
Threat-feed evidence
History
Related pages
Pivot from rt-dc.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: "rt-dc.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.