VirusTotal
1 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: alwasleeh-jo.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 1/89 (PhishFort); PhishDestroy score 76/100. レジストラ: Cloudflare Pages.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
alwasleeh-jo.pages.dev is an impersonation phishing page that borrows Cloudflare's branding and was hosted on Cloudflare's own Pages platform. It targets people who trust the Cloudflare name, whether they are account holders or ordinary visitors who expect a Cloudflare screen to be legitimate. PhishDestroy first flagged it on 2026-09-09. The site has been offline since 2026-09-13 and was still dead when we last checked on 2026-10-19.
Cloudflare impersonation works because its screens are familiar. Its account logins, security checks and "verify you are human" prompts appear across much of the web, so a convincing copy rarely makes visitors suspicious. Scam pages of this kind usually ask for credentials or personal details under the cover of a routine check. Anything typed in goes straight to the operator, and stolen Cloudflare logins can give control over a victim's domains, DNS and hosted sites. The page title now reads "Suspected Phishing | Cloudflare", which is the provider's own block notice. We classified the original content as Cloudflare impersonation.
Independent detection is thin. On 2026-09-13, only PhishFort flagged the domain out of 89 VirusTotal engines. PhishDestroy is the only blocklist carrying it. The clearest outside confirmation is the provider block itself: Cloudflare took the content down and put its phishing warning in its place.
The pages.dev subdomain was created on 2026-08-11, 29 days before PhishDestroy detected it. That is a short life typical of throwaway phishing deployments. It ran on a Cloudflare, Inc. network address in Canada and used a Google Trust Services certificate, the standard setup for Pages projects. Pages hosting is free and quick to set up, and a pages.dev address can look like a genuine Cloudflare property to a casual visitor.
If you entered a Cloudflare password on this site, change it immediately and turn on two-factor authentication. Then review your account for unfamiliar API tokens, members, DNS changes or new Pages and Workers deployments. If you reused that password on other services, change it there too. If you submitted email or other personal details, expect targeted follow-up phishing. Defenders should block the hostname and watch for lookalike pages.dev subdomains using Cloudflare branding. Report any new copies to Cloudflare's abuse team so they can be taken down as quickly as this one was.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
13a81523203300c9142c48079b2e19a74e6690a5b688fc4978989eec568d35b1Saved 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.
alwasleeh-jo.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 source1/89 engine detections
View sourcealwasleeh-jo.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-09T07:29:42.823Z.
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 ↗
alwasleeh-jo.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.