VirusTotal
13 / 89 engine detections
レポートを開くフィッシング: ajbells.netlify.app — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); CF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ajbells.netlify.app is a site built on Netlify's free hosting platform and listed on the PhishDestroy blocklist. PhishDestroy first saw it on 2026-08-09. It went offline on 2026-09-12, and a check on 2026-10-19 found the address still dead, with nothing served at its root. Whatever it once displayed has been removed, but the name stays blocked in case it is redeployed.
This domain has no confirmed scheme type, and no impersonated brand or phishing kit has been identified. The risk comes from what security vendors saw: thirteen engines rated the site malicious. That pattern usually means a page that collects logins, personal details or wallet credentials, or one that sends visitors to such a page. Free subdomains like this are cheap to create and easy to abandon, which makes them a common choice for short-lived fraud pages.
VirusTotal recorded 13 detections out of 89 engines on 2026-09-13, one day after the site went offline. The flagging vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai and CyRadar. When several unrelated vendors flag the same address, it is unlikely to be a one-off false positive. Among the blocklists tracked here, only PhishDestroy lists it.
The site sits on a netlify.app subdomain, so Netlify controls the parent domain and anyone can create a name like this in minutes without registering a domain. The hosting traces to an Amazon network in Germany, which reflects the cloud infrastructure behind the platform rather than the operator's location. It stayed online only about five weeks after PhishDestroy first saw it, which fits a throwaway deployment.
If you visited this site and typed in a password, change it right away on the real service and on any account that shares it, and turn on two-factor authentication. If you entered card or banking details, contact your bank to block the card and watch for unfamiliar charges. If you shared a wallet seed phrase, treat that wallet as compromised and move your funds to a new one. Defenders should block the full subdomain, search proxy and email logs for visits between 2026-08-09 and 2026-09-12, and report any reappearance to Netlify.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ajbells.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
到達可能→利用不可
No threat flag
View source13/89 engine detections
View sourceajbells.netlify.app
View sourceコミュニティ報告:1 件
カテゴリPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-07-29T08:06:18.608Z.
Listed 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 ↗
ajbells.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.