Google Safe Browsing
No threat flag
Not on Google threat lists at check time
“Ruqvexa”
No threat flag
Not on Google threat lists at check time
No malicious flag
Browser scan with screenshot
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 104.21.47.95
Each check shows its own collection time. Zero detections do not guarantee safety.
انتحال MetaMask: ruqvexa.app — آخر نشاط معروف (HTTP 200). ملخص الأدلة: VirusTotal 10/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
10 / 91 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
ruqvexa.app is an impersonation phishing page that presents itself under the name "Ruqvexa". MetaMask and SEAL both list it, which places it among threats to crypto wallet users. PhishDestroy first detected it on 2026-09-29. As of 2026-10-19 the site was still online and serving its phishing content.
Impersonation sites like this copy the look and language of a legitimate crypto service so visitors trust them enough to act. The page carries only its own invented name, "Ruqvexa", rather than a recognizable brand. Its purpose matches our impersonation classification: it gets visitors to hand over something valuable. On sites in this category, that usually means connecting a wallet and signing a transaction or token approval, typing in a recovery phrase, or entering login details. Any of these can give the operators control of the victim's funds or accounts.
On 2026-10-01, 10 of 91 VirusTotal engines flagged the domain. Those vendors were alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a minority of engines, but several of them are mainstream security products, so many users are already warned. Wallet-side protection matters most here. MetaMask's blocklist and SEAL both include the domain alongside PhishDestroy, so MetaMask users should see a warning before the page loads.
The domain was registered on 2026-08-25 through CloudFlare, Inc. That is roughly five weeks before PhishDestroy flagged it, a short gap typical of disposable scam domains. Traffic passes through Cloudflare's network, with the address geolocated to Canada, so the real origin server is hidden behind the proxy. The certificate from Google Trust Services is a free, automatically issued one. The padlock in the browser therefore says nothing about whether the site is legitimate.
If you connected a wallet to ruqvexa.app, review and revoke any token approvals or permissions granted during that visit using a trusted approval-management tool. Move remaining assets if you signed anything you did not fully understand. If you typed in a recovery phrase, treat that wallet as compromised and transfer funds to a new wallet with a fresh phrase right away. If you entered a password, change it wherever you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level and check logs for users who reached it.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
2dcf5f496c80a602b1305468e700387e3d70d0e1f260b63a7f10e640d3076ee9Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.ruqvexa.appDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of ruqvexa.app · checked Sep 29, 2026
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.
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
No threat flag
View source10/91 engine detections
View sourcePage captured
View sourceruqvexa.app
View source٧٩ نطاقًا متشابهًا محفوظًا
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ruqvexa.app
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 ↗
ruqvexa.app)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.