VirusTotal
0 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: acces-trzr-sute.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 0/89; PhishDestroy score 68/100. مسجّل…
يبقى تحليل 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
acces-trzr-sute.pages.dev is an impersonation phishing page that borrows Cloudflare's name and look to win the trust of anyone who lands on it. PhishDestroy first flagged it on 2026-08-09. The site has been offline since 2026-09-13, and its content was blocked by the hosting provider when last checked on 2026-10-19.
Impersonation pages like this copy the branding of a trusted service so visitors believe they are on a legitimate page. They are then pushed to type in logins, verification codes or other sensitive details, which go straight to the operator. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning notice, while PhishDestroy classified the site itself as a Cloudflare impersonation. Anything a victim entered before the block should be treated as stolen.
Independent support is thin. VirusTotal returned 0 detections out of 89 engines on 2026-09-13, the same day the site went offline, so automated scanners never caught it while it was live. PhishDestroy is the only blocklist carrying the domain. Cloudflare's own suspected-phishing notice replacing the page is the clearest outside signal that the provider agreed with the assessment.
The project sits on Cloudflare Pages under a free pages.dev subdomain. It was created on 2025-10-07, about ten months before PhishDestroy detected it. Throwaway subdomains like this cost nothing and inherit the reputation of a major platform, which helps explain the zero scanner hits. Traffic was served from Cloudflare, Inc. infrastructure geolocated to Canada, and the TLS certificate from Google Trust Services is the platform's standard issuance, so it says nothing about legitimacy.
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. Turn on two-factor authentication, preferably with an app or hardware key, and review recent logins and active sessions for anything you don't recognize. If you typed in a one-time code, assume the attacker may have used it and check your account settings for added emails, API tokens or forwarding rules. Defenders should block the domain and watch for similar pages.dev subdomains using Cloudflare branding. Because scanners missed this site, curated blocklists are worth feeding into mail and web filters.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
cff9fc7e8d35bcdd49760135de10172bcf61f7de0851262dfbc1b28b8ea47f7fSaved 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 sourceacces-trzr-sute.pages.dev
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
بلاغ مجتمعي واحد
الفئةIMPERSONATION
Brand abuse: impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
acces-trzr-sute.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 ↗
acces-trzr-sute.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.