mquetzporclics.ru
Evidence Summary
PhishDestroy first observed mquetzporclics.ru on Sep 13, 2026. Stored content metadata identifies ["telegram"] as the apparent target. Page analysis recorded additional brand references to Telegram. Stored page analysis classifies the content as impersonation. Current evidence score: 100/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Cloudflare Radar. VirusTotal recorded 14 detections among 89 engines: alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Sep 21, 2026 at 02:08 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. Non-positive and contextual checks: AlienVault OTX listed 1 community pulse reference (not vendor detections) on Sep 13, 2026 at 18:55 UTC. The separate external-blocklist snapshot contained no matches on Sep 21, 2026 at 02:20 UTC. Google Safe Browsing returned no flag on Sep 19, 2026 at 22:01 UTC. URLScan completed without a malicious verdict (score 0) on Sep 14, 2026 at 03:30 UTC.
HTTP 200 was recorded on Sep 21, 2026 at 01:53 UTC. The recorded creation date for the domain is Apr 6, 2026. At collection time, the hostname resolved to 31.31.196.17 on AS197695 (Domain names registrar REG.RU, Ltd). The recorded endpoint location is Moscow, RU. The stored server header is nginx. DOM analysis on Sep 13, 2026 at 22:20 UTC returned 93/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists GlobalSign nv-sa / GlobalSign GCC R6 AlphaSSL CA 2025 as the certificate issuer with validity through Mar 6, 2027; checked Sep 13, 2026 at 22:02 UTC.
The content indicators and 2 positive source findings support the current ["telegram"]-themed impersonation classification.
Network Security Intelligence
Forensic History & Detection Timeline
-
Threat First Observed Sep 13, 2026 · 20:52 UTCDomain ingestion complete. Initial state is marked as unknown pointing to IP
31.31.196.17.
Threat Response Pipeline
Public Blocklist Status
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
nginx
Scanner note: alive_content: raw=ok; http=200; via=https_direct; server=nginx
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive