VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-trezz-io-eng-cdn.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-trezz-io-eng-cdn.pages.dev is an impersonation phishing page that poses as Cloudflare and targets people who trust that brand. It runs on a Cloudflare Pages subdomain, so the address carries a legitimate-looking platform suffix. PhishDestroy first flagged it on 2026-07-27. The site has been offline since 2026-09-13, the provider has blocked its content, and it was still dead at the last check on 2026-10-19.
Impersonation pages like this copy the look of a trusted service and ask the visitor to sign in, verify an account or confirm details. Whatever is typed into the form goes to the operator instead of the real company, and that can include passwords, one-time codes and personal data. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning page and matches the provider block. We classified the site as an impersonation of Cloudflare.
Independent scanners did not catch this site. VirusTotal returned 0 detections out of 89 engines when it checked on 2026-09-13, the same day the site went offline. The classification rests on PhishDestroy's own listing. The provider's later block, which replaced the content with a phishing warning, shows that the hosting platform also took action against it.
PhishDestroy recorded the page on 2026-07-27, earlier than the 2026-08-15 registration date listed for it on Cloudflare Pages. Free Pages subdomains take minutes to create and come with a reputable parent domain, which helps a short-lived lure look credible. The site resolved to 188.114.97.9 on Cloudflare, Inc.'s network, geolocated to Canada. Its TLS certificate came from Google Trust Services (WE1), so the padlock in the browser said nothing about whether the site was legitimate.
If you entered credentials on this page, change your Cloudflare password at once, plus any other account that used the same password. Turn on or reset two-factor authentication, sign out all active sessions and review recent account activity. Cloudflare account holders should also check for new API tokens, members or DNS changes they did not make, and rotate any keys that could have been exposed. Defenders should block this specific pages.dev hostname rather than the whole platform. They can also search proxy and mail logs for any users who visited it between 2026-07-27 and 2026-09-13.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
309e87a5d7f3c908bdfdd1e037911bb63e0181bee248857e97857c71988edc4bSaved 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-eng-cdn.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-trezz-io-eng-cdn.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-cdn.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.