VirusTotal
8 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: access-trezz-io-en-hrd.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 8/89 (BitDefender, ESET, Fortinet, G-Data, Lionic)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 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-hrd.pages.dev is an impersonation phishing page that abuses the Cloudflare name. It lives on a free Cloudflare Pages subdomain, which lends a disposable site a borrowed sense of legitimacy. PhishDestroy first flagged it on 2026-08-09. The site has been offline since 2026-09-13 and was still dead when last checked on 2026-10-19, with its content blocked by the provider.
Impersonation pages copy the look and wording of a trusted brand so visitors drop their guard and hand over logins, account details or other sensitive information. A long, keyword-stuffed hostname under a familiar platform domain is a common way to make a throwaway page look official at a glance. Anything typed into such a page goes straight to the operator. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning screen rather than the original lure, while our classification describes the page that ran before the block.
On 2026-09-13, 8 of 89 VirusTotal engines flagged the page as malicious: BitDefender, ESET, Fortinet, G-Data, Lionic, PhishFort, Sophos and Webroot. That is a modest share of engines, but the vendors include a dedicated anti-phishing service alongside several major endpoint products, so the verdict does not rest on a single source. PhishDestroy lists the domain on its blocklist. The hosting provider's own block of the content independently confirms that the page was judged harmful.
The page is served through Cloudflare's network, with the hosting IP geolocated to Canada, and it was set up through Cloudflare Pages. The registration date recorded for the subdomain is 2026-08-21, later than our first sighting on 2026-08-09. Its TLS certificate came from Google Trust Services, so a padlock in the browser said nothing about whether the page was safe.
If you entered a password on this page, change it right away on the real service and on any other account that uses the same password. Turn on two-factor authentication and sign out of all active sessions. Watch for follow-up emails or messages that refer to your visit, because phishing operators often reuse captured contacts. Defenders should block the full hostname, search proxy and DNS logs for visits since 2026-08-09, and treat unfamiliar pages.dev subdomains that use brand-like wording with suspicion.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
a7ffbdcfe9663441b3bb674855229274250c4b928dcc060796a3f4f6b2ca4985Saved 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 source8/89 engine detections
View sourceaccess-trezz-io-en-hrd.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-trezz-io-en-hrd.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-hrd.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.