VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: about-trzr-bridg.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; PhishDestroy score 68/100. レジストラ: Cloudflare Pages.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 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
about-trzr-bridg.pages.dev is an impersonation phishing page that trades on the Cloudflare brand. It sits on a throwaway subdomain of Cloudflare's own free Pages hosting, so the address looks native to the provider it imitates. PhishDestroy flagged it on 2026-08-26, the same day it went live. The site has been offline since 2026-09-13 and was still dead when rechecked on 2026-10-19, with its content blocked by the hosting provider.
Impersonation pages copy the look of a trusted service so visitors type in logins, recovery details or other sensitive data, which go straight to the operator. A Cloudflare-themed lure works because many people know the brand from security checks and account dashboards, and they tend to follow its prompts without much thought. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial. That differs from our impersonation classification and reflects the provider's block, not the original lure.
The strongest independent signal is Cloudflare's own action: it pulled the content and replaced it with a phishing warning. VirusTotal returned 0 detections out of 89 engines on 2026-09-13, the day the site went offline. Antivirus vendors never caught up with this short-lived subdomain. PhishDestroy is the only blocklist carrying it. For a page that lived barely three weeks, the lack of scanner hits shows how easily fresh lures slip past automated checks.
The subdomain was created on 2026-08-26 and detected that same day, which fits a disposable setup built for quick use. It was issued through Cloudflare Pages and resolved to 172.66.44.140 on Cloudflare's network, geolocated to Canada. Its certificate from Google Trust Services (WE1) is issued automatically to Pages sites. The padlock only confirms an encrypted connection. It says nothing about who runs the page.
If you entered a Cloudflare password on this page, change it right away and turn on or reset two-factor authentication. Then check your account for unfamiliar API tokens, members, DNS changes or new Pages and Workers deployments. Reuse of that password anywhere else means changing it there too. Defenders should block this specific subdomain rather than all of pages.dev and search proxy and email logs for earlier visits. Users who reached the page should be treated as possibly compromised until their credentials are rotated.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
7caf34a357ca70b9cdb6936d22dca2120c54c08400117aa259736d1e6ba92c29Saved 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 source0/89 engine detections
View sourceabout-trzr-bridg.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
about-trzr-bridg.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 ↗
about-trzr-bridg.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.