Skip to security report
Analytics Dashboard
Domain security report
rollingslots.casino favicon

rollingslots.casino

“Rollingslots: Most Popular Online Crypto Casino Based on Blockchain”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 13/93 Automated brand label: Genericcrypto
Feb 8, 2026 Genericcrypto 1 Report Sent CDN
API
Resolved IP
104.21.41.90
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
13 det.
URLQuery
URLQuery
100 det.
URLScan
URLScan
Report ↗
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

13 / 93

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

100 det.

Observation time not recorded
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
13/93
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Analysis indicates that rollingslots.casino was registered on February 21 2026 and subsequently taken offline. The domain resolves to IP 104.21.41.90, which is owned by Cloudflare (AS13335) and located in the United States. The authoritative name servers are karl.ns.cloudflare.com and vivienne.ns.cloudflare.com, confirming the use of Cloudflare’s DNS infrastructure. No TLS certificate was observed, meaning the site was served without HTTPS encryption. The site’s page title, “Rollingslots: Most Popular Online Crypto Casino Based on Blockchain,” aligns with the listed scam type of a crypto‑related scam.

Infrastructure scans reveal a trust score of 0 out of 100 from Gridinsoft, indicating a highly untrusted profile. Detected front‑end components include React, SweetAlert2, and third‑party CDNs jsDelivr and cdnjs, while the network layer employed HTTP/3 under Cloudflare’s edge. The domain appears on a single security blocklist and has been actively blocked by PhishDestroy. VirusTotal analysis shows that 13 of 93 scanning engines flagged the domain, providing independent confirmation of malicious intent.

The phishing kit associated with the site is identified as the “Gambler Scam” kit, which is commonly used to lure victims into fraudulent cryptocurrency gambling schemes. Given the combination of a newly created domain, lack of TLS, zero trust score, presence on blocklists, detection by multiple AV engines, and association with a known gambling phishing kit, defenders should treat rollingslots.casino as a high‑confidence malicious indicator. Recommended actions include adding the domain and its resolving IP address to network deny lists, enforcing DNS sink‑holing for the associated Cloudflare name servers, and monitoring for any re‑use of the same kit or similar branding in future campaigns. Continuous threat‑intel feeds should be consulted for updates, and any inbound traffic to the domain should be logged and investigated.

Data coverage & collection

19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
13 / 93 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
100 · recorded detections / alertsCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Network & DNS
104.21.41.90 · 2 · nameserversCollection time not recorded
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Response records
1 · outgoing report recordsCollection time not recorded
Availability history
16 · stored state changes
Source observation history
4 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Domain registration
  • TLS certificate
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

104.21.41.90 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Time to First Unavailability 75 days
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.
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.
Technical detailsProvenance & timestamps
First DetectedFeb 8, 2026
DOM Analysisanalyzed Apr 23, 2026score 78/1001 brand signal
Submitted URLhttps://rollingslots.casino/

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.41.90
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • karl.ns.cloudflare.com
  • vivienne.ns.cloudflare.com

Location describes the IP network.

viewdns.info · 104.21.41.90rapiddns.io

Latest Classified Outcome 2026-10-16 20:22:38 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 01:08:56 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-05-11 22:06:13 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-05-11 22:06:13 UTC → 2026-09-30 16:14:55 UTC · 3,402.15h midpoint estimate ≈ 2026-07-21 19:10: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.
Technologies · 6 identified
S
SweetAlert2
C
cdnjs
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 93 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3402.15
Estimate basis
Bounded by observations
Estimate precision
very_low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rollingslots.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionE

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Unreachable

Timeline & response

1 · outbound report records

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.
  1. Cloudflare Radar Scan 2026-03-07 07:44:53 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  2. Cloudflare Radar Scan 2026-03-07 06:02:13 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  3. Domain Status Transition 2026-03-01 05:52:42 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  4. Cloudflare Radar Scan 2026-02-27 22:58:28 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  9. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  11. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/07c4155e-11df-454b-b3e8-05566e45d491

  13. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/4afa94b6-24b2-4171-bfea-ef09de45b690

  14. Availability monitor · Recorded state

    Reachable→Unavailable

  15. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/8e317fa7-2e15-43bc-9967-b51203f9cc73

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
rollingslots.casino detected and queued for full analysis
Feb 8, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Feb 8, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Jul 29, 2026
Cloudflare Radar Report
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 Wayback Machine — historical evidence archived
Mar 14, 2026
VirusTotal
13/93 recorded on VirusTotal
Feb 25, 2026
Brand Impersonation
Impersonation of Genericcrypto
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Feb 8, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 18, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 7, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 7, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Mar 1, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Feb 27, 2026
Initial Abuse Report (#1)
Sent to 1 abuse contact with forensic evidence
abuse@namesilo.com
Feb 26, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Feb 8, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 24, 2026
Time to First Unavailability
1800 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Feb 8, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 13 det. ChainPatrol URLQuery 100 det. SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Content 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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 rollingslots.casino)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: rollingslots.casino

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Rollingslots: Most Popular Online Crypto Casino Based on Blockchain”. Apparent target: Genericcrypto.

VirusTotal detections for rollingslots.casino: 13 (2026-02-25 01:04:57 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/rollingslots.casino"
  title="PhishDestroy threat report for rollingslots.casino"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>