VirusTotal
5 / 91 engine detections
Open report“Rusk Inu: Dashboard | VRFD”
5 / 91 engine detections
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, jupiter-verify.exchange, is currently under investigation for brand impersonation targeting Jupiter, a decentralized finance platform. Analysis indicates the site presents itself as a legitimate Jupiter service but displays anomalous content, including a page title labeled "Rusk Inu: Dashboard | VRFD," which does not align with the purported brand. The domain is active and may be part of a broader campaign to deceive users into interacting with fraudulent infrastructure. Infrastructure analysis reveals the domain was registered on July 07, 2026, through Dynadot Inc, a registrar commonly associated with malicious activity. It resolves to the IP address 188.114.97.3, which is linked to Cloudflare’s network. The site employs Node.js, Vue.js, and Nuxt.js for its frontend and backend, alongside Cloudflare Browser Insights for performance monitoring. Despite its active status, the domain has not been flagged by any of the 95 vendors on VirusTotal as of the latest scan. No blocklist entries or trust score degradations were observed, though this may reflect the domain’s recent registration and limited exposure. Given the discrepancy between the domain’s branding and its actual content, coupled with the use of Cloudflare to obfuscate hosting details, users and organizations are advised to treat jupiter-verify.exchange as high-risk. Immediate actions should include blocking the domain at the network level, monitoring for related indicators of compromise (IOCs) such as the IP address 188.114.97.3, and alerting security teams to potential phishing campaigns leveraging Jupiter’s brand. Further investigation into the domain’s traffic patterns and associated wallet addresses is recommended to assess its role in crypto-draining or credential-harvesting operations.
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 reputation is not attributed to this domain.
may.ns.cloudflare.comsevki.ns.cloudflare.comLocation describes the IP network.
fb03bc5e34b5f35f5f4412f2cd985a488346c17f0e82cdad7df8a7fc90ab3659Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of jupiter-verify.exchange · checked Jul 7, 2026
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.
content_divergence · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='jupiter-verify.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnect
jupiter-verify.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
Unavailable→Reachable
Reachable→Unavailable
Unavailable→Reachable
Reachable→Unavailable
5/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcejupiter-verify.exchange
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
jupiter-verify.exchange)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.