VirusTotal
12 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-eng-trezr--x-logg-u.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, CyRadar, ESET…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 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-eng-trezr--x-logg-u.pages.dev is an impersonation phishing page that PhishDestroy classifies as abusing the Cloudflare brand. Its hostname strings together "access", "trezr" and "logg", wording made to look like a wallet or account login and aimed at crypto users who reach it through a link. PhishDestroy first flagged it on 2026-08-09. The site has been offline since 2026-09-13, and on 2026-10-19 it was still dead with its content blocked by the provider.
Impersonation pages like this copy the look of a trusted service so visitors type in credentials, recovery details or other secrets, which go straight to the operator. A login lure dressed up as a wallet access page often asks for a seed phrase or password, and either one gives the attacker control of the account or funds. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial rather than the original lure, while we classify the site itself as an impersonation phishing page.
On 2026-09-13, 12 of 89 VirusTotal engines flagged the hostname, including alphaMountain.ai, BitDefender, CyRadar, ESET, Fortinet, G-Data, LevelBlue and Lionic. That is a minority of engines, but the vendors come from several separate detection ecosystems and agree independently. The PhishDestroy blocklist lists the domain. The provider has since replaced the content with a phishing warning, which supports the verdict.
The site ran as a free subdomain on Cloudflare Pages, created on 2025-10-16, nearly ten months before PhishDestroy detected it. It resolved to Cloudflare, Inc. address space in Canada. Free static hosting platforms let operators put up throwaway lure pages quickly under a shared, reputable parent domain, and that is why the hostname itself does so much of the deceiving.
If you entered a seed phrase or recovery words on this page, treat the wallet as compromised and move any funds to a new wallet generated on a trusted device. If you entered a password, change it everywhere you reused it and turn on app-based 2FA. Remember that no legitimate hardware wallet or provider will ever ask for your recovery phrase on a website. Defenders should block the hostname, search proxy and mail logs for visits since 2026-08-09, and watch for look-alike Pages subdomains that use the same "access" and "logg" naming pattern.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
3550886d1ae4839f3a42c6e33e41e950090225a3ff69d3a647d2754885ded579Saved 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.
access-eng-trezr--x-logg-u.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 source12/89 engine detections
View sourceaccess-eng-trezr--x-logg-u.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: phishing, credential harvesting, impersonation, impersonating Trezor
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-eng-trezr--x-logg-u.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.