VirusTotal
7 / 89 engine detections
打开报告“Suspected Phishing | Cloudflare”
冒充 Cloudflare: 88fl.vip — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 7/89 (alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, PhishFort); Spamhaus DBL_PHISH…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
7 / 89 engine detections
打开报告恶意
打开报告DBL_PHISH
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
88fl.vip is an impersonation phishing domain built around the Cloudflare brand. It targets site owners, administrators and anyone who trusts Cloudflare's name. PhishDestroy first flagged it on 2026-08-10. The site has been offline since 2026-09-13, its content is blocked by the provider, and it was still dead when last checked on 2026-10-19.
Cloudflare impersonation usually relies on familiar Cloudflare visuals, such as login screens, security checks or account alerts, to make a request for credentials look routine. A victim who types a Cloudflare email and password, or approves a fake verification step, gives the operator a way into the account. That account controls DNS, SSL settings and traffic for every site behind it, so the damage reaches far beyond one login. The page currently displays the title "Suspected Phishing | Cloudflare", which is Cloudflare's own phishing warning, while our classification is impersonation of the Cloudflare brand.
7 of 89 VirusTotal engines flagged the domain as of 2026-09-13: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, PhishFort, SOCRadar and Webroot. That is a modest count, but it includes a dedicated brand-protection vendor and several mainstream web filters. Spamhaus lists the domain in its DBL with the DBL_PHISH tag, so mail and DNS filters that use Spamhaus will block it. It also appears in 4 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. It is served from Cloudflare, Inc. address space located in Canada, which means a site pretending to be Cloudflare was running on Cloudflare's own network. Its certificate comes from Google Trust Services (WE1), a standard issuer for Cloudflare-fronted sites. A valid padlock therefore said nothing about whether the page was legitimate. The provider-level block that followed shows the hosting network acted on the abuse.
If you entered Cloudflare credentials on this domain, change your Cloudflare password right away from the real dashboard. Enable or reset two-factor authentication and revoke any API tokens or global API keys you can't account for. Then check your zones for unexpected DNS records, page rules, Workers or newly added members, since attackers often use a hijacked account to redirect traffic quietly. Change the same password anywhere else you reused it. Defenders should block 88fl.vip at DNS and mail gateways and search proxy and email logs for earlier visits. Anyone who interacted with the site should be treated as a possible credential compromise.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP 声誉不属于此域。
elaine.ns.cloudflare.comLocation describes the IP network.
e6e04d59cc773e84400c39e5cbaea26f320701304ee7a291c1a1b2c915e59708Saved 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
88fl.vip
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
不可用→可访问
0→7
可访问→不可用
4 community references
View sourceNo threat flag
View source7/89 engine detections
View source88fl.vip
View source已存储 142 个仿冒域名
显示 142 个中的 100 个
1 条社区报告
类别IMPERSONATION
Brand abuse: impersonation, fake affiliation, phishing, credential harvesting, impersonating Marina Bay Sands
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 ↗
88fl.vip)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.