VirusTotal
3 / 89 engine detections
レポートを開くブロックリスト掲載ドメイン: crypto-q5t.netlify.app — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 3/89 (alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 89 engine detections
レポートを開くno 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
crypto-q5t.netlify.app is an impersonation phishing page that posed as a legitimate crypto service to win the trust of wallet holders. PhishDestroy first flagged it on 2026-09-08, and it went offline three days later, on 2026-09-11. As of 2026-10-19 the address is dead and serves no content at its root. The throwaway name, a generic "crypto" label plus a random suffix on a free hosting subdomain, fits a short-lived campaign rather than any real project.
Impersonation pages copy the look of a familiar crypto brand or wallet interface and then ask the visitor to "verify", "connect" or "restore" something. Depending on the variant, that means typing a seed phrase or private key into a form, or approving a wallet connection and signature that hands spending rights to the attacker. Either way, the victim loses control of the funds in the affected wallet, usually within minutes and with no way to reverse the transfers.
The strongest confirmation comes from the crypto ecosystem itself. The domain sits on MetaMask's phishing blocklist and on SEAL's list as well as PhishDestroy's, so many wallet users would have seen a warning before the page loaded. Generic antivirus coverage was thin: when VirusTotal checked the domain on 2026-09-16, only 3 of 89 engines flagged it, namely alphaMountain.ai, Forcepoint ThreatSeeker and VIPRE. A clean result from most scanners therefore said little about this site's safety.
The page lived on a Netlify subdomain, which anyone can create in seconds without buying a domain. That makes it cheap to launch and easy to abandon, which matches the three-day lifespan. It resolved to Amazon infrastructure in Germany. Its DigiCert certificate is the platform's standard one, so the padlock in the browser said nothing about who ran the page.
If you typed a seed phrase or private key into this page, treat that wallet as compromised and move any remaining assets to a newly created wallet right away. If you connected a wallet or signed anything, review and revoke token approvals with a trusted approval-checking tool, and watch for unexpected outgoing transactions. Do not answer anyone who offers to "recover" lost funds, because recovery offers are a common follow-up scam. Defenders should block the hostname, look for it in proxy and DNS logs from around 2026-09-08 to 2026-09-11, and report any new lookalike Netlify subdomains to the platform's abuse team.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 crypto-q5t.netlify.app · checked Sep 8, 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.
crypto-q5t.netlify.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能→利用不可
0→3
到達可能
No threat flag
View source3/89 engine detections
View sourcecrypto-q5t.netlify.app
View sourcePage captured
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 ↗
crypto-q5t.netlify.app)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.