VirusTotal
13 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: wptjn16kwg-fghzd83pli-6vz82d-wp38k.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CyRadar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開くno community references
レポートを開く80/100
レポートを開く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 is a phishing page that imitates Cloudflare and runs on a randomly named subdomain of Cloudflare's own Pages hosting service. Its likely targets are people who manage websites and DNS through Cloudflare, and visitors used to seeing Cloudflare branding on security checks. PhishDestroy first flagged it on 2026-09-08. The site has been offline since 2026-09-17, and its content was still blocked by the hosting provider when last checked on 2026-10-19.
Cloudflare impersonation pages usually copy the brand's login screens or its familiar "checking your browser" challenges. Victims are pushed to type in their Cloudflare credentials or to follow fake verification steps. A stolen Cloudflare login can hand an attacker control of a victim's domains, DNS records and traffic, which makes these accounts valuable. The page title now reads "Suspected Phishing | Cloudflare", which is the wording of Cloudflare's own warning page, while PhishDestroy classified the site itself as Cloudflare impersonation.
On 2026-09-18, VirusTotal showed 13 of 89 security engines flagging the site. The vendors included alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Agreement from that many unrelated engines makes a false positive unlikely. urlscan.io returned a malicious verdict and matched the page to generic Cloudflare branding. PhishDestroy lists the domain on its blocklist.
The subdomain was created on 2026-09-02, six days before PhishDestroy detected it, and was taken offline about nine days after detection. Free Pages hosting gives operators a trusted-looking Cloudflare address, a valid certificate from Google Trust Services (WE1) and fresh random names for every deployment. The IP sits on Cloudflare, Inc. infrastructure geolocated to Canada. Because the brand being impersonated also owns the hosting, the copy looks more convincing, and the provider can also shut it down quickly.
If you entered a Cloudflare email and password on this page, change the password right away and enable or reset two-factor authentication. Then review active sessions and API tokens, and remove any you do not recognize. Check your zones for DNS records, page rules, Workers or account members you did not add. If you followed any "verification" instructions that had you run commands or download files, scan the device and change passwords stored on it. Defenders should block the hostname and watch for similar random-named Pages subdomains that use Cloudflare branding.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
74ded98b8256aa7fa8cf3adf2969364889f89728bcb87873c0acf1f3b0517ef8Saved 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 wptjn16kwg-fghzd83pli-6vz82d-wp38k.pages.dev · checked Sep 16, 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.
wptjn16kwg-fghzd83pli-6vz82d-wp38k.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→13
到達可能→利用不可
到達可能
No threat flag
View source13/89 engine detections
View sourcewptjn16kwg-fghzd83pli-6vz82d-wp38k.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 ↗
wptjn16kwg-fghzd83pli-6vz82d-wp38k.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.