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-oTSBnjq2mPGGqTy_qjaypDG2oDZ7qEqE/·Source voice preserved·Brand labels redacted
⚠️
This domain has been flagged as malicious
Detected by 13 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 4 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@identitydigital.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence. More than 4 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 4 separate notifications over 4 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
4 months
Reports sent
4
Latest case ID
PD-1773540055-coinsecurity.di
Current status
Serving traffic (alive)
Ref
C451B3A0
Score
100/100
Engine
PD-4 Turbo
This domain, www.[REDACTED], is actively flagged as a high-risk possibly phishing site impersonating Google. Analysis indicates the domain was registered on March 3, 2026, through [REDACTED], and remains operational as of July 12, 2026. The site resolves to IP address 87.120.219.250 and presents a page title matching the targeted brand, further supporting the impersonation claim. Security vendors have detected this domain on two blocklists, and it appears in two threat intelligence pulses, reinforcing its classification as malicious infrastructure. Infrastructure analysis reveals the use of Google Web Server technology, HSTS, and HTTP/3, which may be employed to lend an appearance of legitimacy or to evade detection. The SSL certificate is issued by Let's Encrypt, a common choice for both legitimate and malicious sites due to its accessibility. While the presence of these technologies does not inherently confirm malicious intent, their combination with the domain's registration details and detection by security vendors raises significant concerns. The page content itself has not been fully analyzed, but the page title explicitly matches the targeted brand, aligning with typical brand impersonation tactics. Defenders should treat this domain as confirmed malicious infrastructure. The risk level is classified as high due to the domain's active status, its presence on multiple blocklists, and its detection by 13 out of 95 security vendors. Network-level blocking is recommended for this IP and domain to prevent potential credential theft or other fraudulent activities. Given the domain's recent creation and ongoing activity, continuous monitoring is advised to track any changes in hosting, SSL certificates, or associated infrastructure. If this domain is encountered in logs or user reports, it should be investigated as part of a broader possibly phishing campaign targeting Google users.
VirusTotal
VirusTotal
13 det.
URLQuery
URLQuery
2 det.
OTX AlienVault
DNS Security
3/14
URLScan
URLScan
Gridinsoft
0/100
SSL
Let's Encrypt
Age
5 mo
Observed status
Active threat 200
THE ENABLERS REGISTRY
DestroyList
Listed
Reports Sent
3 ignored
Data coverage VirusTotal 13 / 94 URLQuery 2 det. OTX 2 pulses CF Radar clean URLScan report ready DNS blocks 3/14 SSL valid, 71d WHOIS 5 mo old Screenshot not captured Redirect chain not probed Gridinsoft 0/100
Network Security Intelligence
DNS Provider Blocks 3 / 14
Controld Adblock Controld Family Controld Malware

Threat Response Pipeline

Discovery
Checks
Reports
Availability
18/19
Pre-emptive Discovery & Ingestion
Threat Ingested
1/1 ✓
Threat Ingested
[REDACTED] detected and queued for full analysis
Mar 03, 2026
Threat Intelligence Checks
IANA #1910 Radar · Web Archive · VirusTotal · Google Safe Browsing · OTX Threat Intel · DNS Security Blocks · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · VT Detection +12 · VT Detection +1 · IANA #1910 Radar Scan
12/12 ✓
IANA #1910 Radar
Scanned via IANA #1910 Radar — DNS, certificates & network data
Web Archive
Preserved in Wayback Machine — historical evidence archived
VirusTotal
13 / 94 vendors flagged on VirusTotal
Jul 12, 2026
Google Safe Browsing
Jul 12, 2026
OTX Threat Intel
Found in 2 OTX pulses on AlienVault OTX
Jul 12, 2026
DNS Security Blocks
Blocked by 3 of 14 DNS providers: Controld adblock, Controld family, Controld malware
Brand Impersonation
Impersonation of Google
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 25, 2026
VT Detection +12
+12 new detections (1 → 13): ADMINUSLabs, BitDefender, Chong Lua Dao, CyRadar +9
Jul 12, 2026
VT Detection +1
+1 new detection (0 → 1): SOCRadar
Mar 04, 2026
IANA #1910 Radar Scan
Scanned via IANA #1910 Radar — network analysis completed
Mar 03, 2026
Notification Records
Initial Abuse Report (#1) · ICANN Escalation #3 · ICANN Escalation #4 · 3 Reports Filed
4/4 ✓
Initial Abuse Report (#1)
Sent to 2 abuse contacts at [REDACTED] with forensic evidence
abuse@identitydigital.comcompliance@icann.org
Mar 15, 2026
ICANN Escalation #3
Escalation #3 sent to 2 recipients including ICANN Compliance — follow-up record after a previous report
abuse@identitydigital.comcompliance@icann.org
May 30, 2026
ICANN Escalation #4
Escalation #4 sent to 2 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse@identitydigital.comcompliance@icann.org
Jun 01, 2026
3 Reports Filed
3 report records were stored over 132 days; current observed status: Active threat
Publication & Availability
DestroyList Published · Monitoring Continues
1/2
DestroyList Published
Mar 03, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation

Public Blocklist Status

Evidence Capture

Live Snapshot
2026-03-03 20:31 UTC
Malicious · 13/94 engines
Forensic screenshot of [REDACTED] showing the phishing page layout
IP: 87.120.219.250
[REDACTED]
143d old
Let's Encrypt
Page Title
Google

Domain Intelligence

Domain[REDACTED]
Registrar Global Domain Group US(US)
IP Address 87.120.219.250 CDN
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 Mar 03, 2026 (143d)
Elapsed Since First Report 12 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 3 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 DetectedMar 03, 2026
Nameservers["imani.ns.IANA #1910.com","andronicus.ns.IANA #1910.com"]
Favicon Hashfavicona615b465733cab212d64f85132eb8e16
Case IDPD-20260303-41FB4E
Shared-IP Neighbors · 8 other domains
87.120.219.250 is hosting 8 other flagged possibly phishing/scam domains in our database. Co-hosting on a non-CDN IP is a strong bulletproof-hosting signal.
Abuse Report History · 3 stored reports over 79 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.
3 abuse reports filed over 132 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.
3
reports
132
days
ICANN CC
  1. Report #1 ICANN CC 269h still active Mar 15, 2026 · 02:01 UTC
    ESCALATION #2 (269h active): Possibly phishing - [REDACTED]
    abuse@identitydigital.com compliance@icann.org
  2. Report #3 ICANN CC 1819h still active May 30, 2026 · 03:24 UTC
    ESCALATION #3 (1819h active): Possibly phishing - [REDACTED]
    abuse@identitydigital.com compliance@icann.org
  3. Report #4 ICANN CC 1866h still active Jun 1, 2026 · 02:14 UTC
    ESCALATION #4 (1866h active): Possibly phishing - [REDACTED]
    abuse@identitydigital.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.
Related Campaign Members · 8 sharing fingerprint
Other tracked possibly phishing domains sharing this site’s infrastructure fingerprint: [REDACTED] Google — suggests a coordinated kit / operator cluster.
Technologies · 3 identified
Google Web Server
HSTS
Security

HTTP Strict Transport Security — forces browsers to use HTTPS connections only.

HTTP/3
Miscellaneous

Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.

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

VirusTotal Analysis

13 / 94 security vendors flagged this domain
View on VT
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE

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 Jul 12, 2026

89
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.04s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
13ms
Total Blocking Time
SI
2.89s
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]
13 detections · Same kit
[REDACTED]
[REDACTED]
In DestroyList · Same kit
[REDACTED]
[REDACTED]
7 detections
[REDACTED]-help-us.[REDACTED]
[REDACTED]-help-us.[REDACTED]
7 detections
[REDACTED]
[REDACTED]
7 detections
[REDACTED]
[REDACTED]
10 detections
[REDACTED]
[REDACTED]
8 detections
[REDACTED]
[REDACTED]
15 detections

Other Domains on 87.120.219.250 6 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] 11/95 [REDACTED] favicon [REDACTED] 7/95 [REDACTED] favicon [REDACTED] 6/95 [REDACTED] favicon [REDACTED] 4/95

More Domains at Global Domain Group 6 flagged

[REDACTED] favicon [REDACTED] 2/95 [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] 3/95 [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] [REDACTED] favicon [REDACTED] 1/95

Other Google Impersonation Domains

These domains also target Google users. View all Google threats →

productionmaza.cfd productionmaza.cfd 27 [REDACTED] [REDACTED] 26 [REDACTED] [REDACTED] 25 [REDACTED] [REDACTED] 25 [REDACTED] [REDACTED] 25 [REDACTED] [REDACTED] 25 [REDACTED] [REDACTED] 25 [REDACTED] [REDACTED] 24

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 “Google”, which may be designed to impersonate Google.

[REDACTED] has been flagged by 13 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.