VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-io-start-trezzer.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-io-start-trezzer.pages.dev is a phishing page that PhishDestroy classifies as impersonation, with Cloudflare as the brand it imitates. Its hostname uses wording like "access" and "start" to look like a legitimate setup or login link, and it targets crypto users who arrive through a shared link. PhishDestroy first flagged it on 2026-08-23. The site has been offline since 2026-09-13, and on 2026-10-19 it was still dead with its content blocked by the hosting provider.
Impersonation pages borrow a trusted name and layout so visitors lower their guard. They then ask for something valuable, usually account credentials or a wallet recovery phrase, and send whatever is typed straight to the operator. The page now shows the title "Suspected Phishing | Cloudflare", which is the provider's own warning screen, while our classification covers the impersonation content the page served before it was blocked. Anyone who handed over a password or seed phrase should assume the attacker has it.
Independent detection was weak. VirusTotal returned 0 detections from 89 engines on 2026-09-13, the same day the site went offline, so automated scanners never caught it while it was live. PhishDestroy is the only blocklist that lists it. The provider's decision to replace the content with a phishing warning backs up the classification more strongly than the scanner results do.
The project was created on Cloudflare Pages on 2025-10-31, almost ten months before PhishDestroy detected it. Free subdomains on shared platforms like this are cheap to create, inherit the parent domain's reputation and are easy to replace. The site resolves to Cloudflare, Inc. network space geolocated to Canada, and its certificate comes from Google Trust Services (WE1). Because the certificate was issued automatically, the padlock says nothing about whether the site is legitimate.
If you typed a password into this page, change it wherever you reused it and turn on app-based two-factor authentication. If you entered a wallet recovery phrase, treat that wallet as compromised and move your funds to a new wallet with a freshly generated seed phrase. Never enter a seed phrase on any website. Defenders should block the hostname, search mail and chat logs for links to it, and watch for new pages.dev subdomains using similar access and start wording.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
d6d1f54693818f0b505e8bf4348cbdb1e085d746c53bb01514cf741e13dcc963Saved 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-io-start-trezzer.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
access-io-start-trezzer.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-io-start-trezzer.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.