VirusTotal
0 / 89 engine detections
فتح التقرير“Desktop Browser Required”
mage-glade-44.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 0/89; PhishDestroy score 53/100. مسجّل النطاق: Cloudflare Pages.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
0 / 89 engine detections
فتح التقريرno community references
فتح التقريرNo threat flag
فتح التقريرNo malicious flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mage-glade-44.pages.dev is an impersonation phishing page hosted on a free Cloudflare Pages subdomain. It was built to pass itself off as a trusted service and capture what visitors type into it. PhishDestroy flagged it on 2026-09-13, the same day the subdomain appeared. The site has been offline since 2026-09-20, and its content was still blocked by the hosting provider at our last check on 2026-10-19.
Impersonation pages copy the look of a familiar brand so visitors trust them enough to log in, verify an account or paste wallet recovery words. Anything entered goes straight to the operator, who can then take over the account or empty the wallet. This page displayed the title "Desktop Browser Required," a notice telling visitors to switch devices rather than branded content, while our analysis classified it as impersonation.
Independent detection was essentially absent. When checked on 2026-09-19, none of the 89 VirusTotal engines flagged the page. Among public blocklists, only PhishDestroy listed it. The zero score reflects how quickly the page came and went, not a clean bill of health, and the provider's later block confirms the problem was real.
The subdomain went live and was caught on the same day, 2026-09-13. That fits the throwaway pattern of spinning up a free Pages project, running it briefly and abandoning it. Traffic was served through Cloudflare's network at 188.114.96.9, with the address geolocated to Canada. Its Google Trust Services certificate is the standard one issued automatically to Pages sites, so the padlock showed only that the connection was encrypted and said nothing about who ran the page.
If you entered a username and password, change that password right away, along with any other account that uses the same one, and turn on app-based two-factor authentication. If you typed a seed phrase or private key, treat that wallet as compromised and move your funds to a newly generated wallet you control. Report the incident to the real service the page imitated. Defenders should block the domain and look for similar randomly named Pages subdomains in mail and proxy logs. They should not treat the zero-detection VirusTotal result as evidence that the page was safe.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
690b2d562fc02d3a3bc3ff805d6c28723051330a040d6d1210d95703016ae0bcSaved 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
mage-glade-44.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 sourcemage-glade-44.pages.dev
View sourceListed 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 ↗
mage-glade-44.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.