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-oDK8YwV_ZwV/·Source voice preserved·Brand labels redacted
⚠️
This domain has been flagged as malicious
Detected by 7 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 · HIGH [REDACTED] was notified 27 hours 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 3 times, most recently ) to abuse@microsoft.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence. More than 27 hours 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 3 separate notifications over 27 hours, 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
27 hours
Reports sent
3
Latest case ID
PD-20260727-D04AAE
Current status
Serving traffic (alive)
Ref
5525D5DD
Score
83/100
Engine
PD-4 Turbo
This domain, 2222[.]ooo, was registered through [REDACTED] on August 07, 2024 and is currently resolved to the IP address 13.75.95.171. The authoritative name servers listed for the zone are [REDACTED] and [REDACTED]. Threat‑intelligence feeds have flagged the domain as active possibly phishing infrastructure; the THE ENABLERS REGISTRY blocklist currently lists it, and it appears on one additional security blocklist.

VirusTotal analysis shows that seven of ninety‑one scanning engines have returned a malicious verdict, indicating a consensus of suspicious behavior among multiple vendors. No public SSL/TLS certificate details, HTTP response codes, or page title information are available in the collected data, so the content served by the site has not been examined. Likewise, there is no indication of a targeted brand or specific possibly phishing kit in the evidence set.

The limited detection footprint—one blocklist entry and a modest VirusTotal detection count—suggests that the infrastructure is either newly deployed or operating with a low profile, but the presence of multiple vendor detections confirms that the domain is being used for malicious purposes. Defenders should add 2222[.]ooo to outbound and inbound filtering rules, monitor DNS queries for the associated name servers, and consider enriching local threat feeds with the IP 13.75.95.171. Continuous re‑evaluation is recommended, as further analysis of the web content or TLS fingerprint could reveal additional indicators of compromise.
VirusTotal
VirusTotal
7 det.
OTX AlienVault
URLScan
URLScan
SSL
Let's Encrypt 12d
Age
2 yr
Observed status
Last known active
THE ENABLERS REGISTRY
DestroyList
Listed
Reports Sent
3 ignored
Data coverage VirusTotal 7 / 91 URLQuery no detections OTX 1 pulse CF Radar clean URLScan report ready DNS blocks none SSL valid, 12d WHOIS 24 mo old Screenshot not captured Redirect chain not probed

Threat Response Pipeline

Discovery
Checks
Reports
Availability
10/11
Pre-emptive Discovery & Ingestion
Threat Ingested
1/1 ✓
Threat Ingested
2222.ooo detected and queued for full analysis
Jul 27, 2026
Threat Intelligence Checks
URLScan.io Snapshot · IANA #1910 Radar · VirusTotal · Google Safe Browsing · OTX Threat Intel · Forensic Evidence Collected · Technical Analysis Recorded
7/7 ✓
URLScan.io Snapshot
Submitted to urlscan.io — screenshot, DOM & HTTP transactions captured
Jul 27, 2026
IANA #1910 Radar
Scanned via IANA #1910 Radar — DNS, certificates & network data
VirusTotal
7 / 91 vendors flagged on VirusTotal
Jul 27, 2026
Google Safe Browsing
Jul 27, 2026
OTX Threat Intel
Found in 1 OTX pulse on AlienVault OTX
Jul 27, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Jul 27, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 28, 2026
Notification Records
Abuse Reports Sent
1/1 ✓
Abuse Reports Sent
Abuse report sent to registrar [REDACTED], hosting provider, 2 abuse contacts
abuse@IANA #472.comabuse@microsoft.com
Jul 27, 2026
Publication & Availability
DestroyList Published · Availability Unverified
1/2
DestroyList Published
Jul 27, 2026
Availability Unverified
The latest response is insufficient to classify current availability

Public Blocklist Status

Evidence Capture

Live Snapshot
2026-07-27 04:43 UTC
Malicious · 7/91 engines
Forensic screenshot of 2222.ooo showing the phishing page layout
IP: 13.75.95.171
[REDACTED]
719d old
Let's Encrypt
Page Title
澳门金沙

Domain Intelligence

Domain2222.ooo
IP Address 13.75.95.171 HK
GeoHK Hong Kong, HK
NetworkAS8075 · Microsoft Azure Cloud (eastasia)
RegistrationCreated Aug 07, 2024 Expires Aug 07, 2027
Technical detailsDNS, SSL SANs, timestamps
First DetectedJul 27, 2026
Nameservers[REDACTED][REDACTED]
TLS Fingerprintc23e65b896f15b6d3aef55ad67ba9423ddb9ea1c…
Case IDPD-20260727-D04AAE
Technologies · 3 identified
Nginx
Web servers Reverse proxies

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

[REDACTED] 100% confidence
jQuery
JavaScript libraries

jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.

[REDACTED] 100% confidence
HSTS
Security

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

[REDACTED] 100% confidence
Detected via IANA #1910 Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 91 security vendors flagged this domain
View on VT
alphaMountain.ai
BitDefender
CyRadar
ESET
Fortinet
G-Data
PhishFort
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of 2222.ooo · checked Jul 27, 2026

66
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
6.65s
Largest Contentful Paint
CLS
0.042
Cumulative Layout Shift
TBT
3ms
Total Blocking Time
SI
6.71s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Evidence & External Reports

Third-Party Detection — ChainAbuse
2 reports filed for 2222.ooo · category: Impersonation
Flagged by automated brand-abuse detection on Jul 14, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).

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]
21 detections · Similar title
[REDACTED]
[REDACTED]
20 detections · Similar title
[REDACTED]
[REDACTED]
18 detections · Similar title
[REDACTED]
[REDACTED]
18 detections · Similar title
[REDACTED]
[REDACTED]
5 detections
[REDACTED]
[REDACTED]
12 detections
[REDACTED]
[REDACTED]
5 detections
[REDACTED]
[REDACTED]
11 detections

More Domains at IANA #472 6 flagged

322320a2.buzz favicon 322320a2.buzz 14/95 [REDACTED] favicon [REDACTED] 1/95 playnance.fr favicon playnance.fr 1/95 [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] 1/95 acessse.co favicon acessse.co 1/95

About This Report: 2222.ooo

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 “澳门金沙”.

2222.ooo has been flagged by 7 security vendors as of July 28, 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 2222.ooo — 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 2222.ooo)
  • 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.