VirusTotal
9 / 92 engine detections
レポートを開く“Ruqvexa”
Aaveなりすまし: ruqvexc.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 92 engine detections
レポートを開く悪意あり
レポートを開く4 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
ruqvexc.com is an impersonation phishing page that presents itself as Ruqvexa, the name shown in its page title. The domain is one letter off from that name, a common way to catch users who mistype an address or click a lookalike link. PhishDestroy first flagged it on 2026-10-16, four days after registration. As of 2026-10-19 the site was still online and serving its phishing content.
Impersonation pages copy the look and wording of a real service so visitors believe they are on the genuine site. Victims usually arrive through ads, social media posts, direct messages or search results. The cloned interface then asks them to sign in, verify an account or connect a wallet. Anything entered, such as passwords, recovery phrases or private keys, goes straight to the operators, who can then take over accounts and empty wallets.
PhishDestroy, MetaMask and SEAL all list the domain, three independent blocklists from the crypto security community. It also appears in 4 AlienVault OTX threat pulses. A VirusTotal scan on 2026-10-16 returned 0 detections from 92 engines, so standard antivirus engines had not yet caught it. That gap is common for newly registered phishing domains, and a clean VirusTotal result should not be read as a sign the site is safe.
The domain was registered on 2026-10-12 through Cloudflare, Inc. It resolves to 188.114.97.3 on AS13335 (Cloudflare, Inc.) in the US, which places the true origin server behind Cloudflare's proxy. Its TLS certificate was issued by Let's Encrypt (YE1), so the padlock in the browser only means the connection is encrypted. It says nothing about whether the site is legitimate.
Do not enter any credentials or wallet details on ruqvexc.com, and reach the real service only through a bookmarked or independently verified address. If you typed a password there, change it right away wherever you used it and turn on two-factor authentication. If you entered a seed phrase or private key, treat that wallet as compromised and move your funds to a newly created wallet immediately. Defenders should block the domain at DNS and web proxy layers, add it to mail and chat filters, and report it to Cloudflare's abuse channels.
Last checked
Edge-IP の評判はこのドメインに起因しません。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
5f071167d499a57d29aa5cd5d3f18b118176363d6cdf7570034c0da6d72bff75Saved 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.
down.ruqvexc.comDomain recordwww.ruqvexc.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of ruqvexc.com · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://ruqvexc.com/https://ruqvexc.com/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4b3775bf9eb9867-EWRkeep-alivegziptext/htmlFri, 16 Oct 2026 01:59:47 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=jAY04zOLNNYXOg%2FtrXLzspIPsgXqqLyYz1rggPccNRHUi6k1oOdf9yOnF%2BCE6r3pQfav0LkuRHCTGvGKUox9aFswmXZ%2BvW0oIEXRdhW8AUWpq6JeAZC1PWUF1zGIvQ%3D%3D"}]}cloudflarecfCacheStatus;desc="DYNAMIC"max-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
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
到達可能
No threat flag
View source9/92 engine detections
View source4 community references
View sourceruqvexc.com
View sourcePage captured
View source保存された類似ドメイン:95 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ruqvexc.com
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 ↗
ruqvexc.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.