api.jxlpayments.online is a Visa impersonation page detected by PhishDestroy on 2026-10-24. Risk: high (68/100). Registrar: Spaceship. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.
Back To The Future Payment Phish — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy’s intake system classified the site as malicious because an AI analysis identified a payment form that requests full credit‑card details and appears unrelated to the advertised “Back To The Future” event. The domain was first seen by PhishDestroy on 2026-10-24 and returned an HTTP 200 response at that time.
How the scam works
The scheme presents a fake ticket‑sale or payment page that mimics a legitimate event and prompts victims to enter complete credit‑card information. The harvested card data can then be used for unauthorized transactions or sold to other fraud actors.
Evidence
VirusTotal scanned the domain on 2026-10-24 (analysis date 2026-10-20) with 92 engines and reported 0 malicious and 0 suspicious detections. Google Safe Browsing checked the URL on 2026-10-24 and did not flag it, and OTX listed no pulses as of that date. urlscan.io captured the page on 2026-10-24, where its machine‑learning engine assigned a malicious score of 96 and tagged it as phishing, while the overall verdict remained neutral; Cloudflare Radar also labeled the site as phishing on the same day. PhishDestroy’s internal blocklist includes the domain as of 2026-10-24.
Infrastructure
The recorded DNS records on 2026-10-24 listed A records 188.114.96.3 and 188.114.97.3 (and corresponding AAAA records) served via Cloudflare’s network. The TLS certificate observed on that date was issued by Let’s Encrypt for *.jxlpayments.online, valid from 2026-10-14 to 2027-01-12. The apex domain was eight days old when captured.
What to do
Anyone who entered credit‑card data should contact their card issuer immediately and monitor for unauthorized activity. Defenders should block api.jxlpayments.online at firewalls or proxies and review logs for connections to the recorded IP addresses.
No. PhishDestroy classifies api.jxlpayments.online as a Visa impersonation page (risk: high, 68/100); it was first detected on 2026-10-24. Treat the site as unsafe.
Is api.jxlpayments.online safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on api.jxlpayments.online. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used api.jxlpayments.online?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
For the registrable domain jxlpayments.online behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Accountability draft Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Washington, US
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
bonnie.ns.cloudflare.com
rory.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-14 09:31:14
Valid until
2027-01-12 09:31:13
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7fce6a20d382beb50727a33a57483b4c13a8f68937dce371c8f7707bcc6867e0Certificate names · 2 SANs
*.jxlpayments.online
jxlpayments.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including api.jxlpayments.online)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
(US) 
