VirusTotal
5 / 92 engine detections
Open reportva-bank.casino is a crypto casino scam detected by PhishDestroy on 2026-09-06. Risk: critical (88/100). Registrar: NameCheap. Status: Last known active. Hosting: AS-REGRU "Domain names registrar REG.RU", Ltd, RU. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.
“Va-Bank Casino | Official Crypto Casino – Slots & Live Dealers”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
5 / 92 engine detections
Open reportchecked — no detections recorded
Open report4 community references
Open reportprovider verdict: clean
Open report80/100
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
va-bank.casino presents itself as "Va-Bank Casino | Official Crypto Casino – Slots & Live Dealers." It targets players who want to gamble with cryptocurrency. PhishDestroy classifies it as a gambling site flagged as fraudulent and first detected it on 2026-09-06. As of 2026-10-19 the domain was still alive and redirecting visitors, so the operation remains active.
The site matches the Gambler Scam kit, a template for casino fronts that use flashy slot lobbies, live-dealer branding and generous bonuses to attract crypto deposits. Schemes of this type usually let balances grow on screen, sometimes with early small wins. When the player tries to cash out, the site blocks the withdrawal with extra verification, wagering requirements, or demands for a "fee" or "tax" paid up front. Victims lose their original deposit and any further payments made to unlock winnings that never arrive. Crypto transfers are hard to reverse, so these losses are usually permanent.
On 2026-09-20, five of 89 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, but these vendors reached their verdicts independently, and coverage of fraudulent gambling sites usually lags behind coverage of classic phishing. The domain also appears in four AlienVault OTX threat pulses. Among blocklists, PhishDestroy currently lists it.
The domain was registered through NameCheap, Inc. on 2025-09-16, almost a year before PhishDestroy detected it. That long lifespan suggests an established operation rather than a throwaway page. The site is hosted at 83.166.247.135 on the REG.RU network in Russia, which places the infrastructure far from most players' legal recourse.
Do not deposit on va-bank.casino, and never pay a "withdrawal fee," "tax" or "verification deposit" to release a balance, because that money is lost as well. If you have already sent funds, keep the transaction IDs, deposit addresses and chat logs. Report the losses to your local cybercrime authority and to the exchange you sent from, which may be able to flag the receiving addresses. If you handed over ID documents or reused a password on the site, change that password elsewhere and watch for identity misuse. Treat anyone offering to "recover" your funds for a fee as a likely follow-up scam. Defenders should block the domain and its hosting IP, and add the Gambler Scam kit's casino branding to their detection rules.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a074eb-9577-74b9-a12d-26c47f67d286 |
|---|---|
| Final url | https://va-bank.casino/en/ |
| Status | 200 |
| Redirected | same-domain |
| Ip | 83.166.247.135 |
| Ptr | 83-166-247-135.cloudvps.regruhosting.ru |
| Contacted IP addresses | [
"83.166.247.135"
] |
| Asns | [
"197695"
] |
| Countries | [
"RU"
] |
| Tls | {
"san": [
"va-bank.casino"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "va-bank.casino",
"protocol": "TLS 1.3",
"valid_to": "2026-12-04T10:08:34Z",
"valid_from": "2026-09-05T10:08:35Z"
} |
| Domain age days | 2293 |
| Apex age days | 2293 |
| Tls age days | 0 |
| Tls valid days | 89 |
| Requests | 1 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 75,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=utf-8"
} |
Observed: · Retrieved:
| Uuid | db9b069f-3cb9-41ea-a75c-78ba7841c457 |
|---|---|
| Final url | https://va-bank.casino/en/ |
| Status | 200 |
| Redirected | https-only |
| History | [
{
"url": "http://va-bank.casino/",
"status": 307
},
{
"url": "https://va-bank.casino/",
"status": 302
},
{
"url": "https://va-bank.casino/en/",
"status": 200
}
] |
| DOM structure hash | 4cf2f7027093fe4fb1e0cc6f591b62c9065a125c535b011b80cc9ca1d9b44986 |
| Document hash | eda69d2a0f5eec0c53c4fcb7814e3f5957f715fe1abbbfcb8bb295044b7a2bdd |
| Domain risks | [
"CIPA Filter",
"CIPA",
"Gambling"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "va-bank.casino",
"type": "A",
"value": "83.166.247.135"
}
] |
| Dnssec valid | false |
| Ip | 83.166.247.135 |
No. PhishDestroy classifies va-bank.casino as a crypto casino scam (risk: critical, 88/100); it was first detected on 2026-09-06. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on va-bank.casino. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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.
bradley.ns.cloudflare.comdavina.ns.cloudflare.comemx.mail.rupriority 10Location describes the IP network.
3f82f231a83c51ce9005bad2fc1c3e705acebd9c252c1f1f8471afc08d862a34va-bank.casinoSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of va-bank.casino · checked Sep 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
redirected
http_redirect
3→4
2→3
1→2
Reachable
5/92 engine detections
View source4 community references
View sourceNo threat flag
View sourcePD-20260906-F36AC1
va-bank.casino
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
va-bank.casino
PD-20260906-F36AC1 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
va-bank.casino)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.