VirusTotal
11 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-trezz-io-eng-log.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CyRadar, ESET…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 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-trezz-io-eng-log.pages.dev is a phishing page that PhishDestroy classifies as Cloudflare impersonation, hosted on a free Cloudflare Pages subdomain with a hostname stitched together from words like access, eng and log. It targets anyone who might trust a page that looks like it comes from Cloudflare or sits on its infrastructure. PhishDestroy first saw it on 2026-07-27. The site has been offline since 2026-09-13 and was still dead at the last check on 2026-10-19.
Impersonation pages like this copy the look of a trusted service and present a login or verification step. Anything typed into it goes to the operator instead of the real provider. Victims lose account passwords and sometimes one-time codes, which lets the attacker take over the account. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial rather than the original lure, while our classification refers to the impersonation content it served before the provider blocked it.
VirusTotal scanned the site on 2026-09-13, the same day it went offline, and 11 of 89 engines flagged it. The flagging vendors were alphaMountain.ai, BitDefender, CyRadar, ESET, Fortinet, G-Data, Lionic and PhishFort, a mix of mainstream antivirus vendors and phishing-focused specialists. That count is moderate, but agreement across that range of vendors supports the verdict. PhishDestroy lists the domain on its blocklist. The hosting provider has since blocked the content itself.
The site ran on Cloudflare Pages and resolved to Cloudflare, Inc. network space located in Canada. Its registration is dated 2026-08-23, almost a month after PhishDestroy first detected it on 2026-07-27, so the two dates do not follow the usual register-then-detect order. A free platform subdomain like this costs nothing and can be thrown away quickly, which suits short-lived phishing. The Google Trust Services certificate gave the page a standard padlock and is no sign of legitimacy.
If you entered a username or password on this page, change that password right away on the real service. Change it anywhere else you reused it. Turn on or reset two-factor authentication, sign out other active sessions, and check account activity for logins or changes you don't recognize. Be wary of follow-up emails that reference the same login. Defenders should block the hostname, search proxy and DNS logs for visits since 2026-07-27, and reset credentials for any users who reached the page.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
d256a77c21b294ebfa4e1ffaaf46ec7c27205c093eb97d7283fb1f1b9b689050Saved 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 source11/89 engine detections
View sourceaccess-trezz-io-eng-log.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: phishing, credential harvesting, impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
access-trezz-io-eng-log.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-trezz-io-eng-log.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.