Notification and current-status evidence
The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
dcnn[.]ru
“ГБУЗ НО Клинический диагностический центр”
证据摘要
This domain, dcnn.ru, is classified under an elevated risk level for generic credential phishing activity. Analysis indicates the infrastructure was designed to harvest user credentials, likely targeting Russian-speaking audiences or entities interacting with .ru domains. The domain’s longevity and specific targeting suggest it may have been repurposed for malicious campaigns after an extended period of benign use. Infrastructure analysis reveals the following technical indicators: dcnn.ru was flagged by 1 out of 95 security vendors on VirusTotal, indicating limited but present detection. The domain was registered on February 16, 2004, through RU-CENTER-RU, a registrar commonly associated with Russian domain registrations. It resolves to the IP address 95.79.46.168, which may host additional malicious or compromised resources. The domain’s SSL certificate is issued by Let’s Encrypt, a common choice for both legitimate and phishing sites due to its accessibility. It appears on one security blocklist, and its current status is offline, though this does not eliminate residual risk from cached or archived copies. Mitigation against generic credential phishing threats like dcnn.ru requires a multi-layered approach. Organizations should implement domain-based blocking at the network level, ensuring all resolutions to 95.79.46.168 are monitored or restricted. Users should be trained to recognize phishing indicators, such as unexpected login prompts or mismatched URLs, particularly in emails or messages referencing .ru domains. Security teams should also verify SSL certificates manually, as Let’s Encrypt certificates are frequently abused in phishing campaigns. Given the domain’s age, historical DNS records should be reviewed to identify any prior malicious associations or patterns of abuse.
已提交证据快照
- 已发送
- 台账记录
- 1
- 案件 ID
PD-20260611-3E575E- 已捕获页面标题
- ГБУЗ НО Клинический диагностический центр
- PDF 文件
- PDF 证据
法律依据
完整证据文本
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Data Coverage
威胁响应 Pipeline
阻止列表覆盖
监控中的外部数据源 10 个 · 已存快照 2026年8月10日
社区报告
由 1 名社区成员报告;首次发现于 2026年6月11日
- 已存储报告
- 1
- 已报告的唯一 URL
- 1
社区情报
1 条社区报告
类别IMPERSONATION
Brand abuse: impersonation, phishing, impersonating MeritKing
技术
识别出 10 项高置信度技术
VirusTotal 分析
网站性能分析
Google PageSpeed Insights — mobile performance audit of dcnn.ru · checked Jun 25, 2026
您是否受到本网站的影响?
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
检查任意域名
使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析
立即扫描举报网络钓鱼
将可疑域名提交至我们的威胁数据库——保护社区
报告实时威胁动态
最近的网络钓鱼报告和观察到的可用性变化
监控