VirusTotal
0 / 89 engine detections
打开报告“Suspected Phishing | Cloudflare”
冒充 Cloudflare: lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 0/89; PhishDestroy score 68/100. 注册商: Cloudflare…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
0 / 89 engine detections
打开报告no community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This Cloudflare Workers subdomain is an impersonation phishing page built to pass as Cloudflare. It targets people who manage websites, DNS or domains through a Cloudflare account. PhishDestroy first flagged it on 2026-09-10. The site has been dead since 2026-09-19 with its content blocked by the hosting provider, and it was still offline at the last check on 2026-10-19.
Cloudflare-branded phishing usually poses as a login prompt, security alert or verification step, and whatever the victim types goes straight to the operator. A stolen Cloudflare account is valuable because it controls DNS, SSL and traffic routing for every site behind it. With that access an attacker can redirect visitors, inject malicious scripts or hijack email records. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial rather than a lure, while we classified the page as Cloudflare impersonation.
Independent detection was close to nonexistent. VirusTotal returned 0 detections from 89 engines on 2026-09-20, one day after the site went offline, so scanners had little live content left to judge. PhishDestroy is the only blocklist listing it. The provider's block, visible in the current page title, separately shows that the content was treated as phishing.
The operation ran entirely on Cloudflare Workers under a disposable account subdomain with a random-looking prefix. It resolved to 172.67.204.84 on Cloudflare, Inc.'s network, geolocated to Canada, with a certificate from Google Trust Services. Hosting a fake Cloudflare page on Cloudflare's own platform gave it a plausible address and a valid padlock. It also put the page within reach of the provider, which shut it down nine days after our first sighting.
If you entered credentials here, change your Cloudflare password right away and turn on or reset two-factor authentication. Revoke any API tokens and keys you cannot account for. Then review the audit log, DNS records, Page Rules, Workers and account members for changes you did not make. Change that password anywhere else you reused it. Defenders should block this domain along with its parent Workers account subdomain, and alert on Cloudflare-themed login pages served from free serverless hosting.
Edge-IP 声誉不属于此域。
Location describes the IP network.
101f018acbba55c7d2096990a13e77445db068a476ad6aa59b8aaaae12133074eugeniebenoits397.workers.devSaved 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 lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev · checked Sep 18, 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.
lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
可访问→不可用
可访问
No threat flag
View source0/89 engine detections
View sourcelispy-rivedfdsr-787c.eugeniebenoits397.workers.dev
View source已存储 142 个仿冒域名
显示 142 个中的 100 个
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 ↗
lispy-rivedfdsr-787c.eugeniebenoits397.workers.dev)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.