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.
How the scam works
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.
Evidence
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.
Infrastructure
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.
What to do
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.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
