Hostname
proxy-dag.ru
Last fetched
proxy-dag.ru resolves to 212.233.75.84, announced in 212.233.72.0/21 by VK-AS - LLC VK in RU. proxy-dag.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
- 212.233.75.84
212.233.72.0/21 · VK-AS - LLC VK · Moscow, RU
- 212.233.76.138
212.233.72.0/21 · VK-AS - LLC VK · Moscow, RU
- 212.233.73.165
212.233.72.0/21 · VK-AS - LLC VK · Moscow, RU
- 212.233.121.145
212.233.120.0/22 · VK-AS - LLC VK · Moscow, RU
- 89.208.197.20
89.208.196.0/22 · VK-AS - LLC VK · Moscow, RU
- 89.208.198.103
89.208.196.0/22 · VK-AS - LLC VK · Moscow, RU
- 161.104.106.181
161.104.104.0/21 · VK-AS - LLC VK · Paris, FR
- 161.104.106.197
161.104.104.0/21 · VK-AS - LLC VK · Paris, FR
- 161.104.106.203
161.104.104.0/21 · VK-AS - LLC VK · Paris, FR
- 161.104.106.206
161.104.104.0/21 · VK-AS - LLC VK · Paris, FR
- 212.111.86.73
212.111.84.0/22 · VK-AS - LLC VK · Moscow, RU
- 212.111.85.221
212.111.84.0/22 · VK-AS - LLC VK · Moscow, RU
- 212.111.85.217
212.111.84.0/22 · VK-AS - LLC VK · Moscow, RU
- 95.163.214.122
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
- 83.166.239.21
83.166.232.0/21 · VK-AS - LLC VK · Moscow, RU
- 95.163.214.137
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
- 95.163.214.110
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
- 95.163.214.114
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
- 95.163.213.196
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
- 95.163.212.95
95.163.208.0/21 · VK-AS - LLC VK · Moscow, RU
IPv6 resolution
No AAAA record for proxy-dag.ru is recorded in WhisperGraph.
WHOIS identity
- Registrar
- registrar:ru-center-ru
- Registrant organisation
- private person
Mail and authentication
Nameservers
- pns62.cloudns.com
- pns61.cloudns.net
- pns63.cloudns.net
- pns64.cloudns.uk
Threat-feed evidence
History
Related pages
Pivot from proxy-dag.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: "proxy-dag.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.