VirusTotal
15 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 3443x43x34x.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 15/89 (Criminal IP, alphaMountain.ai, BitDefender, ESET, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 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
3443x43x34x.pages.dev is an impersonation phishing page that posed as Cloudflare, aimed at people who manage websites, domains or DNS through Cloudflare. PhishDestroy first flagged it on 2026-09-05. The site has been offline since 2026-09-13 and was still dead on 2026-10-19, with its content blocked by the hosting provider. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning banner and matches that block, while we classified the original content as Cloudflare impersonation.
Cloudflare impersonation pages copy the look of Cloudflare's dashboard, sign-in screen or security check so the visitor believes they are dealing with Cloudflare itself. The usual goal is to capture the login email, password and sometimes a one-time code, which gives the attacker control of the victim's Cloudflare account. With that access, an attacker can redirect a victim's domains, alter DNS records, create API tokens or quietly point legitimate sites at malicious content. Hosting the lure on a free subdomain helped it look like part of Cloudflare's own ecosystem.
Fifteen of 89 VirusTotal engines marked the page as malicious when checked on 2026-09-14, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Criminal IP, alphaMountain.ai and Google Safe Browsing. Google Safe Browsing separately lists it under SOCIAL_ENGINEERING, the category used for deceptive phishing pages. It also appears on the PhishDestroy blocklist. The verdicts of several established security vendors, together with the provider takedown, back the classification.
The subdomain was created on 2026-09-02 and caught three days later, and it went offline about eleven days after creation, so this was a short-lived throwaway deployment. It was published through Cloudflare Pages and served from Cloudflare, Inc. network space geolocated to Canada, which means the brand being imitated was also the platform carrying the lure. The random-looking subdomain name points to quick, disposable setup rather than an attempt at a convincing lookalike address.
If you entered credentials on this page, change your Cloudflare password right away, and change it on any other service where you reused it. Turn on or reset two-factor authentication, sign out all active sessions, and review your account's API tokens, member list, DNS records and page rules for anything you did not create. Check your domains for unexpected redirects or nameserver changes. Defenders should block the domain, search proxy and email logs for visits or messages linking to it, and alert staff that real Cloudflare sign-ins never take place on random pages.dev subdomains.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
cf4ff462fe49bc437a86d1726699969fe1025c9750a41a19a83cd23cb8631c24Saved 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.
3443x43x34x.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 flag recorded→Flag recorded
Threat flag recorded
View source15/89 engine detections
View source3443x43x34x.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 ↗
3443x43x34x.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.