VirusTotal
0 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: 8f43e77f-34aa-4acd-bd26-2ed234bbbc82.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 0/89; 1 external…
يبقى تحليل 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
This throwaway subdomain on Cloudflare Pages was built to pass itself off as Cloudflare, aiming at people who trust the brand's login, security and verification screens. PhishDestroy first flagged it on 2026-08-01. The site has been dead since 2026-09-13, with its content blocked by the hosting provider, and it was still offline when last checked on 2026-10-19.
Impersonation pages like this borrow Cloudflare's look and wording to make a fake account sign-in, security check or verification prompt seem routine. Whatever a visitor types, such as an email, password or one-time code, goes to the operator, who can then take over the victim's account and the websites and DNS settings tied to it. The page title now reads "Suspected Phishing | Cloudflare", which matches Cloudflare's own warning notice rather than the original lure, and it lines up with the provider block on the content.
PhishDestroy classified the site as impersonation, and ScamSniffer independently lists it, so two separate blocklists agree. VirusTotal tells a different story. None of its 89 engines flagged the address when it was checked on 2026-09-13, the same day the site went offline. That gap shows how short-lived pages on shared hosting can slip past antivirus vendors entirely, which makes curated blocklists the more reliable signal here.
The Pages project dates to 2024-09-27, nearly two years before PhishDestroy detected it, so this was not a freshly spun-up lure. It sat on Cloudflare's own network, resolving to an address geolocated in Canada. Hosting a fake Cloudflare page on Cloudflare's free Pages service puts the scam on a domain suffix many users already associate with the real company, and that familiarity is what the lure relies on.
If you entered Cloudflare credentials on this page, change your Cloudflare password at once, sign out all sessions and reset two-factor authentication, especially if you typed in a one-time code. Then review your account's audit log, API tokens, DNS records and member list for changes you did not make. Use the same password nowhere else, and if you did, change it on those services too. Defenders should block the subdomain, search proxy and mail logs for visits or links to it, and treat random-looking pages.dev hostnames that carry Cloudflare branding as suspect.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
15d3f4c2b521954be606f7a39a0b39e83efc1cc31c76e7be08e0f6d10664bbceSaved 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
8f43e77f-34aa-4acd-bd26-2ed234bbbc82.pages.dev
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 source8f43e77f-34aa-4acd-bd26-2ed234bbbc82.pages.dev
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
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 ↗
8f43e77f-34aa-4acd-bd26-2ed234bbbc82.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.