VirusTotal
18 / 91 engine detections
打开报告“404: NOT_FOUND”
冒充 Facebook: facebook-case-business.com — 最后已知的活跃状态 (HTTP 308). 证据摘要: VirusTotal 18/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); Google Safe…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
18 / 91 engine detections
打开报告恶意
打开报告Threat flag recorded
打开报告DBL_PHISH
4 community references
打开报告80/100
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
facebook-case-business.com is a phishing domain that impersonates Facebook. Its name targets business page owners and advertisers by suggesting an official "case" or support process. PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still online and its content returned a redirect rather than a page of its own.
Domains built like this usually support a familiar Facebook lure. The victim gets a message claiming their page or ad account has a policy violation, copyright complaint or pending case, and is told to file an appeal before the account is disabled. The appeal form asks for the Facebook login, password and often the two-factor code, which hands the attacker control of the account, its pages and any linked ad spend. When we checked, the page title read "404: NOT_FOUND", while our classification is Facebook impersonation phishing.
On 2026-09-25, 18 of 91 VirusTotal engines flagged the domain as malicious. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF and CyRadar. Agreement across that many separate vendors is strong support for the phishing verdict. Google Safe Browsing lists the domain under SOCIAL_ENGINEERING, and Spamhaus DBL classifies it as DBL_PHISH. It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-09-15 through Cloudflare, Inc., only two days before PhishDestroy detected it. That short gap fits a campaign domain created for immediate use. It resolves to 216.198.79.65 on Amazon.com, Inc. infrastructure in the US. Its Let's Encrypt certificate means the browser padlock appears, so the padlock alone does not show the site is genuine.
If you entered your Facebook credentials on this site, change your password right away from the official app or site. Log out of all other sessions, and reset two-factor authentication if you typed in a code. Under Facebook's security settings, check Business Manager admins, page roles, linked emails and ad payment methods for anything you did not add. Facebook does not open policy cases on outside domains, so treat any message pointing you elsewhere as phishing. Defenders should block the domain at DNS and the mail gateway, search mail logs for messages linking to it, and reset credentials for any staff who clicked.
Edge-IP 声誉不属于此域。
hasslo.ns.cloudflare.comLocation describes the IP network.
db64e89401d8c662fe58d66a4bbeb1ea39edc54860fa8be548a3ccadf67f9a08Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
可访问→不可用
未知→redirected
http_redirect
protected→redirected
http_redirect
未知→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
可访问→不可用
未知→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
protected→redirected
http_redirect
未知→protected
http_access_restricted · access_restriction
redirected→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
17→18
https://radar.cloudflare.com/scan/a2941dea-4ebb-4e11-bcec-ba453d34c25b
可访问→不可用
No flag recorded→Flag recorded
可访问
4 community references
View sourceThreat flag recorded
View source18/91 engine detections
View sourcefacebook-case-business.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
facebook-case-business.com
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 ↗
facebook-case-business.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
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.