Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 4 times, most recently ) to abuse@web.com with the evidence stored for the case at that time.
More than 5 months later, the 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. PhishDestroy\'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 SNAPNAMES 27, LLC 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.
crownstake[.]com
Phishing and security check for crownstake.com
“crownstake.com”
PhishDestroy first recorded crownstake.com on Feb 8, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 68/100.
The latest stored availability state is “Last known active” (HTTP 200) on Aug 4, 2026 at 22:14 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.
VirusTotal returned 1 detection from 95 scanners in the stored check on Jul 10, 2026 at 15:08 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 4, 2026 at 22:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.
Other stored evidence. Google Safe Browsing stored no positive flag on Mar 2, 2026 at 20:38 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 09:52 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 10:35 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 25, 2026 at 11:53 UTC.
Stored context lists registrar SNAPNAMES 27, LLC, IP address 23.48.8.13. Except for the registration date, these fields do not share a source timestamp in this report and may change.
Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.
Security Signals
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
ICANN Got Paid. Accountability Did Not Arrive.
For this gTLD, the registrar above operates under an ICANN contract. ICANN collects annual, variable and transaction-based fees tied to registrations, renewals and transfers.
Accreditation: monetized. Accountability: please check back later.
Then the magic starts: ICANN writes RAA §3.18, the registrar investigates abuse inside its own customer base, and victims deliver the evidence for free while every layer waits for someone else to act. If that makes victims feel safer, excellent—the invoice worked.
Abuse Report History · 4 stored reports over 37 days · click to expand
-
Report #1 Feb 8, 2026 · 18:21 UTCPhishing Abuse Report: crownstake[.]comabuse@web.com
-
Report #2 ICANN CC 583h still active Mar 5, 2026 · 01:49 UTCESCALATION #2 (583h active): Phishing - crownstake[.]comabuse@web.com abuse@verisign-grs.com compliance@icann.org
-
Report #3 ICANN CC 617h still active Mar 6, 2026 · 11:31 UTCESCALATION #3 (617h active): Phishing - crownstake[.]comabuse@web.com abuse@verisign-grs.com compliance@icann.org
-
Report #4 ICANN CC 869h still active Mar 16, 2026 · 23:35 UTCESCALATION #4 (869h active): Phishing - crownstake[.]comabuse@web.com abuse@verisign-grs.com compliance@icann.org
Casino / Gambling License Verification
Technologies · 5 identified
JavaScript runtime built on Chrome V8 engine for server-side development.
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
VirusTotal Analysis
Archived Evidence
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of crownstake.com · checked Mar 2, 2026
Evidence & External Reports
Were You Affected by This Site?
If you entered account credentials, personal or payment information, or downloaded a file from this domain, take immediate action. Below are resources to help you report the incident and protect yourself.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
About This Report: crownstake.com
This report presents the latest stored evidence available to PhishDestroy. Source timestamps are shown where available; availability and vendor verdicts can change after collection.
The captured site displayed the page title “crownstake.com”.
As of Aug 4, 2026, crownstake.com had detections from 1 security engines.
If you believe this listing is inaccurate, submit an appeal. To learn about our methodology, visit the FAQ page.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive