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-ojKwY0uuozS8nN/·Source voice preserved·Brand labels redacted
⚠️
This domain has been flagged as malicious
Detected by 2 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 2 times, most recently ) to complaint@IANA #1923 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 2 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
2
Latest case ID
PD-20260316-D543EF
Current status
Serving traffic (alive)
Ref
C483EE84
Score
25/100
Engine
PD-4 Turbo
[REDACTED] was registered on March 11, 2026 through [REDACTED] and is currently active. DNS resolution points to 142.251.154.119, an address owned by [REDACTED] in the United States. The site returns HTTP status 200 and presents a page titled "Google Chrome – The Fast and Secure Web Browser Built to be Yours," a clear attempt to mimic a legitimate brand. The authoritative nameservers are john.ns.IANA #1910.com and natasha.ns.IANA #1910.com, confirming IANA #1910’s role as the DNS and CDN provider.

Infrastructure analysis shows the domain is listed on a single security blocklist and has been flagged by THE ENABLERS REGISTRY. VirusTotal scans indicate that only 2 of 95 security vendors have identified the domain as malicious, suggesting limited visibility in broader threat feeds. The site’s Gridinsoft trust score is 1 out of 100, reflecting an extremely low reputation. The observed possibly phishing kit is identified as the Gambler Scam, commonly associated with cryptocurrency‑focused fraud.

While the low vendor detection count and minimal blocklist presence could be interpreted as a nascent campaign, the combination of a brand‑impersonation page title, a known possibly phishing kit, and a trust score of 25/100 provides strong evidence of malicious intent. The primary uncertainty lies in the scope of victim exposure, as current data does not disclose the volume of possibly phishing emails or the specific cryptocurrency assets being targeted. Nonetheless, the presence of a high‑risk brand impersonation vector warrants immediate attention.

Defenders should add [REDACTED] to outbound and inbound filtering policies and monitor DNS queries for the associated IANA #1910 nameservers. Network sensors should flag any HTTP traffic to the IP 142.251.154.119, especially requests that include the observed page title. Continuous re‑evaluation of detection feeds is advised, as additional security vendors may raise their detection counts as the campaign matures.
VirusTotal
VirusTotal
2 det.
URLScan
URLScan
Gridinsoft
1/100
Age
4 mo
Observed status
Active threat 200
THE ENABLERS REGISTRY
DestroyList
Listed
Reports Sent
2 ignored
Data coverage VirusTotal 2 / 94 URLQuery no detections OTX no pulses CF Radar clean URLScan report ready DNS blocks none SSL no cert WHOIS 4 mo old Screenshot not captured Redirect chain not probed Gridinsoft 1/100
Security Signals
GS Gridinsoft Analysis 1 / 100
4 0 2 0 42

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
Mar 17, 2026
Threat Intelligence Checks
URLScan.io Snapshot · IANA #1910 Radar · VirusTotal · Google Safe Browsing · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · VT Detection +1
8/8 ✓
URLScan.io Snapshot
Submitted to urlscan.io — screenshot, DOM & HTTP transactions captured
Mar 24, 2026
IANA #1910 Radar
Scanned via IANA #1910 Radar — DNS, certificates & network data
VirusTotal
2 / 94 vendors flagged on VirusTotal
Mar 19, 2026
Google Safe Browsing
Mar 17, 2026
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Mar 24, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results
Jul 24, 2026
VT Detection +1
+1 new detection (0 → 1): Gridinsoft
Mar 17, 2026
Notification Records
Initial Abuse Report (#1) · ICANN Escalation #3 · 2 Reports Filed
3/3 ✓
Initial Abuse Report (#1)
Sent to 3 abuse contacts at [REDACTED] with forensic evidence
Apr 13, 2026
ICANN Escalation #3
Escalation #3 sent to 3 recipients including ICANN Compliance — follow-up record after a previous report
May 05, 2026
2 Reports Filed
2 report records were stored over 101 days; current observed status: Active threat
Publication & Availability
DestroyList Published · Monitoring Continues
1/2
DestroyList Published
Mar 17, 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-17 02:33 UTC
Malicious · 2/94 engines
Forensic screenshot of [REDACTED] showing the phishing page layout
IP: 142.251.154.119
[REDACTED]
134d old
Page Title
Google Chrome – The Fast and Secure Web Browser Built to be Yours
Impersonates
Across Facebook Google Linkedin Tiktok Youtube

Domain Intelligence

Domain[REDACTED]
IP Address 142.251.154.119 CDN
GeoUS San Francisco, US
NetworkASAS15169 · [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 Mar 11, 2026 (134d)
Elapsed Since First Report 37 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 2 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 17, 2026
Nameserversjohn.ns.IANA #1910.comnatasha.ns.IANA #1910.com
Favicon Hashfavicon50679c0c5e3ed56d05c1d0ed312419a7
Case IDPD-20260316-D543EF
Abuse Report History · 2 stored reports over 22 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 101 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
101
days
ICANN CC
  1. Report #2 ICANN CC 657h still active Apr 13, 2026 · 15:32 UTC
    ESCALATION #2 (657h active): Possibly phishing - [REDACTED]
    complaint@IANA #1923 abuse@verisign-grs.com compliance@icann.org
  2. Report #3 ICANN CC 1178h still active May 5, 2026 · 07:50 UTC
    ESCALATION #3 (1178h active): Possibly phishing - [REDACTED]
    complaint@IANA #1923 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.
Related Campaign Members · 8 sharing fingerprint
Other tracked possibly phishing domains sharing this site’s infrastructure fingerprint: [REDACTED] Across — suggests a coordinated kit / operator cluster.
Technologies · 4 identified
YouTube
Google AdSense

Advertising platform — conversion and remarketing tracking pixel.

Google Analytics
Analytics

Web analytics service tracking website traffic and user behavior.

marketingplatform.google.com
Google Tag Manager
Tag managers

Tag management system for deploying marketing and analytics tags.

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

VirusTotal Analysis

2 / 94 security vendors flagged this domain
View on VT
Gridinsoft
SOCRadar

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]
15 detections · Similar title
[REDACTED]
[REDACTED]
15 detections · Similar title
rollwin.lol
rollwin.lol
6 detections · Similar title
[REDACTED]
[REDACTED]
5 detections · Similar title

Other Domains on 142.251.154.119 6 possibly phishing domains

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

logstorage.in favicon logstorage.in 18/95 [REDACTED] favicon [REDACTED] 16/95 [REDACTED] favicon [REDACTED] 12/95 [REDACTED] favicon [REDACTED] 11/95 org-vote.rest favicon org-vote.rest 6/95 [REDACTED] favicon [REDACTED] 5/95

More Domains at IANA #1923 6 flagged

[REDACTED] favicon [REDACTED] 1/95 [REDACTED] favicon [REDACTED] 1/95 [REDACTED] favicon [REDACTED] 1/95 bose.locker favicon bose.locker [REDACTED] favicon [REDACTED] 18/95 osejp.co favicon osejp.co 1/95

Other Across Impersonation Domains

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

[REDACTED] [REDACTED] 24 [REDACTED] [REDACTED] 24 [REDACTED] [REDACTED] 22 [REDACTED] [REDACTED] 22 hungfapeper.sbs hungfapeper.sbs 22 [REDACTED] [REDACTED] 22 [REDACTED] [REDACTED] 22 polymarket-login.at polymarket-login.at 22

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 “Google Chrome – The Fast and Secure Web Browser Built to be Yours”, which may be designed to impersonate Across.

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