VirusTotal
4 / 89 engine detections
レポートを開くブロックリスト掲載ドメイン: crypto-car.netlify.app — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 4/89 (ChainPatrol, alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開く15/100
レポートを開く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-car.netlify.app is an impersonation phishing page on a free Netlify subdomain. It posed as a legitimate crypto service to lure people who hold digital assets. PhishDestroy first logged it on 2026-09-08. It went offline on 2026-09-11, and at the last check on 2026-10-19 it was still dead, with nothing served at its root.
Impersonation pages copy the look and wording of a trusted crypto brand so visitors believe they are on the real service. The goal is to get the visitor to act there. That can mean typing a seed phrase or login details, connecting a wallet and signing a transaction, or sending funds to an address the operator controls. Whatever is handed over goes straight to the scammers, and on-chain transfers or leaked recovery phrases usually cannot be undone. The page lived for only about three days after we found it, which fits the pattern of throwaway pages launched, promoted briefly and then abandoned.
Four of 89 VirusTotal engines flagged the address as of 2026-09-16: ChainPatrol, alphaMountain.ai, Forcepoint ThreatSeeker and VIPRE. That is a low count overall. However, ChainPatrol focuses specifically on crypto threats, and the site also sits on the MetaMask and SEAL blocklists alongside PhishDestroy. Those three wallet-security lists agreeing carries more weight here than the raw engine tally.
The operator did not register a domain. They used a subdomain on Netlify, a free hosting platform that lets anyone publish a site in minutes, which keeps both cost and effort near zero. Traffic resolved to Amazon network infrastructure in Germany, and the HTTPS padlock came from DigiCert. That certificate belongs to the hosting platform, not to the scammer, so the padlock says nothing about whether the page could be trusted.
If you entered a seed phrase or private key on this page, treat that wallet as compromised. Move any remaining assets to a new wallet created on a clean device. If you connected a wallet and signed anything, review your token approvals with a revocation tool and cancel any you do not recognize. If you typed in an exchange or account password, change it and reset two-factor authentication. Security teams should keep the subdomain blocked, because dead Netlify pages can be republished, and should report any revival to Netlify'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-car.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-car.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→4
到達可能
No threat flag
View source4/89 engine detections
View sourcecrypto-car.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-car.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.