VirusTotal
14 / 91 engine detections
レポートを開く“Richmondzux | a premium AI trading | Authorized Platform”
フィッシング: richmondzux.shop — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 91 engine detections
レポートを開く悪意あり
レポートを開く4 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
richmondzux.shop presents itself as a legitimate cryptocurrency exchange under the brand name Richmondzux, marketing itself as a premium AI-powered trading platform. It targets retail crypto investors and traders looking for automated or AI-assisted trading services. PhishDestroy first identified this site on 2026-09-18, and as of 2026-10-19 the site remains fully live and serving content.
Fake exchange platforms like this one lure victims by offering the appearance of a professional, authorized trading environment — in this case reinforced by the page title 'Richmondzux | a premium AI trading | Authorized Platform.' Users are typically prompted to create an account, deposit cryptocurrency or fiat funds, and watch fabricated balance displays that show artificial gains. When victims attempt to withdraw, they are blocked, charged invented fees, or simply cut off entirely, losing everything they deposited.
Fourteen of 91 engines on VirusTotal flagged richmondzux.shop as malicious as of 2026-09-29, with detections from BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF, and alphaMountain.ai. Four threat intelligence pulses on OTX independently corroborate the classification. The domain is listed on the PhishDestroy blocklist.
The domain was registered on 2026-08-02 through Dynadot Inc. and appeared in threat feeds less than seven weeks later, a pattern consistent with short-lifecycle fraud infrastructure. The site is hosted on Cloudflare's network with a Canadian-geolocated IP and uses a TLS certificate issued by Google Trust Services under the WE1 intermediate.
If you visited the site but did not register or deposit funds, no immediate action is required beyond avoiding any further interaction. If you created an account or transferred any cryptocurrency or payment details to this platform, treat those funds as unrecoverable and report the incident to your national cybercrime authority and your payment provider or exchange immediately. Do not respond to any follow-up contact from operators claiming to facilitate withdrawals, as these are typically secondary recovery scams. Security teams should block richmondzux.shop at the DNS and proxy layer and add the associated Cloudflare IP to monitoring watchlists.
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 の評判はこのドメインに起因しません。
curt.ns.cloudflare.comLocation describes the IP network.
fc04ca864040a803e5d766a72674279ea80f8374a4757a9a097ab2c554f4365aSaved 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 richmondzux.shop · checked Sep 18, 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.
richmondzux.shop
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
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
4 community references
View sourceNo threat flag
View source14/91 engine detections
View sourcePage captured
View sourcerichmondzux.shop
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 ↗
richmondzux.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.