Security engines reporting a detection: 13. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Report overview
On July 23 2026 the domain wingo.casino was observed hosting a fraudulent crypto‑casino page titled “Wingo: Most Popular Online Crypto Casino Based on Blockchai
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
On July 23 2026 the domain wingo.casino was observed hosting a fraudulent crypto‑casino page titled “Wingo: Most Popular Online Crypto Casino Based on Blockchain”. Infrastructure analysis shows the domain resolves to the Cloudflare edge address 172.67.169.241, advertised under AS13335 Cloudflare, Inc. and located in the United States. Registration is handled through Cloudflare, Inc. with authoritative nameservers bart.ns.cloudflare.com and fay.ns.cloudflare.com, indicating the use of Cloudflare’s DNS and proxy services. The site presented an HTTPS certificate issued by Google Trust Services (WE1), confirming the presence of a valid TLS certificate despite the malicious intent. Threat intelligence flags the domain on three independent security blocklists and it is actively blocked by PhishDestroy, MetaMask and SEAL.
VirusTotal scans returned 15 positive detections out of 95 vendors, and the Gridinsoft trust score is 1 / 100, reflecting a highly suspicious reputation. AlienVault OTX references the domain in a single threat‑intel pulse, further corroborating its malicious nature. The HTTP response code reported was 666, an uncommon status that may be employed to evade standard monitoring. The observed phishing kit matches the “Gambler Scam” profile, and the campaign is classified as a crypto‑scam targeting users seeking cryptocurrency gambling services.
Current operational status is offline, which may be temporary or the result of takedown actions. Uncertainty remains regarding the exact victim interaction flow, as the page content has not been publicly archived. Defenders should continue to block the domain at network perimeter and DNS layers, monitor for re‑registration or use of sibling domains, and update endpoint protection signatures to include the observed IP address and associated SSL fingerprint. Ongoing collection of any new indicators, such as URL patterns or payload hashes, is recommended to maintain coverage against potential re‑emergence.
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='wingo.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 count11 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 1, 2025
DOM Analysisanalyzed Jul 28, 2026score 100/1001 brand signal
Submitted URLhttps://wingo.casino/
Favicon Hash
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:31:10 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-19 02:20:04 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-19 02:20:04 UTC → 2026-09-30 16:14:55 UTC · 277.91hmidpoint estimate ≈ 2026-09-24 21:17:29 UTC · precision 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 · 11 reports over 195 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.
11 abuse reports filed over 227 days — eventually taken down
Cloudflare, Inc. was notified 11 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.
11
reports
227
days
ICANN CC
Report #1Feb 26, 2026 · 19:00 UTC
Phishing Abuse Report: wingo[.]casino
abuse@spaceship.com
Report #2ICANN CC103h still activeMar 3, 2026 · 02:04 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.
31 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
wingo.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.
Jun 6, 2026
Time to First Unavailability
1302 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.
7 evidence signal groups linked11 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 · wingo.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.
Content matches4
Same favicon hash or the same page title as this host.
Gridinsoft Analysis
1 / 100
(US)
