VirusTotal
3 / 91
“Jupiter Global — Your onchain spending account”
jupiter.global was first observed on March 2, 2026 and presents a page titled “Jupiter Global — Your onchain spending account”. The site mimics the legitimate Jupiter brand and targets cryptocurrency users, positioning itself as an on‑chain spending account. The domain is registered through Porkbun LLC and resolves to 104.21.10.76, an address owned by Cloudflare (AS13335) located in the United States. DNS resolution is served by ali.ns.cloudflare.com and leonard.ns.cloudflare.com, indicating the use of Cloudflare’s authoritative name servers.
The web server returns HTTP 200 and advertises a modern stack: Vercel front‑end, HTTP/3, HSTS, and Cloudflare Browser Insights. TLS is supplied by a Let’s Encrypt certificate labeled “E7”. No unusual server headers were observed beyond the standard Cloudflare delivery. The presence of Vercel suggests the site may be built on a popular static‑site framework, facilitating rapid deployment of copycat pages.
Threat intelligence flags the domain as high‑risk brand impersonation. VirusTotal recorded a single vendor detection out of 95 scanners, while Gridinsoft assigned a trust score of 0 out of 100. The domain appears on one external blocklist and is actively listed by PhishDestroy. Despite the low number of VirusTotal detections, the combination of a zero trust score, confirmed brand misuse, and a cryptocurrency‑focused lure justifies a high risk rating.
Defenders should immediately block DNS resolution for jupiter.global and add the IP 104.21.10.76 to network deny lists. Continuous monitoring of Cloudflare‑hosted assets for similar brand‑impersonation patterns is advised, as the infrastructure can be replicated with minimal effort. Incident response teams should treat any credential or wallet address submissions to this site as compromised and advise affected users to revoke access and monitor for unauthorized transactions.
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
content_splitcloudflareScanner note: alive_content: raw=ok; http=200; via=https_direct; server=cloudflare
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.
leonard.ns.cloudflare.comLocation describes the IP network.
0efc132162c56801f9dd2f2d4626a54b96dd0cc4effeb4491015b4b6ce3b8dfdSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Reported by 1 community member, first seen Mar 2, 2026
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
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