VirusTotal
14 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 3ulqj-3qvq-fc61-ahmh7v-6x4b.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 14/89 (alphaMountain.ai, BitDefender, CyRadar, ESET…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開く悪意あり
レポートを開くno 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
This throwaway Cloudflare Pages subdomain hosted a phishing page impersonating Cloudflare. Its targets are people who manage websites, domains and DNS through a Cloudflare account. PhishDestroy first flagged it on 2026-08-06. The site has been offline since 2026-09-13, its content blocked by the hosting provider, and it was still dead when last checked on 2026-10-19.
Cloudflare impersonation pages usually copy the dashboard login or a security-check prompt and claim the visitor must sign in to fix an account or domain problem. Anything typed into the form goes to the attacker, not to Cloudflare. A stolen Cloudflare login can let an attacker redirect DNS, take over domains, or plant malicious content on a victim's own sites, so the damage can spread to that site's visitors. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning page shown after the provider blocked it, while PhishDestroy classified the original content as Cloudflare impersonation.
On 2026-09-13, 14 of 89 VirusTotal engines marked the address as malicious. The flagging vendors included alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Agreement from several unrelated security companies supports the phishing verdict, although most engines never caught it. PhishDestroy's blocklist is the only list carrying it, and the provider's own block confirms the host also judged the content abusive.
The subdomain was created on 2026-07-20, 17 days before PhishDestroy detected it. That gap is typical of disposable phishing pages spun up for a short campaign. It ran on the free Cloudflare Pages service, so it shared Cloudflare's own network, routed through a Canadian edge, and carried an ordinary Google Trust Services certificate. Hosting a fake Cloudflare page on a genuine Cloudflare address makes the lure more convincing, because the padlock and hosting look legitimate.
If you entered credentials on this page, change your Cloudflare password at once and log out all active sessions. Enable or re-enroll two-factor authentication, then revoke and reissue any API tokens and keys. Review your account's audit log, DNS records, page rules and member list for changes you did not make. If you used the same password on any other service, change it there too. Defenders should block the subdomain, watch for logins from unfamiliar locations on Cloudflare accounts, and remind staff to reach the Cloudflare dashboard only by typing its address directly.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
aefe596151934c82ed05c92a3121727e078ce18dea75e333d00859d06d37e9c5Saved 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.
3ulqj-3qvq-fc61-ahmh7v-6x4b.pages.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 source14/89 engine detections
View source3ulqj-3qvq-fc61-ahmh7v-6x4b.pages.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 ↗
3ulqj-3qvq-fc61-ahmh7v-6x4b.pages.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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.