Skip to security report
Domain security report
betio.casino favicon

betio.casino

“BETIO | Enter the world of sport and stakes!”

Threat verdict
Assessment sources

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

Availability Unverified Current reachability is unverified Observed · HTTP probe
VirusTotal detections: 2/89 Automated brand label: Ethereum
OTX: 23 refs Nov 20, 2025 Ethereum CDN
API
Registrar
SD-onenetwork (ASN: 16…
Resolved IP
57.129.97.29
Registered
Aug 23, 2025
2 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
2 det.
OTX references
URLScan
URLScan
ScamAdviser
Scamadviser
55/100Caution Recommended
TLS Certificate
Within stored validity dates
XUI.one · Hostname coverage not recorded
Age
1.2 yr
PhishDestroy
DestroyList
Listed

Source evidence

9 · 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

2 / 89

Report
Interpretation & limits

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

URLScan verdict

malicious

Report
Interpretation & limits

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

OTX

23 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.

DNS blocks

14 checked — no blocks

Observation time not recorded
Interpretation & limits

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

Scamadviser

55/100

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.

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.

Security Signals
SA Scamadviser Warnings 55/100
According to Tranco this site has a low rank High number of suspicious websites on this server We tried to analyze the content of the site but failed

Evidence Summary

Critical
VirusTotal
2/89
OTX
23 community refs
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.

This domain was identified as an elevated-risk threat. Specifically, betio.casino is a brand impersonation of ethereum, designed to trick users into believing they are interacting with a legitimate crypto platform. The page title 'BETIO | Enter the world of sport and stakes!' suggests a gambling or betting theme, which is a common lure for crypto drainer attacks. The domain is currently offline, but the infrastructure behind it remains a concern.

Technical indicators paint a clear picture. VirusTotal shows 1 out of 95 security vendors flagging the domain, with the domain appearing on one security blocklist. It was registered through SD-onenetwork (ASN 16276) and resolved to IP address 57.129.97.29. An SSL certificate issued to XUI.one was associated with the domain. While the domain is now inactive, its past presence on blocklists and vendor flags indicates malicious intent.

Users should avoid any interaction with betio.casino or its purported services. Since this is a crypto drainer targeting ethereum users, never connect a wallet or enter private keys on such sites. Always verify the authenticity of crypto platforms through official channels and use tools like PhishDestroy to check domain safety. If you have already interacted with this domain, monitor your wallet for unauthorized transactions and consider revoking any approvals granted.

Data coverage & collection

22 · datasets with records / 9 · 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
2 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
23 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
DNS security filters
0 / 14 · provider blocksCollection time not recorded
Scamadviser
55/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
SD-onenetwork (ASN: 16276)Collection time not recorded
Network & DNS
57.129.97.29 · 2 · nameserversCollection time not recorded
TLS certificate
XUI.one
Page captures
2 · retained captures
Page analysis
2 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Availability history
30 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
52 · retained relationshipsCollection time not recorded
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

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

  • URLQuery
  • PhishStats
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

SD-onenetwork (ASN: 16276) · 57.129.97.29 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context CDN shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2025-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar SD-onenetwork (ASN: 16…
Abuse contactabuse@ovh.net
RegistrationCreated Aug 23, 2025 — Expires Aug 23, 2026
Technical detailsProvenance & timestamps
First DetectedNov 20, 2025
DOM Analysisanalyzed Mar 11, 2026score 81/1002 brand signals
Submitted URLhttps://betio.casino/
Favicon Hash
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
57.129.97.29
Network ASN
AS16276
Organization
OVH SAS
Observed location
Frankfurt am Main, DE
Server header
wd

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • harlee.ns.cloudflare.com
  • lochlan.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
XUI.one
Valid from
2021-03-07 19:39:47
Valid until
2031-03-05 19:39:47
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-03-11 12:49:21 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd21ce91a1b81ec094d23bbcf1696dd47eeeb42cae5f9741dc3c57b2e1e9e8e66

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-18 08:21:15 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-18 10:12:58 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-02 10:22:57 UTC last content: 2026-10-02 10:22:57 UTC current episode first observed: 2026-10-02 16:16:28 UTC observed RIP window: 2026-10-02 10:22:57 UTC → 2026-10-02 16:16:28 UTC · 5.89h midpoint estimate ≈ 2026-10-02 13:19:42 UTC · precision high · 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
Chong Lua Dao
Gridinsoft

Archived Evidence

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

Availability observations

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

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 yet scanned No 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='betio.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S

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

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

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-06 23:37:29 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
Stored observation history31

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 26
  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

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  13. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  14. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  15. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  16. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  17. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  18. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  19. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  20. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  21. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. Availability monitor · Recorded state

    audit_replace→https://radar.cloudflare.com/scan/39895cd6-17e9-428f-8d9d-6b640eb9bf0d

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
betio.casino detected and queued for full analysis
Nov 20, 2025
URLScan.io Capture
Stored URLScan report with capture artifacts
Feb 28, 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
2/89 recorded on VirusTotal
Sep 19, 2026
OTX Community References
23 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Sep 28, 2026
Brand Impersonation
Impersonation of Ethereum
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Feb 28, 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
DestroyList Published
Nov 20, 2025
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.

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

52 stored lookalike domains

ethercum.org homoglyph Internal report etheruem.org transposition Internal report athereum.org bitsquatting dethereum.org insertion e.thereum.org subdomain efhereum.org replacement ehereum.org omission etereum.org omission eth3reum.org replacement ether.eum.org subdomain etheream.org vowel-swap ethereim.org replacement
Show all (40)
ethereium.org insertion etherem.org omission etheremu.org transposition ethereom.org vowel-swap etheresum.org insertion ethereujm.org insertion ethereum2.org addition ethereum3.org addition ethereum4.org addition ethereumc.org addition ethereumd.org addition ethereumorg.com various ethereumr.org addition ethereums.org addition ethereumx.org addition ethereun.org homoglyph ethereunm.org homoglyph ethereurm.org homoglyph ethereurn.org homoglyph ethereuym.org insertion ethereuzm.org insertion ethereyum.org insertion etherium.org vowel-swap etherrum.org replacement etherteum.org insertion etherum.org omission ethezeum.org bitsquatting ethireum.org vowel-swap ethnereum.org insertion ethreum.org omission ethureum.org bitsquatting etihereum.org homoglyph ithereum.org vowel-swap othereum.org vowel-swap rethereum.org insertion sethereum.org insertion thereum.org omission uthereum.org bitsquatting zethereum.org insertion zthereum.org replacement

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Nov 20, 2025

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 0 stored notification records Unverified

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes
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 betio.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

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: betio.casino

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “BETIO | Enter the world of sport and stakes!”. Apparent target: Ethereum.

VirusTotal detections for betio.casino: 2 (2026-09-19 02:28:19 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.

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/betio.casino"
  title="PhishDestroy threat report for betio.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>