Analysis of luckwinner.online indicates that the domain was registered through NameCheap, Inc. on February 21, 2026 and presently resolves to the Cloudflare edge address 104.21.76.25, which is associated with ASN 13335 (Cloudflare, Inc.) and geolocated to the United States. The authoritative name servers are kiki.ns.cloudflare.com and valentin.ns.cloudflare.com. No TLS certificate was observed, suggesting that the site was served over plain HTTP or that the certificate was unavailable at the time of collection. The page title returned by the HTTP response reads "Luckwinner: Most Popular Online Crypto Casino Based on Blockchain," and the listed scam type is a crypto‑related scam.
Malware and phishing analyses have linked the infrastructure to a known "Gambler Scam" phishing kit. VirusTotal reports show that 11 of 93 scanning engines flagged the domain, and it appears on one external blocklist. The domain has been taken offline and is currently listed as blocked by the PhishDestroy service.
Evidence confirms the existence of a crypto‑casino lure, but the exact payload, credential‑stealing forms, and victim interaction flow have not been publicly disclosed. Defenders should continue to monitor the IP address 104.21.76.25 for any re‑use in new campaigns, enforce blocklisting of the domain and its associated Cloudflare IP range, and incorporate the observed page title and kit fingerprint into detection rules. Additional scrutiny of traffic to the identified name servers may reveal future iterations of the Gambler Scam infrastructure.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='luckwinner.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
DOM Analysisanalyzed 2026年7月29日score 78/1001 brand signal
Submitted URLhttps://luckwinner.online/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:10:18 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(US)
