VirusTotal
6 / 89 engine detections
打开报告“Suspected Phishing | Cloudflare”
冒充 Cloudflare: sfhryu.com — 内容不可用. 证据摘要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, PhishFort); CF Radar malicious…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 89 engine detections
打开报告恶意
打开报告4 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
sfhryu.com is a meaningless string of letters that served a page dressed up as Cloudflare. It targeted people who manage websites through Cloudflare and visitors used to seeing its security checks. PhishDestroy first flagged it on 2026-09-03. The site went offline on 2026-09-15, and its DNS was still inactive at our latest check on 2026-10-19.
Cloudflare-themed phishing works because its interstitial screens are everywhere. People click through them without thinking, and administrators trust anything that looks like their dashboard. Pages like this usually push the victim to sign in or verify an account. Whatever is typed goes to the operator, who can then take over DNS, API tokens and every site behind that account. The page title read "Suspected Phishing | Cloudflare", the wording of Cloudflare's own warning screen. We nonetheless classified the domain as an impersonation phishing page.
On 2026-09-16, six of 89 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, PhishFort and SOCRadar. That is a low count. Most engines never classified the site before it disappeared, so a clean result from a single scanner would have been misleading. PhishFort, a brand-protection specialist, is among the vendors that caught it. Four AlienVault OTX pulses reference the domain, which shows other researchers tracked it independently. PhishDestroy is the only blocklist carrying it.
The domain was registered through Cloudflare, Inc. and resolved to Cloudflare's network, with the address geolocated to Canada. A scam imitating Cloudflare therefore sat on Cloudflare's own infrastructure, which makes it harder to tell apart from the real thing. Its certificate came from Google Trust Services (WE1), which is routine for sites behind Cloudflare. The padlock proved nothing about legitimacy. The site stayed live for only about twelve days after we first saw it.
If you entered credentials on this page, change your Cloudflare password immediately and turn on two-factor authentication with an authenticator app or security key. Then review active sessions, API tokens, account members and recent DNS or page-rule changes for anything you did not make. Revoke any tokens you cannot account for and change the password on any other service that shared it. Defenders should block sfhryu.com at the DNS and proxy level and search logs for past visits. Do not block the hosting IP, since it is shared Cloudflare address space serving countless legitimate sites.
Edge-IP 声誉不属于此域。
gerald.ns.cloudflare.comLocation describes the IP network.
9ca2e612d83bba6d9a5390a441335d29c125f2b20e0f63df697d29c2482eaec3Saved 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 sfhryu.com · checked Sep 14, 2026
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.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
不可用→可访问
可访问→不可用
可访问
No threat flag
View source6/89 engine detections
View source4 community references
View sourcesfhryu.com
View source已存储 142 个仿冒域名
显示 142 个中的 100 个
1 条社区报告
类别PHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-03T11:05:27.399Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
sfhryu.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 ↗
sfhryu.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.