VirusTotal
3 / 89 engine detections
Apri il rapportoDominio in blocklist: crypto-lii.netlify.app — Contenuto non disponibile (HTTP 404). Riepilogo delle prove: VirusTotal 3/89 (alphaMountain.ai, Forcepoint…
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
3 / 89 engine detections
Apri il rapportono community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoNo malicious flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
crypto-lii.netlify.app is an impersonation phishing page built on a free Netlify subdomain and aimed at cryptocurrency users. Its listing on the MetaMask and SEAL blocklists points to wallet holders as the intended victims. PhishDestroy first saw it on 2026-09-08, and the site was offline by 2026-09-11. It was still dead at the last check on 2026-10-19, with nothing served at the root.
Impersonation pages copy the look of a familiar crypto service so visitors trust them. A typical page then asks the visitor to connect a wallet, sign a transaction, or type in a recovery phrase or login details. Anything entered goes straight to the operators. A recovery phrase hands over the whole wallet, while a signed approval lets them move tokens without asking again. Throwaway hosting like this lets a page go live within minutes and vanish just as quickly, which fits the three-day lifespan seen here.
Wallet-security blocklists caught it first. MetaMask and SEAL both list the domain alongside PhishDestroy, which means the major wallet-side filters independently treat it as hostile. On VirusTotal the picture is thin: on 2026-09-16, after the page had already gone dark, 3 of 89 engines flagged it (alphaMountain.ai, Forcepoint ThreatSeeker and VIPRE). That low count reflects how briefly the site was up, not a clean bill of health.
The operators never registered a domain. They used a Netlify subdomain, which costs nothing and leaves no registration trail, a common choice for short-lived crypto phishing. The page was served from Amazon.com, Inc. infrastructure in Germany. Its DigiCert certificate is the platform's standard one, so the browser padlock said nothing about who ran the page.
If you connected a wallet to this site, use a token-approval checker to review your approvals and revoke any you don't recognize, especially recent unlimited allowances. If you typed a seed phrase or private key into it, treat that wallet as compromised. Create a new wallet on a clean device and move any remaining funds there right away. If you entered an exchange or service login, change that password and reset two-factor authentication. Security teams should block the hostname and watch for similar names on free hosting subdomains. New lookalikes on the same platform can be reported to Netlify's abuse team.
Last checked
La reputazione Edge-IP non è attribuita a questo dominio.
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 crypto-lii.netlify.app · checked Sep 8, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
crypto-lii.netlify.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
Sconosciuto→inactive
http_no_content
2→3
Raggiungibile→Non disponibile
0→2
Raggiungibile
No threat flag
View source3/89 engine detections
View sourcecrypto-lii.netlify.app
View sourcePage captured
View sourceListed 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 ↗
crypto-lii.netlify.app)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.