VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-trezrr-logo.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
access-trezrr-logo.pages.dev is an impersonation phishing page hosted on a Cloudflare Pages subdomain and classified by PhishDestroy as abusing the Cloudflare brand. The hostname itself carries a misspelling, "trezrr", that resembles the name of the Trezor hardware wallet, a pattern built to catch people who skim links. PhishDestroy first detected it on 2026-08-10. The site has been offline since 2026-09-13, and when it was last checked on 2026-10-19 it was still dead with its content blocked by the provider.
Impersonation pages borrow a trusted name and look so that visitors lower their guard and type in logins, recovery details or other sensitive data, which go straight to the operator. A free pages.dev address helps the trick, because the link ends in a legitimate platform domain rather than an obviously strange one. The page title now reads "Suspected Phishing | Cloudflare", which is the wording of Cloudflare's own warning notice and fits the provider block. That differs from the content we classified as impersonation.
Independent detection is thin. On 2026-09-13, the same day the site went offline, VirusTotal showed 0 detections out of 89 engines. That clean score reflects how quickly short-lived Pages projects come and go, not that the site was safe. PhishDestroy's blocklist is the listing that backs this classification, and the provider's own phishing block on the content points the same way.
The Pages project dates to 2025-09-19, nearly eleven months before PhishDestroy flagged it, so it sat unnoticed for a long stretch. It ran entirely on Cloudflare: Cloudflare Pages for the subdomain and a Cloudflare, Inc. network address located in Canada. The Google Trust Services certificate is the standard automatic one for such projects, so the padlock said nothing about who was behind the page.
If you entered a password on this page, change it right away anywhere you reused it, turn on app-based two-factor authentication, and check for logins you don't recognize. If you typed a wallet recovery phrase or PIN, treat that wallet as compromised and move your funds to a new wallet with a freshly generated phrase from a device you trust. Defenders should block the hostname, search mail and proxy logs for earlier visits, and watch for new look-alike pages.dev subdomains with misspelled wallet or brand names.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
e23cbae0bc3f7e289a6464d8af6c4ae0b8ba092590ccaec9937024941e39f0e3Saved 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 sourceaccess-trezrr-logo.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: impersonation, phishing, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
access-trezrr-logo.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 ↗
access-trezrr-logo.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.