VirusTotal
5 / 91 engine detections
Open reportstakewise.uk is a gambling scam detected by PhishDestroy on 2026-09-19. Risk: critical (100/100). Registrar: Dynadot. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 5/91 engines flag it. Do not enter credentials or connect a wallet.
“StakeWise Casino ™ - Official Online Casino”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.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 / 91 engine detections
Open report1 threat-system alert
Open reportMalicious
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | stakewise.uk |
phishing | Phishing Block |
PhishDestroy threat report
stakewise.uk presents itself as "StakeWise Casino ™ - Official Online Casino" and is aimed at online gamblers, particularly those who play with crypto. PhishDestroy classifies it as a credential phishing page and first saw it on 2026-09-19. As of 2026-10-19 the site was still live and reachable. The page title shows a casino storefront, while our classification is credential phishing.
Phishing sites of this kind use a polished casino front with sign-up bonuses and an "official" label to get visitors to register or log in. Whatever goes into those forms, including email addresses, passwords and sometimes account or wallet details, goes straight to the operators. Stolen logins are then tried on other gambling, exchange and email accounts, so reusing one password across sites turns a single phishing visit into several account takeovers.
On 2026-10-03, five of 91 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That count is low, so most scanners still let the site through. urlscan.io rated the page malicious and recognised generic gambling branding. MetaMask's and SEAL's blocklists both carry it alongside PhishDestroy, and it appears in three AlienVault OTX threat pulses.
The domain was registered through Dynadot on 2026-04-15, about five months before PhishDestroy detected it. Because it had time to sit quietly before being flagged, newly found gambling domains like this should not be trusted just because they look established. Traffic goes through Cloudflare's network, with the visible address geolocated to Canada. This means the real origin server is hidden behind the proxy.
If you created an account or logged in on stakewise.uk, change that password right away, along with the password on every other site where you used the same one. Turn on two-factor authentication, starting with your email, exchange and gambling accounts. Do not deposit funds or follow "verification" requests from this site, and watch for follow-up phishing sent to the email address you used. Security teams should block the domain at DNS and proxy level, check logs for users who submitted forms to it, and reset credentials for anyone affected.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0b88a-f278-7264-a798-3c09a9f3f6fa |
|---|---|
| Final url | https://stakewise.uk/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://stakewise.uk/",
"from": "http://stakewise.uk/",
"status": 307
}
] |
| Ip | 172.67.149.179 |
| Contacted IP addresses | [
"172.67.149.179"
] |
| Asns | [
"13335"
] |
| Document hash | b93fa2a2a99566fafa8e1f8fb6726d310dfbb94768cd7d7fac2899bb72b49107 |
| Script hashes | [
"2595496fe48df6fcf9b1bc57c29a744c121eb4dd11566466bc13d2e52e6bbcc8",
"ef57ec383ef089d0c60948fa013bf9e01b3df6bf2e74f6695ca30ddbb3d1a9ef",
"1762dd6a64fcd59421610b68625258f9224a1f278159c4d99282adb631470465"
] |
| Globals | [
"_paq",
"Piwik",
"Matomo",
"AnalyticsTracker",
"piwik_log"
] |
| Cookies | [
"rtc",
"_pk_id.1243.3a47",
"_pk_ses.1243.3a47"
] |
| Tls | {
"san": [
"*.stakewise.uk",
"stakewise.uk"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "stakewise.uk",
"protocol": "QUIC",
"valid_to": "2026-11-09T07:38:29Z",
"valid_from": "2026-08-11T07:38:30Z"
} |
| Domain age days | 156 |
| Apex age days | 156 |
| Tls age days | 38 |
| Tls valid days | 89 |
| Requests | 124 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 93,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"genericgambling"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Generic Gambling"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8"
} |
Observed: · Retrieved:
| Uuid | 48e8ba63-2672-4a5d-a3ee-57c21f4e2e83 |
|---|---|
| Final url | https://stakewise.uk/ |
| Status | 200 |
| History | [
{
"url": "https://stakewise.uk/",
"status": 200
}
] |
| DOM structure hash | 935f910785cf0f4eadf83435cb7dfbf89c571d5f7ebf64b2bdfb458a2a9a499d |
| Document hash | 79624f7d69b4b65e5cdbcfc3f006d8852041ad47c9da69786d99f94e719d8e7b |
| Domain risks | [
"Gaming",
"Entertainment",
"CIPA Filter",
"CIPA",
"Gambling"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "stakewise.uk",
"type": "A",
"value": "104.21.71.220"
},
{
"name": "stakewise.uk",
"type": "A",
"value": "172.67.149.179"
},
{
"name": "stakewise.uk",
"type": "AAAA",
"value": "2606:4700:3035::ac43:95b3"
},
{
"name": "stakewise.uk",
"type": "AAAA",
"value": "2606:4700:3034::6815:47dc"
}
] |
| Dnssec valid | false |
| Ip | 104.21.71.220 |
| Registration record | {
"registrar": "Dynadot, LLC t/a Dynadot",
"created": "2026-04-15T08:18:46Z",
"updated": "2026-04-15T09:45:43Z",
"expires": "2027-04-15T08:18:46Z",
"nameservers": [
"lennon.ns.cloudflare.com.",
"stephane.ns.cloudflare.com."
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 0,
"suspicious": 1,
"undetected": 36
} |
|---|---|
| Vendor labels | {
"Gridinsoft": "suspicious"
} |
| Reputation | 0 |
| Created | 2026-04-15T00:00:00Z |
| Updated | 2026-04-15T00:00:00Z |
| First seen | 2026-04-15T10:07:18Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "stephane.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "lennon.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "TXT",
"value": "google-site-verification=eHaZlOgPiHMA-T_LJJ_Yi-WsJiFLjU2qldFqgvd-D68"
},
{
"ttl": 300,
"type": "MX",
"value": "route1.mx.cloudflare.net",
"priority": 19
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3034::6815:47dc"
},
{
"ttl": 300,
"type": "TXT",
"value": "v=spf1 include:_spf.mx.cloudflare.net ~all"
},
{
"ttl": 300,
"type": "MX",
"value": "route2.mx.cloudflare.net",
"priority": 63
},
{
"ttl": 300,
"type": "A",
"value": "104.21.71.220"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3035::ac43:95b3"
},
{
"ttl": 300,
"type": "MX",
"value": "route3.mx.cloudflare.net",
"priority": 20
},
{
"ttl": 300,
"type": "A",
"value": "172.67.149.179"
},
{
"ttl": 21600,
"type": "NS",
"value": "lennon.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-21T11:14:03Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.stakewise.uk",
"stakewise.uk"
],
"issuer": "Let's Encrypt / YE2",
"serial": "5f5b96beccbda22d276f5450bbe27e4f7bc",
"sha256": "476253cc7bd1c4e2be05140d6efebb7592f91a8789f051b3515a8dacd97ad662",
"subject": "stakewise.uk",
"valid_to": "2027-01-07T06:57:09Z",
"valid_from": "2026-10-09T06:57:10Z"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"expiration": "2027-04-15T08:18:46Z",
"last changed": "2026-04-15T09:45:43Z",
"registration": "2026-04-15T08:18:46Z",
"last update of RDAP database": "2026-07-19T23:08:52Z"
},
"registrar": "Dynadot, LLC t/a Dynadot",
"registrar_iana_id": "DYNADOT"
} |
No. PhishDestroy classifies stakewise.uk as a gambling scam (risk: critical, 100/100); it was first detected on 2026-09-19. VirusTotal: 5/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on stakewise.uk. 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.
Last checked
Edge-IP reputation is not attributed to this domain.
lennon.ns.cloudflare.comstephane.ns.cloudflare.comroute1.mx.cloudflare.netpriority 19route3.mx.cloudflare.netpriority 20route2.mx.cloudflare.netpriority 63Location describes the IP network.
476253cc7bd1c4e2be05140d6efebb7592f91a8789f051b3515a8dacd97ad662*.stakewise.ukstakewise.ukSaved 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 stakewise.uk · checked Sep 19, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
stakewise.uk
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
0→1
3 community references
View source5/91 engine detections
View sourceNo threat flag
View sourcePD-20260919-E99F20
Page captured
View sourcestakewise.uk
View sourcePD-20260919-E99F20 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains 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 ↗
stakewise.uk)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.