VirusTotal
11 / 91 engine detections
보고서 열기“risex.exchange”
risex.exchange — 연결 가능 · 액세스가 제한됨 (HTTP 403). 사기 유형: Fake Exchange. 증거 요약: VirusTotal 11/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker); 3 external blocklist matches (MetaMask, ScamSniffer, SEAL); PhishDestroy score 100/100. 등록기관: Global Domain Group.
원본 포렌식 기록을 보존하기 위해 아래의 상세 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.
AI-assisted evidence review
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
17 community references
View source11/91 engine detections
View sourcePage captured
View sourceNo threat flag
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
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.