VirusTotal
3 / 89 engine detections
Abrir informeDominio en listas de bloqueo: velora.icu — Contenido no disponible. Resumen de las pruebas: VirusTotal 3/89 (alphaMountain.ai, Forcepoint ThreatSeeker…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
3 / 89 engine detections
Abrir informe2 community references
Abrir informeprovider verdict: clean
Abrir informeNo threat flag
Abrir informeResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
velora.icu is a domain on the PhishDestroy blocklist that we first saw on 2026-09-10. No impersonated brand or page content is tied to it, so the specific scheme behind it has not been identified. The site went offline on 2026-09-10, the same day we first saw it, and its DNS was still inactive when we last checked on 2026-10-19.
With no captured page content, the evidence does not show which scheme velora.icu ran. It does show that three independent security vendors judged the domain malicious or risky, and that it was dropped from DNS the same day it surfaced. Short, quiet lifespans like this are common with throwaway domains that briefly host lures for logins, seed phrases or crypto payments. Anyone who reached this site through an unsolicited link, an ad or a direct message should assume it was not legitimate.
On 2026-09-10, VirusTotal showed 3 of 89 engines flagging the domain: alphaMountain.ai, Forcepoint ThreatSeeker and SOCRadar. That is a low count, but it comes from three unrelated threat-intelligence sources reaching the same conclusion on their own. The domain also appears in 2 AlienVault OTX pulses, which means other researchers have grouped it with tracked threat activity. Among the blocklists we check, only PhishDestroy currently lists it.
The domain was registered on 2026-05-04 through Fewmoretaps OU d/b/a Trustname.com, about four months before it came to our attention. A gap like that often means the name was held in reserve and activated later, rather than registered on the spot for one campaign. No hosting network was identifiable because the domain no longer resolves.
Because the domain is down, the main risk now is to anyone who used it while it was live. If you entered a password there, change it everywhere you reused it and turn on app-based two-factor authentication. If you typed in a seed phrase or private key, treat that wallet as compromised and move any remaining funds to a new wallet. If you sent a payment, keep the transaction details and report them to your exchange or local authorities. Defenders should block velora.icu at DNS and proxy level and search their logs for past lookups, since the name could be reactivated.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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.
velora.icu
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
Desconocido→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
2→3
Accesible→No disponible
2 community references
View sourceNo threat flag
View source3/89 engine detections
View sourcevelora.icu
View source⚠️ ESCALATION #1 (0h active): Phishing - velora[.]icu
PD-1788908006-velora.icu Recipient: abuse@trustname.com Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
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 ↗
velora.icu)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
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
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de 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.