Editorial mirrorBrand mentions redacted to public IDs. Hover to inspect. Everything else is theatre.How it works
THE ENABLERS REGISTRYRegistrar accountability archive
Archive LiveRead-only public record · No ads · No tracking
Cracked crypto wallet with classified breach data and surveillance feed overlay.
Domain dossier / preserved indicators

Redacted domain dossier, minus the house style

We are far too editorially nervous to tell you whether the upstream publisher is correct. We can, however, preserve the dossier, keep the indicators readable, and route every external exit through the source gate.

Domain fileIndicators preservedSource gate wrapped
File /domain/d1-qTi7Yzi7oEWymDSE/·Source voice preserved·Brand labels redacted
⚠️
This domain has been flagged as malicious
Detected by 14 security vendors. Exercise extreme caution — do not enter personal information or connect wallets. Generate an official AI-powered complaint letter to file with cybercrime authorities.
REGISTRAR NEGLIGENCE · EGREGIOUS [REDACTED] was notified 5 months ago — the threat is still operational.
Why this matters — ICANN RAA §3.18 obligation & victim-assistance

On THE ENABLERS REGISTRY delivered an evidence-backed abuse report (repeated 11 times, most recently ) to domainabuse@IANA #69.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence. More than 5 months later, the possibly phishing infrastructure remains reachable .

Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. THE ENABLERS REGISTRY\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.

Victim-assistance obligation. [REDACTED] doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 11 separate notifications over 5 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.

Elapsed since first report
5 months
Reports sent
11
Latest case ID
[REDACTED]
Current status
Serving traffic (alive)
Ref
DBD685FA
Score
100/100
Engine
PD-4 Turbo
The domain [REDACTED] hosted a fraudulent cryptocurrency gambling platform, impersonating a legitimate crypto casino brand under the scam type "cryptocurrency." The site claimed to be the "Most Popular Online Crypto Casino Based on Blockchain," but its purpose was to deceive users into depositing cryptocurrency, likely leading to financial theft. The threat posed is direct financial loss through a fake gambling interface designed to capture user funds.

Technical evidence confirms malicious activity. VirusTotal reported 17 out of 95 security vendors flagged the domain, with detection by ADMINUSLabs, alphaMountain.ai, BitDefender, CyRadar, and ESET. The domain was registered through [REDACTED], created on 2025-11-05, hosted on IP 172.67.219.25 (US, [REDACTED]), and used SSL from Google Trust Services / WE1. Nameservers were jen.ns.IANA #1910.com and kirk.ns.IANA #1910.com. The domain appeared on 1 blocklist.

The site is currently down or offline. The risk level is high based on the 17/95 detection rate and its impersonation of a cryptocurrency gambling brand, indicating a clear intent to defraud users.
VirusTotal
VirusTotal
14 det.
URLQuery
URLQuery
100 det.
URLScan
URLScan
Gridinsoft
0/100
Age
9 mo
Observed status
Active threat 200
THE ENABLERS REGISTRY
DestroyList
Listed
Reports Sent
11 ignored
Data coverage VirusTotal 14 / 91 URLQuery 100 det. OTX no pulses CF Radar clean URLScan report ready DNS blocks none SSL no cert WHOIS 9 mo old Screenshot not captured Redirect chain not probed Gridinsoft 0/100

Threat Response Pipeline

Discovery
Checks
Reports
Availability
24/25
Pre-emptive Discovery & Ingestion
Threat Ingested
1/1 ✓
Threat Ingested
[REDACTED] detected and queued for full analysis
Nov 15, 2025
Threat Intelligence Checks
URLScan.io Snapshot · IANA #1910 Radar · Web Archive · VirusTotal · Google Safe Browsing · Forensic Evidence Collected · Technical Analysis Recorded · IANA #1910 Radar Scan · Content Observed Unavailable · IANA #1910 Radar Scan
10/10 ✓
URLScan.io Snapshot
Submitted to urlscan.io — screenshot, DOM & HTTP transactions captured
Mar 01, 2026
IANA #1910 Radar
Scanned via IANA #1910 Radar — DNS, certificates & network data
Web Archive
Preserved in Wayback Machine — historical evidence archived
VirusTotal
14 / 91 vendors flagged on VirusTotal
Jul 26, 2026
Google Safe Browsing
Mar 03, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Mar 01, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 26, 2026
IANA #1910 Radar Scan
Scanned via IANA #1910 Radar — network analysis completed
Mar 07, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 666); the cause was not independently established
Mar 02, 2026
IANA #1910 Radar Scan
Scanned via IANA #1910 Radar — network analysis completed
Feb 27, 2026
Notification Records
Initial Abuse Report (#1) · ICANN Escalation #2 · ICANN Escalation #3 · ICANN Escalation #4 · ICANN Escalation #5 · ICANN Escalation #6 · ICANN Escalation #7 · ICANN Escalation #8 · ICANN Escalation #9 · ICANN Escalation #10 · ICANN Escalation #11 · 11 Reports Filed
12/12 ✓
Initial Abuse Report (#1)
Sent to 1 abuse contact at [REDACTED] with forensic evidence
domainabuse@IANA #69.com
Feb 08, 2026
ICANN Escalation #2
Escalation #2 sent to 3 recipients including ICANN Compliance — follow-up record after a previous report
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Mar 03, 2026
ICANN Escalation #3
Escalation #3 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Mar 04, 2026
ICANN Escalation #4
Escalation #4 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Mar 06, 2026
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Apr 05, 2026
ICANN Escalation #6
Escalation #6 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Apr 20, 2026
ICANN Escalation #7
Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Apr 22, 2026
ICANN Escalation #8
Escalation #8 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Apr 26, 2026
ICANN Escalation #9
Escalation #9 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
Apr 28, 2026
ICANN Escalation #10
Escalation #10 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
May 05, 2026
ICANN Escalation #11
Escalation #11 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
domainabuse@IANA #69.comabuse@verisign-grs.comcompliance@icann.org
May 24, 2026
11 Reports Filed
11 report records were stored over 167 days; current observed status: Active threat
Publication & Availability
DestroyList Published · Monitoring Continues
1/2
DestroyList Published
Nov 15, 2025
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation

Public Blocklist Status

Evidence Capture

Live Snapshot
2025-11-15 13:14 UTC
Malicious · 14/91 engines
Forensic screenshot of [REDACTED] showing the phishing page layout
IP: 172.67.219.25
[REDACTED]
262d old
Page Title
Wagerone: Most Popular Online Crypto Casino Based on Blockchain

Domain Intelligence

Domain[REDACTED]
IP Address 172.67.219.25 CDN
GeoUS San Francisco, US
NetworkASAS13335 · [REDACTED]
Origin IP is hidden behind a CDN proxy. Reverse-IP on the edge IP returns unrelated tenants — origin discovery requires passive-DNS or CT cross-reference.
RegistrationCreated Nov 05, 2025 (262d) Expires Nov 05, 2026
Elapsed Since First Report 107 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Active threat.
Minimum notice count 11 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
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.
ICANN RAA §3.18 The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
HTTP Status200
Technical detailsDNS, SSL SANs, timestamps
First DetectedNov 15, 2025
Nameserversjen.ns.IANA #1910.comkirk.ns.IANA #1910.com
TLS Fingerprinta070850b1568acc85e6e6467af1efa3f26cd7631…
Favicon Hashfavicon50679c0c5e3ed56d05c1d0ed312419a7
Case ID[REDACTED]
Shared-IP Neighbors · 1 other domain
172.67.219.25 is hosting 1 other flagged possibly phishing/scam domain in our database. Co-hosting on a non-CDN IP is a strong bulletproof-hosting signal.
Abuse Report History · 11 stored reports over 105 days · click to expand
This timeline is built from stored outgoing report records. It documents timestamps and listed recipients, but does not by itself prove delivery, acknowledgement, or recipient action.
11 abuse reports filed over 167 days — latest observed status: Active threat
The records name [REDACTED] as a recipient or subject. ICANN Compliance appears in the recipient field for at least one record.
11
reports
167
days
ICANN CC
  1. Report #1 Feb 8, 2026 · 18:38 UTC
    Possibly phishing Abuse Report: [REDACTED]
    domainabuse@IANA #69.com
  2. Report #2 ICANN CC 535h still active Mar 3, 2026 · 02:04 UTC
    ESCALATION #2 (535h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  3. Report #3 ICANN CC 572h still active Mar 4, 2026 · 14:52 UTC
    ESCALATION #3 (572h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  4. Report #4 ICANN CC 616h still active Mar 6, 2026 · 11:06 UTC
    ESCALATION #4 (616h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  5. Report #5 ICANN CC 1324h still active Apr 5, 2026 · 01:58 UTC
    ESCALATION #5 (1324h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  6. Report #6 ICANN CC 1696h still active Apr 20, 2026 · 14:32 UTC
    ESCALATION #6 (1696h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  7. Report #7 ICANN CC 1750h still active Apr 22, 2026 · 20:25 UTC
    ESCALATION #7 (1750h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  8. Report #8 ICANN CC 1843h still active Apr 26, 2026 · 17:27 UTC
    ESCALATION #8 (1843h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  9. Report #9 ICANN CC 1892h still active Apr 28, 2026 · 18:23 UTC
    ESCALATION #9 (1892h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  10. Report #10 ICANN CC 2049h still active May 5, 2026 · 07:32 UTC
    ESCALATION #10 (2049h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
  11. Report #11 ICANN CC 2504h still active May 24, 2026 · 06:27 UTC
    ESCALATION #11 (2504h active): Possibly phishing - [REDACTED]
    domainabuse@IANA #69.com abuse@verisign-grs.com compliance@icann.org
Record scope: the timeline documents outgoing records stored by THE ENABLERS REGISTRY. Delivery, acknowledgement, and subsequent action require separate recipient or infrastructure evidence.
Technologies · 1 identified
Facebook
Detected via IANA #1910 Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 91 security vendors flagged this domain
View on VT
ADMINUSLabs
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive

Evidence & External Reports

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer's greatest advantage. Break it.

If you have interacted with this domain, entered personal information, or connected a cryptocurrency wallet — take immediate action. Below are resources to help you report the incident and protect yourself.

Beware of recovery scammers! After being scammed, criminals may contact you again pretending to be "recovery agents," lawyers, or investigators who claim they can retrieve your lost funds — for a fee. This is a second scam. No legitimate service will ask for upfront payment to recover stolen crypto. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or generate an AI-powered complaint →

Select your country...
180+ countries
Zero-PII — your data never leaves the browser AI writes in your language

Related Domain Reports

[REDACTED]
[REDACTED]
20 detections · Same kit
[REDACTED]
[REDACTED]
20 detections · Same kit
[REDACTED]
[REDACTED]
19 detections · Same kit
[REDACTED]
[REDACTED]
19 detections · Same kit
[REDACTED]
[REDACTED]
7 detections
[REDACTED]
[REDACTED]
8 detections
[REDACTED]
[REDACTED]
4 detections
[REDACTED]
[REDACTED]
10 detections

Other Domains on 172.67.219.25 3 possibly phishing domains

This IP hosts multiple possibly phishing domains — infrastructure shared across campaigns

[REDACTED] favicon [REDACTED] 15/95 [REDACTED] favicon [REDACTED] 13/95 [REDACTED] favicon [REDACTED] 2/95

More Domains at IANA #69 6 flagged

[REDACTED] favicon [REDACTED] 7/95 [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] 3/95 mgmslots.co favicon mgmslots.co 6/95 [REDACTED] favicon [REDACTED] 10/95 [REDACTED] favicon [REDACTED] 10/95

Gambler Scam Campaign Domains

Part of the Gambler Scam possibly phishing campaign. View all campaign domains →

[REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 21 [REDACTED] [REDACTED] 20

About This Report: [REDACTED]

This report presents the latest stored evidence available to THE ENABLERS REGISTRY. Source timestamps are shown where available; availability and vendor verdicts can change after collection.

The site displays a page titled “Wagerone: Most Popular Online Crypto Casino Based on Blockchain”.

[REDACTED] has been flagged by 14 security vendors as of July 26, 2026.

If you believe this listing is inaccurate, you can submit an appeal. For more information about our methodology, visit our FAQ page.

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

Recommendations & Advice for Victims

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with [REDACTED] — act now.

What should I do immediately?
Urgent
  • Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
  • Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
  • 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 possibly phishing site
What information should I collect for my report?
FBI guidelines

According to the FBI, the most important details are transaction data:

  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • 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 [REDACTED])
  • 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?

The FBI recovered over $1 billion in crypto fraud in 2024 thanks to victim reports. Your report matters.

How do crypto scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
  • Pig butchering — trust built over weeks via [REDACTED]/WhatsApp/dating apps, then money stolen
  • Recovery scams — victims targeted AGAIN by fake "recovery agents" demanding upfront fees. Always a scam
  • Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
  • AI-powered scams — deepfakes, automated possibly phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
  • Use a hardware wallet ([REDACTED], [REDACTED]). Never store large amounts in browser wallets
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Read every approval — verify permissions before signing. Reject unlimited approvals
  • Verify domains — check on THE ENABLERS REGISTRY before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
How big is the crypto scam problem?
  • $51 billion flowed to illicit crypto wallets in 2024 — CoinLedger
  • Pig butchering losses grew 40% year over year, now the fastest-growing fraud type
  • Only ~5% of victims report — your report helps shut down criminal networks
  • FBI recovered $1B+ in 2024 thanks to victim reports — FBI.gov

Sources: FBI · CoinLedger · WorldMetrics

Archive note

If the page below still says “we” or sounds suspiciously confident, that remains the upstream publisher speaking. TER only preserves the record, strips the house branding, and keeps exits wrapped through the source gate.