VirusTotal
12 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 344v34v5453.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 89 engine detections
レポートを開く悪意あり
レポートを開くThreat flag recorded
レポートを開くno community references
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
344v34v5453.pages.dev is a phishing page that impersonated Cloudflare. It ran on a random-looking subdomain of Cloudflare's own Pages hosting service, which made it look more legitimate to Cloudflare customers, website operators and administrators. PhishDestroy first flagged it on 2026-08-05. The site has been offline since 2026-09-13 and was still dead at the last check on 2026-10-19.
Pages that impersonate Cloudflare usually show a familiar Cloudflare-style login, account alert or browser-verification screen. The goal is to get the visitor to type in their account credentials or follow instructions the attacker controls. A stolen Cloudflare login can give someone control of DNS, domains and the sites behind them, so a single submitted password can affect a whole web property. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's warning label. We classified the site itself as an impersonation phishing page.
Twelve of 89 VirusTotal engines flagged the domain as of 2026-09-14. That is a moderate count, but the vendors are independent and well established: alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing and Gridinsoft. Google Safe Browsing lists it under SOCIAL_ENGINEERING, its category for deceptive pages that trick users into handing over information. The hosting provider has also blocked the content, and the domain is on the PhishDestroy blocklist.
The subdomain was created on 2026-08-03, only two days before we detected it. That pattern fits a disposable page set up for a short campaign. It was issued through Cloudflare Pages and served from Cloudflare, Inc. infrastructure, with the address geolocated to Canada. Its TLS certificate came from Google Trust Services (WE1), which Pages assigns automatically, so the browser padlock showed only an encrypted connection and nothing about the site's legitimacy.
If you entered credentials on this page, change your Cloudflare password right away and make sure no other site uses the same one. Then turn on or reset two-factor authentication and sign out all active sessions. Check your account's audit log, API tokens, DNS records and member list for anything you did not set up, and contact Cloudflare support if you see unauthorized changes. Defenders should block the domain and treat random-string pages.dev hosts that use Cloudflare branding with suspicion. They should also remind staff that real Cloudflare account actions happen only on the official dashboard.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
87cbb88b060e4648c24037c2537b58c4a027a654503594a00b31a26d409d970bSaved 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.
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 flag recorded→Flag recorded
Threat flag recorded
View source12/89 engine detections
View source344v34v5453.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
344v34v5453.pages.dev
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 ↗
344v34v5453.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.