VirusTotal
1 / 89 engine detections
فتح التقرير“Desktop Browser Required”
نطاق في قوائم الحظر: bridge-kind-52.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 1/89 (URLQuery); PhishDestroy score…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
1 / 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
bridge-kind-52.pages.dev was an impersonation phishing page hosted on a free Cloudflare Pages subdomain. Visitors were shown a screen titled "Desktop Browser Required." PhishDestroy flagged it on 2026-09-13, the same day the subdomain was created. The site has been offline since 2026-09-20, and the hosting provider has blocked its content. It was still down when last checked on 2026-10-19.
Impersonation pages copy the look of a trusted service so visitors will type in logins or recovery phrases, or approve actions they would otherwise refuse. A "Desktop Browser Required" screen is a common gate in these setups. It pushes people off phones and onto desktop browsers, where wallet extensions and saved sessions are available to target. The title shows a device check rather than a branded login, while our classification is impersonation. Anyone who continued past the gate risked handing over credentials or wallet secrets to whoever ran the page.
Independent detection was thin. When VirusTotal checked the site on 2026-09-19, only URLQuery flagged it, out of 89 engines. PhishDestroy is the only blocklist carrying it. That pattern fits a page that lived for about a week, too short for most vendors to catch it. Low vendor coverage here reflects the site's brief lifespan, not evidence that it was safe.
The subdomain was created on 2026-09-13 and detected that same day, so it was a fresh, throwaway deployment rather than an aged domain. It ran on Cloudflare Pages behind Cloudflare, Inc. network space geolocated to Canada. The free pages.dev hostname gave the operator a working HTTPS address with no registration cost. The provider's content block confirms the deployment was disabled at the platform level.
If you entered a password on this page, change it right away, starting with any account that reuses it. Then enable app-based 2FA and sign out of other active sessions. If you typed a seed or recovery phrase, consider that wallet compromised and move any remaining funds to a newly created wallet. Watch for follow-up messages that cite this site or pretend to be support staff offering recovery help. Defenders should block the pages.dev subdomain, watch for sibling Cloudflare Pages deployments with similar random names, and treat "Desktop Browser Required" gates as a phishing indicator.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
08024a341df4466a787fec473e55f122f1472c00f0ecba326e5d279f8ae328c3Saved 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
bridge-kind-52.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 source1/89 engine detections
View sourcebridge-kind-52.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 ↗
bridge-kind-52.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.