VirusTotal
15 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 42cr2c32.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 15/89 (alphaMountain.ai, BitDefender, CyRadar, 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
42cr2c32.pages.dev is a phishing page that impersonates Cloudflare and is aimed at people who manage websites, domains and DNS through a Cloudflare account. PhishDestroy first saw it on 2026-08-05, one day after it was deployed. The site has been offline since 2026-09-13, with its content blocked by the hosting provider, and it was still dead when last checked on 2026-10-19.
Pages that copy Cloudflare usually show a convincing dashboard login or a fake security or verification prompt. The goal is to get the visitor to type their account email, password and sometimes a one-time code. With those credentials, an attacker can take over the account, change DNS records, redirect domains to malicious servers or hijack the sites behind them. The page now carries the title "Suspected Phishing | Cloudflare", which matches the provider's own warning wording, while PhishDestroy classifies the deployment itself as a Cloudflare impersonation page.
Google Safe Browsing lists the site under SOCIAL_ENGINEERING, the category browsers use to warn users about deceptive pages. On VirusTotal, 15 of 89 engines flagged it as of 2026-09-14. The flagging vendors include alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, Fortra and G-Data. This is a solid cross-section of independent vendors, and it agrees with the PhishDestroy blocklist entry. The provider's decision to block the content adds further weight to the verdict.
The page sat on a randomly named subdomain of Cloudflare Pages, a free static hosting service, and was spotted within a day of its 2026-08-04 creation. Throwaway names like this are cheap to spin up and easy to replace, which is typical of short-lived phishing runs. Traffic was served from Cloudflare, Inc. network space geolocated to Canada. This means the operation borrowed the impersonated brand's own platform to look more legitimate.
If you entered your Cloudflare login on this page, change your password right away and make sure the new one is unique. Enable or reset two-factor authentication and sign out of all other sessions. Next, review your account's audit log, API tokens, DNS records, page rules and member list for changes you did not make. Revoke any token you do not recognise, and check that your registrar and email account are also secure. Defenders should block the domain, search proxy and mail logs for visits or links to it, and reset credentials for any users who reached it.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
6189ddf6a27c5d758c207cf2ef901a0f6a8307ec24a04ff75efb3d12361c3d9cSaved 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.
42cr2c32.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
14→15
到達可能→利用不可
No flag recorded→Flag recorded
Threat flag recorded
View source15/89 engine detections
View source42cr2c32.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 ↗
42cr2c32.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.