VirusTotal
0 / 89 engine detections
فتح التقرير“Desktop Browser Required”
melt-moor-24.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
melt-moor-24.pages.dev is an impersonation phishing page hosted on a free Cloudflare Pages subdomain. PhishDestroy flagged it on 2026-09-13, the same day the subdomain was created. The site went offline on 2026-09-20 after the provider blocked its content, and it was still dead when last checked on 2026-10-19.
Impersonation pages copy the look of a trusted crypto service so visitors believe they are on the real site. They then hand over account credentials, recovery phrases or wallet access, which the operators use to take over accounts and empty funds. The page title, "Desktop Browser Required," displays a browser-compatibility notice rather than a recognizable brand, while PhishDestroy classified the site as impersonation phishing. A message like this can push a visitor to reopen the link on a computer before the rest of the scheme continues.
Independent scanners did not catch this one. VirusTotal returned 0 detections out of 89 engines on 2026-09-19, and PhishDestroy is the only blocklist that lists it. A clean VirusTotal result does not mean the site is safe, because new throwaway subdomains often go unnoticed by these engines. The provider's decision to block the content is further confirmation that something was wrong with it.
The subdomain was created and detected on 2026-09-13 and taken down a week later. That short life is typical of disposable phishing pages that run for a few days and are then abandoned. It sat on Cloudflare Pages, resolved to Cloudflare, Inc. network space geolocated to Canada, and used an automatically issued Google Trust Services certificate. The padlock in the browser therefore showed only an encrypted connection and said nothing about who ran the page.
If you typed a password into this page, change it on the real service and on any account that uses the same password, then turn on app-based 2FA. If you entered a seed phrase or private key, treat that wallet as compromised and move any remaining assets to a newly created wallet right away. Report any losses to the genuine service and keep screenshots or browser history as evidence. Defenders should block the domain, search proxy and DNS logs for visits between 2026-09-13 and 2026-09-20, and alert on newly created pages.dev subdomains whose titles push users to switch devices or browsers.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
b12811bc1334c5636fd03d28ee0198bbfa0d558bf8b59fd18aa39ef841697cbeSaved 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
melt-moor-24.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 sourcemelt-moor-24.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 ↗
melt-moor-24.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.