VirusTotal
1 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: allow--suite-rezor-app.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 1/89 (PhishFort); PhishDestroy score 76/100. レジストラ: Cloudflare…
元のフォレンジック記録を保持するため、下の 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
allow--suite-rezor-app.pages.dev is an impersonation phishing page that posed as Cloudflare. It was built on Cloudflare's own free Pages hosting, so its address carried a familiar Cloudflare suffix. Its targets were people who manage websites or domains through Cloudflare. PhishDestroy first flagged it on 2026-08-09. The site has been offline since 2026-09-13, and it was still dead and blocked by the provider at the last check on 2026-10-19.
A page that copies a provider's look and lives on that provider's own hosting gets a head start on trust. A visitor sees the brand styling and the platform's address and has little reason to doubt the login prompt. The words "allow" and "suite" in the subdomain point to a fake authorization or account-access screen. Anyone who signed in there would hand over their Cloudflare credentials. That account can control DNS, domains and site traffic, so an attacker who takes it can redirect or hijack every property behind it. The page title now reads "Suspected Phishing | Cloudflare", Cloudflare's own warning label, which matches the provider block, while our classification describes the original content as Cloudflare impersonation.
Independent detection is thin. On 2026-09-13, only PhishFort out of 89 VirusTotal engines flagged the address. PhishDestroy is the only blocklist carrying it. The strongest outside confirmation comes from the host itself: Cloudflare blocked the content and replaced it with a phishing warning.
The Pages project dates to 2025-10-14, about ten months before PhishDestroy caught it. That gap suggests it either sat unused or ran quietly for a long time. Hosting resolves to Cloudflare's network, geolocated to Canada. The Google Trust Services certificate is standard for Pages sites, so the padlock gave visitors no real signal about whether the page was safe.
If you entered Cloudflare credentials on this page, change your password right away and turn on or reset two-factor authentication. Then sign out all active sessions. In your account, check for API tokens, team members, DNS records, page rules or Workers you did not create, and remove anything unfamiliar. If you reused the same password anywhere else, change it there too. Security teams should block the hostname and search proxy and email logs for visits or lures that pointed to it. They should also warn staff who administer Cloudflare that sign-in or authorization prompts can appear on legitimate-looking platform subdomains.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
18edc22631f8275cfb25fb5c57d638392805605798489b23d18ba3fa6ebae1a6Saved 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 threat flag
View source1/89 engine detections
View sourceallow--suite-rezor-app.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: phishing, impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
allow--suite-rezor-app.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 ↗
allow--suite-rezor-app.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.