VirusTotal
0 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Cloudflare: amp-ayubetclick.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
amp-ayubetclick.pages.dev is an impersonation phishing page hosted on a Cloudflare Pages subdomain, classified by PhishDestroy as abusing the Cloudflare brand. PhishDestroy first saw it on 2026-08-10. The site went offline on 2026-09-13, and on 2026-10-19 it was still dead with its content blocked by the hosting provider. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning screen, while our classification covers the impersonation content the site served before the block.
Impersonation pages borrow the look of a trusted name so visitors drop their guard. They often copy the branding and layout of a familiar service, then ask the visitor to sign in, confirm an account or enter personal details. Whatever is typed goes to the operator, who can reuse the credentials, sell them or use them to reach linked accounts. A free pages.dev address helps the trick because the hostname carries the real platform's domain, so the link looks routine at a glance.
Independent detection is thin. On 2026-09-13, none of the 89 VirusTotal engines flagged the domain, so a clean scan here should not be read as a sign of safety. Its only blocklist listing is PhishDestroy's. The strongest outside signal is the provider's own action: Cloudflare took the content down and replaced it with its suspected-phishing notice.
The subdomain dates to 2026-06-08, about two months before PhishDestroy detected it, so it was live for a while before being caught. It sits on Cloudflare Pages and resolves to Cloudflare, Inc. network space at 188.114.97.9, geolocated to Canada. The certificate from Google Trust Services (WE1) is standard for this platform and gives visitors no reason to trust the page.
If you entered a password on this page, change it right away on the real service and anywhere else you reuse it, then turn on two-factor authentication. Review recent sign-in activity and connected sessions for logins you do not recognize. Treat any follow-up emails or messages that mention this page as phishing. Defenders should block the exact amp-ayubetclick.pages.dev hostname rather than all of pages.dev, and search proxy and mail logs from 2026-06-08 onward for users who reached it.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
e2b93b2fc504514602bb5d9b90afdfcd6fac65d3b1abc2a5125c99eec63cff3bSaved 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 sourceamp-ayubetclick.pages.dev
View source١٤٢ نطاقًا متشابهًا محفوظًا
عرض 100 من 142
بلاغ مجتمعي واحد
الفئةIMPERSONATION
Brand abuse: impersonation, impersonating Betclic
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
amp-ayubetclick.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 ↗
amp-ayubetclick.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.