VirusTotal
4 / 89 engine detections
打开报告“Suspected Phishing | Cloudflare”
冒充 Cloudflare: 121149.com — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 4/89 (Forcepoint ThreatSeeker, Fortinet, PhishFort, SOCRadar); Spamhaus DBL_PHISH; CF Radar…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 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
121149.com is a phishing site that impersonates Cloudflare, the web infrastructure and security company. It targets people who use Cloudflare accounts and visitors used to clicking through Cloudflare security screens. PhishDestroy first detected the domain on 2026-08-10. The site has been offline since 2026-09-13, and when last checked on 2026-10-19 it was still dead with its content blocked by the provider.
Cloudflare impersonation pages usually copy the look of a Cloudflare login form or a "checking your browser" verification screen. The goal is to get the victim to type in account credentials or follow instructions they would not trust from an unknown site. Stolen Cloudflare logins can give an attacker control over a victim's domains, DNS and traffic. The current page title reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial, while we classify the domain as a Cloudflare impersonation page.
Four of 89 VirusTotal engines flagged the domain as of 2026-09-13: Forcepoint ThreatSeeker, Fortinet, PhishFort and SOCRadar. That count is modest, but PhishFort specializes in brand-impersonation phishing, which makes its flag relevant here. Spamhaus lists the domain in its Domain Block List under the phishing category (DBL_PHISH). It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain resolves to 104.21.3.250 on Cloudflare, Inc.'s network, geolocated to Canada. Hosting a Cloudflare impersonation behind Cloudflare's own network let the operator put the brand's real infrastructure in front of the fake. That same placement also made the site easy for the provider to cut off once reported. The provider-blocked status shows that is what happened.
If you entered a Cloudflare email and password on this site, change the password immediately and enable or reset two-factor authentication. Then review your account's audit log, API tokens, member list and DNS records for changes you did not make. Revoke any API tokens you cannot account for, and check that your domains still point where they should. If you reused that password anywhere else, change it there too. Defenders should block 121149.com at DNS and proxy level, search mail and web logs for earlier visits, and alert staff who manage Cloudflare accounts.
Edge-IP 声誉不属于此域。
beau.ns.cloudflare.comuma.ns.cloudflare.comLocation describes the IP network.
a972272d7f7f99c68c40007d2efa745c88c00b0cd1850c9a043ab74bb7e4a165Saved 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 121149.com · checked Sep 13, 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.
121149.com
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
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不可用→可访问
可访问→不可用
0→4
4 community references
View sourceNo threat flag
View source4/89 engine detections
View source121149.com
View source已存储 142 个仿冒域名
显示 142 个中的 100 个
2 条社区报告
类别IMPERSONATION
Brand abuse: impersonation, fake affiliation, gambling, impersonating Las Vegas Sands Corp
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 ↗
121149.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.