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; 5 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.
rover[.]mq
“RoVer”
证据摘要
The domain rover.mq was registered on March 06, 2026 via a Gmail‑based registration process. The site presents a page titled “RoVer” and serves over HTTPS using a Let's Encrypt certificate (identifier E8). An HTTP 301 redirect is observed, suggesting the original request is forwarded to the same or a related host. Network resolution points to IP address 151.247.193.142, which belongs to AS399486 (12651980 CANADA INC.) and is geolocated to France. The authoritative nameservers are ns1.eggywall.cc and ns2.eggywall.cc. Fingerprinting of the web server indicates Nginx as the HTTP engine and React as the front‑end framework. Reputation services flag the domain as high‑risk. Ten out of ninety‑five security vendors on VirusTotal have raised detections, and the domain appears on a single public blocklist. Gridinsoft assigns a trust score of 0 out of 100, and PhishDestroy has already blocked the host. The risk level is classified as high and the domain remains active at the time of analysis. Open‑source intelligence does not yet reveal the exact phishing payload or the credential‑stealing page that may be delivered behind the “RoVer” title. The presence of a generic page title and the use of common web technologies limit attribution to a specific campaign, and the short lifespan of the domain leaves limited historical context. Defenders should add rover.mq to outbound filtering rules and ensure that DNS resolvers return NXDOMAIN or sinkhole responses for the domain. Continuous monitoring of the associated IP address and its ASN is advised, as well as periodic re‑scans with malware analysis platforms to detect any evolving payloads. Incident response teams should treat any user interaction with rover.mq as compromised and initiate credential reset procedures.
已提交证据快照
- 已发送
- 台账记录
- 1
- 案件 ID
PD-20260306-72A5DF- 已捕获页面标题
- RoVer
- 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
网络安全情报
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | roblox.com.py |
malicious | Sinkholed |
| DNS4EU | roblox.com.py |
malicious | Sinkholed |
| Hagezi Threat Feed | roblox.com.py |
malicious | Sinkholed |
| OpenDNS | roblox.com.py |
phishing | Phishing Block |
| Quad9 DNS | roblox.com.py |
malicious | Sinkholed |
| OpenDNS | roblox.gs |
phishing | Phishing Block |
| Hagezi Threat Feed | roblox.gs |
malicious | Sinkholed |
| DNS4EU | roblox.gs |
malicious | Sinkholed |
| Hagezi Threat Feed | rover.mq |
malicious | Sinkholed |
| DNS4EU | rover.mq |
malicious | Sinkholed |
| Hagezi Threat Feed | captchabot.fun |
malicious | Sinkholed |
| DNS4EU | captchabot.fun |
malicious | Sinkholed |
威胁响应 Pipeline
阻止列表覆盖
监控中的外部数据源 10 个 · 已存快照 2026年8月12日
检测时间线
-
VirusTotal
0 → 11
-
Cloudflare Radar
已存储 Cloudflare Radar 扫描 · 打开扫描
-
域名状态
可访问 → 无法访问
-
域名状态
无法访问 → 可访问
-
域名状态
可访问 → 无法访问
VirusTotal 分析
您是否受到本网站的影响?
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
检查任意域名
使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析
立即扫描举报网络钓鱼
将可疑域名提交至我们的威胁数据库——保护社区
报告实时威胁动态
最近的网络钓鱼报告和观察到的可用性变化
监控