VirusTotal
11 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: renegex.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開く悪意あり
レポートを開く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
renegex.com is an impersonation phishing page that borrows Cloudflare's branding to win the trust of crypto users. PhishDestroy first caught it on 2026-09-05. The site went offline on 2026-09-11 after its provider blocked the content, and it was still dead when rechecked on 2026-10-19. Its page title reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning wording, while our classification is impersonation of the Cloudflare brand.
Cloudflare's security checks are familiar to almost everyone online, so a fake "verify you are human" or protection screen rarely raises suspicion. Scams of this kind use that trust to push visitors into the next step. That might mean connecting a wallet, entering login details, or following instructions that hand over control of an account or device. urlscan.io matched the page to generic crypto and crypto-scam patterns, so the likely losses are wallet funds and crypto account access rather than an ordinary website login.
Eleven of 89 VirusTotal engines flagged the domain as of 2026-09-14. They include BitDefender, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a modest share of engines, but it comes from established vendors working independently. urlscan.io returned a malicious verdict. MetaMask and SEAL, two blocklists aimed specifically at crypto threats, list the domain alongside PhishDestroy. Four AlienVault OTX threat pulses also reference it, so other researchers have tracked it too.
The domain was registered on 2026-05-20 through Fewmoretaps OU (Trustname.com). It sat for about three and a half months before it surfaced as a phishing page. Traffic ran through Cloudflare's own network, on an address that geolocates to Canada, so the site impersonated the same company whose infrastructure carried it. Its TLS certificate came from Let's Encrypt, and the padlock it displayed proved nothing about who ran the site.
If you connected a wallet on renegex.com, revoke any token approvals granted around that time. Move remaining assets to a fresh wallet if you signed anything you did not understand. If you typed in a seed phrase, treat that wallet as fully compromised and empty it immediately. If a fake verification step had you paste or run a command on your computer, disconnect it, scan it, and change passwords and 2FA from a clean device. Defenders should block the domain and check logs for visits since 2026-09-05.
Last checked
Edge-IP の評判はこのドメインに起因しません。
brenna.ns.cloudflare.comotto.ns.cloudflare.comLocation describes the IP network.
3e16b2882b485b9fcf3f32e7c03a1df419789fcb4cbf1ee4db1e9f4db1b32b37Saved 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 renegex.com · 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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
利用不可→到達可能
到達可能→利用不可
到達可能
No threat flag
View source11/89 engine detections
View source4 community references
View sourcerenegex.com
View sourcePage captured
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
renegex.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
renegex.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.