VirusTotal
8 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: ijdkc.com — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 8/89 (alphaMountain.ai, BitDefender, CRDF, G-Data, Gridinsoft); Google Safe Browsing…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
8 / 89 engine detections
فتح التقريرThreat flag recorded
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ijdkc.com is a phishing domain that impersonated Cloudflare and was aimed at people who use or trust the company's services, especially website operators with Cloudflare accounts. PhishDestroy first flagged it on 2026-09-06. The site went offline on 2026-09-15, and as of 2026-10-19 its DNS no longer resolves. It is dead, but it remains on our blocklist in case it is revived or reused.
Cloudflare impersonation pages usually copy the look of the Cloudflare dashboard login or its browser check screen. The fake page then asks the visitor for their email, password or a verification step. Anyone who enters credentials gives attackers control of a Cloudflare account, which can mean control of DNS, traffic routing and the websites behind it. The page title read "Suspected Phishing | Cloudflare", which matches the wording of Cloudflare's own phishing warning screen, while PhishDestroy classifies the domain itself as an impersonation phishing page.
Eight of 89 VirusTotal engines flagged the domain as of 2026-09-17: alphaMountain.ai, BitDefender, CRDF, G-Data, Gridinsoft, Kaspersky, PhishFort and SOCRadar. That is a modest count, but it comes from a mix of general antivirus vendors and specialists in brand abuse and threat intelligence, so they reached the same verdict independently. Google Safe Browsing labels the site as social engineering, which triggers warnings in major browsers. The domain also appears in four AlienVault OTX threat pulses alongside the PhishDestroy listing.
The domain was registered on 2026-08-31, only six days before PhishDestroy caught it, and it stopped serving content nine days after that. A domain that is registered, used briefly and abandoned like this fits a disposable phishing campaign. It was registered through Cloudflare, Inc. and hosted on Cloudflare's network with a Canadian IP, so the operator used the impersonated brand's own infrastructure. Its certificate came from Google Trust Services, the standard issuer for sites behind Cloudflare, and says nothing about who ran the page.
If you typed Cloudflare credentials into this site, change your Cloudflare password immediately and sign out all active sessions. Turn on app-based or hardware-key two-factor authentication. Review your account for unfamiliar API tokens, team members, DNS changes or new page rules, and reverse anything you did not make. If you reused that password anywhere else, change it there too. Security teams should block the domain, search proxy and email logs for visits between 2026-08-31 and 2026-09-15, and reset credentials for any user who reached it.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
gerald.ns.cloudflare.comLocation describes the IP network.
949776e54f9926cf0ee8bb707465ff12b854a303c77c775d8e3ca2c85ab0abdbSaved 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.
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
غير معروف→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
غير متوفر→يمكن الوصول إليه
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
يمكن الوصول إليه
4 community references
View sourceThreat flag recorded
View source8/89 engine detections
View sourceijdkc.com
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
بلاغ مجتمعي واحد
الفئةPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as other. Threat detected at 2026-09-06T13:02:53.397Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ijdkc.com
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 ↗
ijdkc.com)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.