VirusTotal
11 / 95 engine detections
रिपोर्ट खोलें“Jackpotheim: Most Popular Online Crypto Casino Based on Blockchain”
क्रिप्टो कैसीनो घोटाला: jackpotheim.casino — सामग्री अनुपलब्ध. साक्ष्य सारांश: VirusTotal 11/95 (alphaMountain.ai, BitDefender, CRDF, CyRadar, G-Data)…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
11 / 95 engine detections
रिपोर्ट खोलें100 det.
दुर्भावनापूर्ण
रिपोर्ट खोलेंno community references
रिपोर्ट खोलेंprovider verdict: clean
रिपोर्ट खोलेंNo threat flag
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
On July 24, 2026 the domain jackpotheim.casino was observed to host a fraudulent cryptocurrency casino front. The site presented the page title “Jackpotheim: Most Popular Online Crypto Casino Based on Blockchain”, indicating a direct attempt to lure victims interested in blockchain gambling. The infrastructure was served through Cloudflare, Inc., as shown by the authoritative nameservers mckenzie.ns.cloudflare.com and melnicoff.ns.cloudflare.com and the resolved IP address 104.21.33.234, which belongs to AS13335 (Cloudflare) and is geolocated in the United States. No TLS certificate was detected, meaning the site operated without HTTPS protection, a typical characteristic of hastily deployed phishing kits.
The malicious content matches the publicly known “Gambler Scam” phishing kit, which is frequently used to impersonate online gambling platforms and harvest crypto credentials. VirusTotal analysis recorded 11 positive detections out of 95 scanned engines, reinforcing the malicious classification. Additional reputation services flagged the domain: PhishDestroy listed it as blocked, and a single security blocklist also contains the host. The Gridinsoft trust score was reported as 0 out of 100, indicating an extremely low trust rating.
The domain is currently marked as offline, but the underlying hosting and DNS configuration remain active, allowing rapid re‑activation. Defenders should continue to block the IP 104.21.33.234 at network perimeter, add jackpotheim.casino to URL filtering and sink‑hole lists, and monitor Cloudflare‑associated IP ranges for resurgence. Continuous re‑scanning with multi‑engine services is advised to capture any future changes in detection status.
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.
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
mckenzie.ns.cloudflare.commelnicoff.ns.cloudflare.comLocation describes the IP network.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='jackpotheim.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
jackpotheim.casino
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
अज्ञात→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/f989b805-0bc7-4f98-8edb-025025d072ca
11/95 engine detections
View sourceNo threat flag
View sourcePage captured
View sourcejackpotheim.casino
View source1 समुदाय सदस्य ने रिपोर्ट किया; पहली बार 07/11/2025 को देखा गया
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 ↗
jackpotheim.casino)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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.