VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access--trezz-io-en-logi.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; PhishDestroy score 48/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--trezz-io-en-logi.pages.dev is an impersonation phishing page hosted on a free Cloudflare Pages subdomain. Its hostname is stitched together from login-style fragments ('access', 'en', 'logi') to look like a sign-in address. PhishDestroy first flagged it on 2026-07-27. The site went offline on 2026-09-13 and was still dead at the last check on 2026-10-19, with its content blocked by the hosting provider.
Pages like this copy a trusted service's look and send visitors to what appears to be a routine login step. Anything typed in, such as an email, password or one-time code, goes straight to the operators. They can then take over the account and reuse those credentials elsewhere. The page title now reads 'Suspected Phishing | Cloudflare', which is Cloudflare's own warning screen rather than the original lure. That title reflects the provider's block, while our impersonation classification describes what the site did before it was taken down.
Independent detection was weak. When VirusTotal last scanned the site on 2026-09-13, none of its 89 engines flagged it, so a reputation check alone would have given visitors no warning. The PhishDestroy blocklist is the only listing behind this classification. The strongest outside confirmation is the hosting provider's decision to replace the page with a phishing interstitial.
The site sits on Cloudflare Pages, served from Cloudflare, Inc. network space at 188.114.96.9 and geolocated to Canada. Free Pages subdomains give phishing operators instant hosting and automatic HTTPS, here through a Google Trust Services certificate. The padlock therefore says nothing about who runs the site. The listed creation date of 2026-08-15 falls after our first sighting on 2026-07-27, a common mismatch for platform subdomains that have no normal domain registration.
If you entered a password on this page, change it immediately on the real service and on any other account that uses the same password. Then sign out all active sessions. Turn on two-factor authentication with an authenticator app or hardware key, and review recent logins and recovery email or phone settings for changes you did not make. Defenders should block the hostname and treat other look-alike pages.dev subdomains as suspect. Because antivirus engines missed this site, do not rely on a clean VirusTotal result to decide whether a link is safe.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
5742343d7ecf1ec2cffe7af8ed22043c652e2fc86910c458f3f9f3ddeded3fa4Saved 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--trezz-io-en-logi.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリIMPERSONATION
Brand abuse: phishing, impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
access--trezz-io-en-logi.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-en-logi.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.