VirusTotal
13 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: akm3c-9abm-ofy-e2hfb-aeczbh.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 13/89 (Criminal IP…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
13 / 89 engine detections
فتح التقريرضار
فتح التقريرno community references
فتح التقرير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 randomly named Cloudflare Pages subdomain hosted a phishing page impersonating Cloudflare, aimed at people who manage websites, domains and DNS through Cloudflare accounts. PhishDestroy first flagged it on 2026-08-20. The site went offline on 2026-09-13, and the content was still blocked by the provider when we last checked on 2026-10-19.
Cloudflare impersonation pages copy the look of the dashboard or login screen so that a visitor will enter an email, password and often a 2FA code. A stolen Cloudflare login can give the attacker control of DNS, SSL settings and API tokens, so the damage can spread to every site on the account. The recorded page title, "Suspected Phishing | Cloudflare", is the wording of Cloudflare's own warning page, while PhishDestroy classified the site as a Cloudflare impersonation phishing page.
On 2026-09-13, 13 of 89 VirusTotal engines flagged the domain. The detections came from Criminal IP, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Because several unrelated vendors reached the same verdict on their own, the phishing classification does not depend on a single source. PhishDestroy lists the domain on its blocklist.
The subdomain was created on 2026-08-17, three days before PhishDestroy detected it, which fits a short-lived phishing setup. It was issued through Cloudflare Pages and served from Cloudflare, Inc. infrastructure geolocated to Canada. Hosting the fake page on Cloudflare's own platform gave it a domain that looks like it belongs to the brand it copied. Its Google Trust Services certificate was issued automatically, so the browser padlock said nothing about who ran the page.
If you entered credentials here, change your Cloudflare password right away and reset 2FA. Then sign out all active sessions and revoke any API tokens or keys you don't recognise. Check your DNS records, page rules, redirects and account members for changes you didn't make, and change the password on any other service where you used the same one. Defenders should block the domain, search proxy and email logs for visits or messages that link to it, and remind staff that real Cloudflare logins never come from a random pages.dev subdomain.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
fb210d8bafd30b39843291588daf5de08447cdded7ca33a0e0f3fc7ef40ea53cSaved 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 source13/89 engine detections
View sourceakm3c-9abm-ofy-e2hfb-aeczbh.pages.dev
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
akm3c-9abm-ofy-e2hfb-aeczbh.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 ↗
akm3c-9abm-ofy-e2hfb-aeczbh.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.