VirusTotal
8 / 89 engine detections
レポートを開く“robinhoodsmax.com/”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@registrar.eu.
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.
Robinhoodなりすまし: robinhoodsmax.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 8/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 89 engine detections
レポートを開くDBL_PHISH
checked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
robinhoodsmax.com is an impersonation phishing page that borrows the Robinhood name to lure the platform's stock and crypto customers. The "max" suffix suggests a souped-up or premium version of the real service, a common hook in brokerage lookalikes. PhishDestroy first flagged it on 2026-09-15. When last checked on 2026-10-19 the site was still online and serving its content.
Robinhood impersonation pages imitate the brand's login and account screens so that visitors type in their real email, password and often a one-time 2FA code. That lets the operators sign in to the genuine account, move cash or crypto out, and change contact details to lock the owner out. The page title shows only the bare domain rather than any Robinhood branding. We classified the site from its use of the Robinhood name and the independent listings below.
Eight of 89 VirusTotal engines flagged the domain as of 2026-09-24: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar, VIPRE and Webroot. That count is modest, but the verdicts come from unrelated vendors. Spamhaus lists the domain in its DBL as phishing. MetaMask and SEAL block it alongside PhishDestroy, which shows the crypto security community has seen it as a threat. Four AlienVault OTX threat pulses also reference it.
The domain was registered on 2026-04-28 through Hosting Concepts B.V. (Registrar.eu), roughly four and a half months before we detected it. That gap suggests it was registered in advance and activated later. The site sits behind Cloudflare, with the address geolocating to Canada, so the true origin server is not visible. Its Let's Encrypt certificate gives it a browser padlock, which proves nothing about legitimacy.
If you entered credentials here, change your Robinhood password immediately from the official app. Reset your two-factor authentication and review recent logins, transfers, linked bank accounts and crypto withdrawals. Contact Robinhood support through the app to report the compromise and ask for a hold on suspicious activity. Change the password anywhere else you reused it. Security teams should block the domain at DNS and proxy level and alert users to brokerage lookalikes using suffixes like "max".
Last checked
Edge-IP の評判はこのドメインに起因しません。
fonzie.ns.cloudflare.comnola.ns.cloudflare.comLocation describes the IP network.
2384b84a63abb3825a602109bab1e83fc42371df30fec4eeb02f54dadb319e32Saved 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 robinhoodsmax.com · checked Sep 15, 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.
robinhoodsmax.com
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
不明→live_content
content_served
5→8
到達可能
4 community references
View sourceNo threat flag
View source8/89 engine detections
View sourcePD-20260915-C194C6
robinhoodsmax.com
View sourcePage captured
View sourcePD-20260915-C194C6 Recipient: abuse@registrar.eu アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
robinhoodsmax.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.