VirusTotal
11 / 91 engine detections
レポートを開く“risex.exchange”
フィッシング: risex.exchange — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker); 3…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 91 engine detections
レポートを開く17 community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Risex.exchange, a domain posing as a legitimate exchange, is flagged by 7 out of 91 VirusTotal vendors as malicious. The domain is now offline, but it previously operated as a fake exchange scam. It was hosted on an IP managed by Cloudflare, Inc., located in the United States. The domain was created on June 4, 2026, and PhishDestroy identified it as a threat by June 19, 2026.
The domain was blocklisted by four entities, including PhishDestroy, MetaMask, ScamSniffer, and SEAL. This indicates a coordinated effort to mitigate the threat posed by this fraudulent operation. The platform risk score of 75 out of 100 underscores the significant risk it posed during its active period.
Despite its relatively short lifespan, risex.exchange managed to deceive users by masquerading as a legitimate exchange platform. The use of a trusted SSL issuer, Google Trust Services, may have lent an air of legitimacy to unsuspecting victims. However, the swift action by security entities and its inclusion on multiple blocklists helped curb its impact. The case of risex.exchange highlights the importance of early detection and rapid response in combating online scams.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
bowen.ns.cloudflare.comlaila.ns.cloudflare.comLocation describes the IP network.
6b33f87126bc13d34fddd117401bf3097768f96dad9f5e62ce5744beefd7e14fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
risex.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
不明→protected
cloudflare_challenge · Cloudflare · challenge
No threat flag
View source17 community references
View source11/91 engine detections
View sourcePage captured
View sourcerisex.exchange
View sourceListed 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 ↗
risex.exchange)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.