Analysis of winro.casino, observed on July 23, 2026, indicates that the domain was taken offline but previously hosted a fraudulent cryptocurrency casino front. The site was served through Cloudflare, Inc., as evidenced by the registrar entry and the use of Cloudflare’s nameservers ada.ns.cloudflare.com and karl.ns.cloudflare.com. SSL termination was provided by Google Trust Services under the WE1 certificate, confirming that the site presented a valid HTTPS certificate despite its malicious intent.
Network resolution pointed to IP address 104.21.13.62, an address owned by AS13335 Cloudflare, Inc. in the United States, which is typical for shared infrastructure and obscures the underlying hosting server. VirusTotal scans recorded 13 detections out of 95 security vendors, demonstrating a consensus among multiple antivirus engines that the domain delivered malicious content. The domain appears on a single security blocklist and was specifically blocked by the PhishDestroy service, reinforcing its classification as a phishing threat.
Threat intelligence identified the underlying phishing kit as the Gambler Scam, a known template used to lure victims with promises of crypto gambling and financial gain. The scam type is cataloged as a crypto scam, aligning with the page title "Winro: Most Popular Online Crypto Casino Based on Blockchain." While the site is currently offline, defenders should assume the infrastructure could be reactivated or cloned, and therefore proactively add winro.casino to internal blocklists, monitor DNS queries for any future resolution changes, and enforce outbound filtering of connections to Cloudflare‑hosted IP ranges associated with this domain. Continuous monitoring of threat feeds for re‑appearance of the domain or related indicators, such as the Gambler Scam kit signatures, is recommended to mitigate potential resurgence.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='winro.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
Minimum notice count8 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
ICANN RAA §3.18
The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
Technical detailsProvenance & timestamps
First DetectedNov 15, 2025
DOM Analysisanalyzed Jul 29, 2026score 78/100
Submitted URLhttps://winro.casino/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:10:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-02-14 16:36:13 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-02-14 16:36:13 UTC → 2026-09-30 16:14:55 UTC · 5,471.65hmidpoint estimate ≈ 2026-06-08 16:25:34 UTC · precision very low · basis bounded
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.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
View Archive Abuse Report Escalation History · 8 reports over 57 days · click to expand
PhishDestroy does not flood registrars.
Follow-up reports are sent only when one of the following is true: a user-initiated re-report was submitted via our public form, our monitoring detected the domain resurfacing in a search engine result or third-party feed, or our live-checker confirmed the domain remains technically active and still exhibits fraudulent behaviour. Each escalation below represents an independent trigger — not automated noise.
8 abuse reports filed over 222 days — eventually taken down
Cloudflare, Inc. was notified 8 times before the domain was removed. ICANN Compliance was CC’d on at least one escalation — receipt of each complaint is therefore on the record.
8
reports
222
days
ICANN CC
Report #1Mar 3, 2026 · 02:05 UTC
Phishing Abuse Report: winro[.]casino
abuse@namecheap.com
Report #2ICANN CC37h still activeMar 4, 2026 · 15:19 UTC
ICANN RAA §3.18 requires accredited registrars to publish an abuse point-of-contact and take reasonable and prompt steps in response to reports of illegal activity. The timeline above documents delivered reports — registrar acknowledgement and takedown timing are independently verifiable via the archived email threads on request.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
21 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
winro.casino detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 2, 2026
Time to First Unavailability
2558 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked8 reports recordedContent unavailable
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · winro.casino
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
