VirusTotal
5 / 92 engine detections
レポートを開く“Roblocl Hub”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@identitydigital.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Robloxなりすまし: roblocl.pro — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
roblocl.pro is a phishing site that imitates Roblox under the page title Roblocl Hub. The domain is a typo-style lookalike of the real brand name, swapping a few letters so it reads as Roblox at a glance. It targets Roblox players and the parents whose accounts and payment details sit behind them. PhishDestroy first flagged it on 2026-09-05, and it was still online and serving content on 2026-10-19.
Pages styled as a Roblox hub usually draw players in with offers such as free Robux, rare items or account tools, then ask them to log in to claim the reward. Whatever the visitor types, including username, password and sometimes a 2FA code, goes to the operators rather than to Roblox. With those credentials they can take over the account, strip its inventory and Robux, and reuse the password wherever it was recycled.
urlscan.io rates the page malicious and recognizes the Roblox branding on it. On VirusTotal, 5 of 92 engines flag the domain as of 2026-10-19: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That count is low, so most browsers and security tools will not warn visitors yet. The domain also appears in 4 AlienVault OTX threat pulses, which shows other researchers have tracked it independently.
The domain was registered on 2026-08-11 through Fewmoretaps OU d/b/a Trustname.com, and it was in use as a phishing page within 25 days. That short gap is typical of throwaway lookalike domains. The site sits behind Cloudflare, Inc., with the address geolocated to Canada, so the real origin server is hidden. Its HTTPS certificate comes from Google Trust Services (WE1). The padlock only means the connection is encrypted and says nothing about whether the site is genuine.
If you entered Roblox login details on this page, change your Roblox password right away from the official app or site. Turn on or reset 2-Step Verification, and sign out of all other sessions. Change the same password anywhere else you used it, and check your account for missing items, Robux or new trade and purchase activity. If a payment method is linked, review recent charges and contact Roblox support about any you did not make. Security teams and parents should block roblocl.pro at the DNS or proxy level and report it to Roblox and Cloudflare's abuse channel.
Edge-IP の評判はこのドメインに起因しません。
josephine.ns.cloudflare.comtim.ns.cloudflare.comLocation describes the IP network.
521670ad50fa210a4ad5143447cc422d5dc8c919ad1b02f0487cbff08b291ccdSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of roblocl.pro · checked Sep 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
roblocl.pro
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
3→4
0→3
2→Observation retained
到達可能
5/92 engine detections
View source4 community references
View sourceNo threat flag
View sourcePD-20260905-6D3E63
roblocl.pro
View sourcePage captured
View sourcePD-20260905-6D3E63 Recipient: abuse@identitydigital.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
roblocl.pro)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.