Security engines reporting a detection: 15. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy first observed roblox.rw on Oct 7, 2026. Current evidence score: 95/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, OpenPhish, and Phishunt. VirusTotal recorded 15 detections among 92 engines: alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky, Lionic, Netcraft, SOCRadar, Sophos, VIPRE, Webroot on Oct 7, 2026 at 08:04 UTC. OpenPhish and Phishunt listed the hostname in the separate external-blocklist snapshot on Oct 7, 2026 at 06:20 UTC. Additional recorded evidence: AlienVault OTX listed 2 community pulse references (not vendor detections) on Oct 7, 2026 at 08:05 UTC. URLScan captured the page on Oct 7, 2026 at 08:09 UTC.
The collector marked the hostname reachable on Oct 7, 2026 at 08:09 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause stale current evidence on Oct 7, 2026 at 06:07 UTC. Registration records for the domain list Inzozi Solution Limited as the registrar and Oct 2, 2026 as the creation date. Registration preceded first observation by 4 days. At collection time, the hostname resolved to 179.43.182.61 on AS51852 (PLI-AS Private Layer INC, PA). The stored server header is nginx. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.
The record contains 3 positive source findings supporting the current phishing classification.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Google PageSpeed Insights — mobile performance audit of roblox.rw· checked Oct 7, 2026
38
Poor
Performance
FCP
5.29s
First Contentful Paint
LCP
5.59s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
1323ms
Total Blocking Time
SI
7.43s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-07 08:04:20 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 179.43.182.61.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · roblox.rw
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Inzozi Solution1
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
