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-oDx7pEeyoT-uqD-6lfGEqEp/·Source voice preserved·Brand labels redacted
⚠️
This domain has been flagged as malicious
Detected by 10 security vendors and listed in 3 public blocklists. 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 TLD Registry (.io) 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 4 times, most recently ) to abuse@nic.io 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. If TLD Registry (.io) doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 4 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
4
Latest case ID
[REDACTED]
Current status
Serving traffic (alive)
Ref
1F39BDEC
Score
95/100
Engine
PD-4 Turbo
The domain [REDACTED] was registered on October 10, 2024 via [REDACTED] It resolves to IP 67.223.118.62, which is allocated to AS22612 ([REDACTED]) located in the United States. The web server reports LiteSpeed and presents a valid [REDACTED] under the Sectigo Public Server Authentication CA DV R36. HTTP response code is 200 and the page title is “AML Wallet”. Scamadviser assigns a trust score of 95/100, indicating a high likelihood of malicious intent. VirusTotal scans show that 10 of 95 security vendors flag the domain as malicious. The domain appears on four security blocklists and is currently blocked by THE ENABLERS REGISTRY, Polkadot, Enkrypt, and Codeesura. The listed scam type is “Crypto Scam”, consistent with the threat classification as a crypto drainer. No additional infrastructure such as extra A records, MX records, or sub‑domains is disclosed. The combination of a low trust score, multiple vendor detections, and active blocklist listings suggests the site is being used to solicit cryptocurrency transfers, likely by impersonating legitimate anti‑money‑laundering services. Defenders should continue to block the domain at network perimeter and endpoint layers, monitor DNS queries for the resolved IP, and consider adding the IP address to threat intelligence feeds. Further investigation of the site’s content, URL paths, and any associated command‑and‑control traffic is required to confirm the exact draining mechanisms.
VirusTotal
VirusTotal
10 det.
URLScan
URLScan
Gridinsoft
72/100
ScamAdviser
Scamadviser
5/100
SSL
Sectigo Public Server Authentication CA DV R36
Age
1.8 yr
Observed status
Active threat 200
THE ENABLERS REGISTRY
DestroyList
Listed
Reports Sent
4 ignored
Data coverage VirusTotal 10 / 95 URLQuery no detections OTX no pulses CF Radar clean URLScan report ready DNS blocks none SSL valid, 272d WHOIS 22 mo old Screenshot not captured Redirect chain not probed Gridinsoft 72/100 Scamadviser 5/100
Security Signals
SA Scamadviser Warnings 5/100
The identity of the owner of the website is hidden on WHOIS The Tranco rank (how much traffic) is rather low The registrar of this website is popular amongst scammers Negative reviews were detected for this website This website looks to be hosted by a shady service provider. The website was reported in the last 30 days as threat by DNSFilter
We found a valid SSL certificate
GS Gridinsoft Analysis 72 / 100
Hosting SSL Certificate Young Domain

Threat Response Pipeline

Discovery
Checks
Reports
Availability
13/14
Pre-emptive Discovery & Ingestion
Threat Ingested
1/1 ✓
Threat Ingested
[REDACTED] detected and queued for full analysis
Sep 08, 2025
Threat Intelligence Checks
URLScan.io Snapshot · IANA #1910 Radar · Web Archive · VirusTotal · Google Safe Browsing · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded
8/8 ✓
URLScan.io Snapshot
Submitted to urlscan.io — screenshot, DOM & HTTP transactions captured
Mar 05, 2026
IANA #1910 Radar
Scanned via IANA #1910 Radar — DNS, certificates & network data
Web Archive
Preserved in Wayback Machine — historical evidence archived
VirusTotal
10 / 95 vendors flagged on VirusTotal
Feb 23, 2026
Google Safe Browsing
Mar 02, 2026
Blocklist Detection
Found in 3 blocklists: Polkadot, Enkrypt, Codeesura
Jul 25, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Mar 05, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 25, 2026
Notification Records
Initial Abuse Report (#1) · ICANN Escalation #4 · 2 Reports Filed
3/3 ✓
Initial Abuse Report (#1)
Sent to 1 abuse contact at [REDACTED] with forensic evidence
abuse@IANA #1068.com
Jan 28, 2026
ICANN Escalation #4
Escalation #4 sent to 2 recipients including ICANN Compliance — follow-up record after a previous report
abuse@nic.iocompliance@icann.org
Mar 22, 2026
2 Reports Filed
2 report records were stored over 178 days; current observed status: Active threat
Publication & Availability
DestroyList Published · Monitoring Continues
1/2
DestroyList Published
Sep 08, 2025
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation

Public Blocklist Status

4
Confirmed in 4 datasets: THE ENABLERS REGISTRY + 3 independent public blocklists — Polkadot, Enkrypt, Codeesura
10 external threat databases checked; 3 matched. Last synchronized Jul 25, 2026. THE ENABLERS REGISTRY database match: confirmed.

Evidence Capture

Live Snapshot
2025-09-08 05:28 UTC
Malicious · 10/95 engines
Forensic screenshot of [REDACTED] showing the phishing page layout
IP: 67.223.118.62
[REDACTED]
653d old
Sectigo Public Server Authentication CA DV R36
Page Title
AML Wallet

Domain Intelligence

Domain[REDACTED]
IP Address 67.223.118.62 US
GeoUS Phoenix, US
NetworkASAS22612 · [REDACTED]
RegistrationCreated Oct 10, 2024 Expires Oct 10, 2025
Elapsed Since First Report 47 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 4 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 DetectedSep 08, 2025
Nameservers[REDACTED][REDACTED]
TLS Fingerprint607b4bf5ff352a38ecda3d678cd38b2e293171d7…
TLS SAN Domains[REDACTED]
Favicon Hashfavicon6b8012a3d4addd3995652e8756f9008e
Case ID[REDACTED]
Abuse Report History · 2 stored reports over 54 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.
2 abuse reports filed over 178 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.
2
reports
178
days
ICANN CC
  1. Report #1 Escalation 85h still active Jan 28, 2026 · 07:32 UTC
    ESCALATION #3 (85h active): Possibly phishing - [REDACTED]
    abuse@IANA #1068.com
  2. Report #4 ICANN CC 1363h still active Mar 22, 2026 · 16:37 UTC
    ESCALATION #4 (1363h active): Possibly phishing - [REDACTED]
    abuse@nic.io 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
LiteSpeed
Web servers

High-performance web server compatible with Apache configurations.

Detected via IANA #1910 Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 95 security vendors flagged this domain
View on VT
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Lionic
Sophos

Archived Evidence

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

Google PageSpeed Insights — mobile performance audit of [REDACTED] · checked Mar 2, 2026

67
Needs Work
Performance
FCP
2.6s
First Contentful Paint
LCP
6.28s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

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]
3 detections · Same kit
[REDACTED]
[REDACTED]
4 detections
[REDACTED]
[REDACTED]
14 detections
[REDACTED]
[REDACTED]
4 detections
[REDACTED]
[REDACTED]
10 detections
[REDACTED]
[REDACTED]
14 detections
[REDACTED]
[REDACTED]
11 detections

More Domains at IANA #1068 6 flagged

[REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] 1/95 [REDACTED] favicon [REDACTED] 5/95 [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED]

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 “AML Wallet”.

[REDACTED] has been flagged by 10 security vendors as of July 25, 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.