VirusTotal
6 / 91 engine detections
Apri il rapporto“Crownsaves - Investment company”
crownsaves.net — Contenuto non disponibile. Riepilogo delle prove: VirusTotal 6/91 (alphaMountain.ai, CRDF, Fortinet, Gridinsoft, Netcraft); Spamhaus DBL_SPAM; PhishDestroy score 73/100. Registrar: Ultahost.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
6 / 91 engine detections
Apri il rapportoDBL_SPAM
4 community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
crownsaves.net is on the PhishDestroy blocklist and presented itself under the page title "Crownsaves - Investment company". It addressed people looking for a place to put their money, but it did not name any established brand. PhishDestroy first saw the domain on 2026-07-27. It went offline on 2026-09-08, and as of 2026-10-19 its DNS no longer resolves.
The site's only self-description was an investment company with no recognisable identity behind it. Combined with security-vendor flags and a spam listing, that matches the risk profile of unlicensed investment fronts. Such sites typically take deposits by promising returns, then make funds hard or impossible to recover. Because the site is now dark, the main exposure is to anyone who already sent money or shared personal and payment details while it was online.
On 2026-08-14, six of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Fortinet, Gridinsoft, Netcraft and SOCRadar. That is a modest count. Still, Netcraft and Fortinet maintain dedicated fraud and phishing feeds, so their agreement carries weight. Spamhaus lists the domain in its DBL as spam, which ties it to unsolicited promotion. It also appears in four AlienVault OTX threat pulses, meaning other researchers had already catalogued it.
The domain was registered through Ultahost, Inc. It was hosted in the Netherlands on the SpectraIP B.V. network, at 5.182.208.206. A free automated Let's Encrypt certificate secured the site, so the padlock in the browser said nothing about who ran the business. The site stayed reachable for roughly six weeks after PhishDestroy first saw it.
If you deposited money with Crownsaves, stop sending further payments, including any "fees" or "taxes" requested to release a balance. Contact your bank or payment provider about a chargeback or recall. Keep receipts, chats and emails, and report the loss to your national fraud authority. If you created an account, change that password anywhere you reused it and watch for follow-up contact from "recovery" services, which often target the same victims. Defenders should block the domain and the hosting IP and check mail logs for messages promoting Crownsaves.
ns2.zencorehost.comcrownsaves.netpriority 0Location describes the IP network.
bf1325d2c3822d3dce2de893a6a2d5786cbc71f65c39a90f3d53d36cca28fc5fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of crownsaves.net · checked Aug 13, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Raggiungibile→Non disponibile
5→6
Raggiungibile
4 community references
View sourceNo threat flag
View source6/91 engine detections
View sourcecrownsaves.net
View source2 segnalazioni della comunità
CategoriaOTHER_INVESTMENT_SCAM
Data submited by Intelligence for good
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
crownsaves.net
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
crownsaves.net)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.