Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
PhishDestroy flags betmore.casino as an active crypto drainer phishing domain designed to trick cryptocurrency users into approving malicious token contracts that drain wallet balances. The domain mimics legitimate crypto-gambling brands to lure victims under the guise of exclusive betting bonuses or promotions. Attack infrastructure points to automated drainer scripts hosted behind a recently registered domain, consistent with fast-flux evasion tactics observed in Q1 2025 campaigns.
Technical indicators confirm elevated risk: the domain resolves to IP 104.21.22.96 and is served over a Let’s Encrypt-issued SSL certificate to lower victim suspicion. Registered on January 06, 2026 through NameSilo, LLC, the domain remains undetected by 95 VirusTotal engines (8/95), has not been marked by Google Safe Browsing, and sits outside all major public blocklists as of present scans. The creation date aligns with a spike in .casino TLD registrations exploited for phishing-as-a-service drainer kits.
Current status is ACTIVE with no takedown initiated; the domain continues to resolve and serve its payload. PhishDestroy recommends immediate network-level blocking of 104.21.22.96 and the domain itself across endpoints and DNS resolvers. Users are advised to revoke any token approvals made via this site and to monitor wallet activity for unauthorized transfers. Remaining risk is high due to zero detections and ongoing accessibility; proactive threat hunting is strongly encouraged.
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
content_divergence
Cloaking score
1/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='betmore.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='betmore.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
checked Oct 11, 2026
Time to First Unavailability18 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 DetectedApr 5, 2026
DOM Analysisanalyzed Jul 29, 2026score 78/1001 brand signal
Submitted URLhttps://betmore.casino/
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:07:58 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-05-22 08:09:02 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-22 08:09:02 UTC → 2026-09-30 16:14:55 UTC · 3,152.10hmidpoint estimate ≈ 2026-07-27 00:11:58 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.
Google PageSpeed Insights — mobile performance audit of betmore.casino· checked Apr 5, 2026
56
Needs Work
Performance
FCP
1.21s
First Contentful Paint
LCP
19.56s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
722ms
Total Blocking Time
SI
2.78s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
betmore.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.
Apr 23, 2026
Time to First Unavailability
442 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.
5 evidence signal groups linked1 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 · betmore.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.
Report 
