VirusTotal
1 / 92 engine detections
Abrir informetornadomixer.org: Dominio en listas de bloqueo, detectado por PhishDestroy el 2026-10-23. Riesgo: crítico (88/100). Registrador: Name.com. Estado: Último activo conocido. Alojamiento: Amazon.com. PhishDestroy envió 1 denuncia de abuso. VirusTotal: 1/92 motores lo marcan. No introduzcas credenciales ni conectes una billetera.
“Tornado - Cryptocurrency Mixer”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
The latest stored availability evidence still shows the domain reachable; 29 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Dominio en listas de bloqueo: tornadomixer.org — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 1/92 (CRDF); 2 external blocklist…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
1 / 92 engine detections
Abrir informeInforme de análisis
Abrir informe4 community references
Abrir informeprovider verdict: clean
Abrir informeSin amenazas marcadas
Abrir informeNo marcado como malicioso
Abrir informeLos resultados reflejan la hora de recopilación de cada fuente. Cero detecciones no garantizan la seguridad. Las referencias de OTX son publicaciones de la comunidad.
PhishDestroy threat report
PhishDestroy’s intake system classified the site as malicious because it presents itself as a cryptocurrency mixer, a service often linked to money‑laundering activities. The recorded page title on 2026-10-23 reads “Tornado – Cryptocurrency Mixer” and the page shows a “Mix Cryptocurrency” interface with deposit statistics. PhishDestroy first observed the domain on 2026-10-23, 45 days after its registration on 2026-09-08, and an HTTP 200 response was recorded on that date.
Cryptocurrency mixers pool funds from many users, shuffle them, and return the same amount to designated addresses, thereby obscuring the transaction trail. Operators typically charge a fee and may request wallet connections, creating opportunities to steal or lock users’ assets.
The intake AI flagged the page as malicious with high confidence, citing the mixer‑related content as a fraud indicator. VirusTotal recorded one malicious detection (CRDF) out of 92 engines on 2026-10-23. URLScan’s engine scoring marked the URL as malicious with a score of 85, while its overall verdict was clean on the same date. Google Safe Browsing reported no flag, OTX listed four pulses referencing the domain, and external blocklists MetaMask and SEAL both flagged it; PhishDestroy also lists the domain internally.
The domain was registered with Name.com on 2026-09-08 and is marked clientTransferProhibited. Hosting records show the site served from IP 98.84.224.111, an Amazon AWS node in the United States, and the HTTP headers indicate a Netlify front‑end. The TLS certificate, issued by Let’s Encrypt, was valid from 2026-09-08 to 2026-12-07 and covers both the apex and wildcard subdomains.
Avoid visiting the site or providing any wallet credentials; if a wallet was connected, monitor the associated accounts for unauthorized activity. Defenders should block tornadomixer.org at DNS or proxy level, log any connections to the recorded IPs, and add the domain to internal threat feeds.
No. PhishDestroy clasifica tornadomixer.org como Dominio en listas de bloqueo (riesgo: crítico, 88/100); se detectó por primera vez el 2026-10-23. VirusTotal: 1/92 motores lo marcan. Considera el sitio inseguro.
No. No conectes una billetera, no firmes mensajes ni apruebes tokens en tornadomixer.org. Los sitios de phishing piden aprobaciones (approve, setApprovalForAll, Permit2) que permiten al operador mover tus activos, y una transacción confirmada no se puede revertir.
Cambia todas las contraseñas que introdujiste allí y activa la autenticación en dos pasos. Si conectaste una billetera o firmaste algo, revoca las aprobaciones y mueve los fondos restantes a una billetera nueva; nunca compartas tu frase semilla. Ayuda paso a paso: guía de emergencia.
Última comprobación
La reputación de Edge-IP no se atribuye a este dominio.
dns1.p01.nsone.netdns2.p01.nsone.netdns3.p01.nsone.netdns4.p01.nsone.netsmtp.google.compriority 1La ubicación corresponde a la red IP.
ee26d7d17475b82519e0e85c654287378c5cc6b062c01c32ede17cd03fac7739*.tornadomixer.orgtornadomixer.orgMetadatos del certificado guardados. Las fechas del certificado sin zona horaria se muestran tal como se almacenaron. El cifrado del transporte no demuestra que el sitio sea de confianza.
Google PageSpeed Insights — auditoría de rendimiento móvil de tornadomixer.org · checked Oct 23, 2026
Metadatos de respuesta con marca de tiempo conservados por la canalización de recopilación local. Cada valor siguiente corresponde a la hora de archivado mostrada.
http://tornadomixer.org/https://tornadomixer.org/Cache-Control: public,max-age=0,must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8Server: NetlifyX-Powered-By: Next.js3809353public,max-age=0,must-revalidate"Netlify Durable"; hit; ttl=27726646gzip3240text/html; charset=utf-8Fri, 23 Oct 2026 01:29:43 GMT"8kojyym65g9b5"query=__nextDataReq|_rsc, header=x-nextjs-data|x-next-debug-logging|next-router-prefetch|next-router-segment-prefetch|next-router-state-tree|next-url|rsc|accept-encoding, cookie=__prerender_bypass|__next_preview_dataNetlifymax-age=31536000rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-EncodingnosniffTue, 20 Oct 2026 20:14:18 GMT1, 130001M5K61M54XB5MNP2BBH7CGXBWNext.jsValores conservados por el recopilador; los valores largos pueden acortarse durante la recopilación.
Una hora estimada describe una ventana de observación. No demuestra una acción del registrador ni el momento exacto en que un sitio dejó de estar disponible.
Observaciones almacenadas de la página, la red y los escáneres, agrupadas por fuente y hora de observación.
Observado: · Retrieved:
| Uuid | 01a16666-8d3d-74b1-8cd9-8c187cb78b6d |
|---|---|
| Final url | https://tornadomixer.org/ |
| Estado | 200 |
| Redirigido | https-only |
| Redirects | [
{
"to": "https://tornadomixer.org/",
"from": "http://tornadomixer.org/",
"status": 307
}
] |
| Ip | 98.84.224.111 |
| Ptr | ec2-98-84-224-111.compute-1.amazonaws.com |
| Contacted IP addresses | [
"98.84.224.111"
] |
| Asns | [
"14618"
] |
| Countries | [
"US"
] |
| Document hash | baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046 |
| Script hashes | [
"49cf866bf4d0282119e51835114325403f28e53fd0bccb63dde7ba3114a8e9fb",
"82d28975ef4120af4576e36df96453dca7465c104a3dc53aa1be2625e8ef685d",
"c0930af826f989eea00dbaca15c1e4b3d3609b7b0bc5416a661a4948d8c26515",
"7a3b5d6ac23f323b67a406c5541141f56821a28f18c0b1eb0336a53c8c99790d",
"34ed6abf4c6d0d1bb3dc56d3f133d2a5dbc3a3c89c791deab314e27143ac14ce",
"ce5d41ae3146e80a319e80274e6787046f8d2e67cc4f85d4703ea94d82fc9dca",
"a28004df24371c97caf4436a204659da088dbe231753a9cbdbbe4bf22779dfd9",
"932e33a2d78e4d190fcb54ac91da84710b38589695b18679a4aa6b11192c3749",
"4e73ef1381120a3bcc849a970152d3415e070d8051b8344a073e97b5ceca000d",
"3a946abd1ea019b60096464bfae1b83262816f25c1d4ee7829846b6158446042"
] |
| Globals | [
"__next_f",
"TURBOPACK",
"next",
"__webpack_hash__"
] |
| Tls | {
"san": [
"*.tornadomixer.org",
"tornadomixer.org"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "tornadomixer.org",
"protocol": "TLS 1.3",
"valid_to": "2026-12-07T17:35:31Z",
"valid_from": "2026-09-08T17:35:32Z"
} |
| Antigüedad del dominio en días | 44 |
| Apex age days | 44 |
| Tls age days | 44 |
| Días de validez TLS | 89 |
| Requests | 15 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 85,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Netlify",
"content-type": "text/html; charset=utf-8",
"x-powered-by": "Next.js",
"strict-transport-security": "max-age=31536000",
"x-content-type-options": "nosniff"
} |
Observado: · Retrieved:
| Uuid | 87f65aa7-a853-4452-982b-d102f71c79f1 |
|---|---|
| Final url | https://tornadomixer.org/ |
| Estado | 200 |
| History | [
{
"url": "https://tornadomixer.org/",
"status": 200
}
] |
| DOM structure hash | 63b72085c7d039cd6e5571735f27ecc966364e8244c4e0195ed0176b628feecd |
| Document hash | baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046 |
| Radar rank | {
"bucket": ">200000"
} |
| Registros DNS | [
{
"name": "tornadomixer.org",
"type": "A",
"value": "13.52.188.95"
},
{
"name": "tornadomixer.org",
"type": "A",
"value": "52.52.192.191"
}
] |
| DNSSEC válido | false |
| Ip | 13.52.188.95 |
| Ficha de registro | {
"registrar": "Name.com, Inc.",
"created": "2026-09-08T16:20:49Z",
"updated": "2026-09-13T16:21:42Z",
"expires": "2027-09-08T16:20:49Z",
"nameservers": [
"dns1.p01.nsone.net",
"dns2.p01.nsone.net",
"dns3.p01.nsone.net",
"dns4.p01.nsone.net"
]
} |
Observado: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 1,
"suspicious": 0,
"undetected": 38
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious"
} |
| Reputation | 0 |
| Registrador | Name.com, Inc. |
| Creado | 2026-09-08T16:20:49Z |
| Expires | 2027-09-08T16:20:49Z |
| Updated | 2026-09-13T16:21:42Z |
| Visto por primera vez | 2026-09-22T11:50:29Z |
| Registros DNS | [
{
"ttl": 3600,
"type": "NS",
"value": "dns2.p01.nsone.net"
},
{
"ttl": 120,
"type": "A",
"value": "98.84.224.111"
},
{
"ttl": 3600,
"type": "NS",
"value": "dns1.p01.nsone.net"
},
{
"ttl": 120,
"type": "A",
"value": "18.208.88.157"
},
{
"ttl": 3600,
"type": "TXT",
"value": "google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k"
},
{
"ttl": 3600,
"type": "MX",
"value": "smtp.google.com",
"priority": 1
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 include:_spf.google.com ~all"
},
{
"ttl": 3600,
"type": "NS",
"value": "dns3.p01.nsone.net"
},
{
"ttl": 3600,
"type": "NS",
"value": "dns4.p01.nsone.net"
},
{
"ttl": 3600,
"type": "SOA",
"rname": "domains+netlify.netlify.com",
"value": "dns1.p01.nsone.net"
}
] |
| Dns at | 2026-10-23T02:11:17Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"*.tornadomixer.org",
"tornadomixer.org"
],
"issuer": "Let's Encrypt / YE2",
"serial": "634ed360528ab3e9dfa8b516ad2b369e533",
"sha256": "ee26d7d17475b82519e0e85c654287378c5cc6b062c01c32ede17cd03fac7739",
"subject": "tornadomixer.org",
"valid_to": "2026-12-07T17:35:31Z",
"valid_from": "2026-09-08T17:35:32Z"
} |
| Ficha de registro | {
"registrar": "Name.com, Inc.",
"registrar_iana_id": "625",
"registrar_url": "http://www.name.com",
"created": "2026-09-08T16:20:49Z",
"updated": "2026-09-13T16:21:42Z",
"expires": "2027-09-08T16:20:49Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"dns1.p01.nsone.net",
"dns2.p01.nsone.net",
"dns3.p01.nsone.net",
"dns4.p01.nsone.net"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-09-08T16:20:49Z",
"last changed": "2026-09-13T16:21:42Z",
"registration": "2026-09-08T16:20:49Z",
"registrar expiration": "2027-09-08T16:20:49Z",
"last update of RDAP database": "2026-09-13T16:21:42Z"
}
} |
| Mail configuration | {
"mx": [
"smtp.google.com"
],
"spf": "v=spf1 include:_spf.google.com ~all",
"dkim": [
"google"
],
"dkim_bits": 2048,
"providers": [
"Google Workspace"
],
"spf_lookups": 1
} |
|---|---|
| Registros CAA | {
"domain": "tornadomixer.org"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-10-23T01:29:40Z",
"first": "2026-10-23T01:29:40Z",
"changes": 0,
"days_archived": 1,
"avg_page_bytes": 4326
} |
| Título de la página y metadatos | {
"title": "Tornado - Cryptocurrency Mixer",
"description": "Generated by create next app"
} |
| Formularios y contenido mixto | {
"third_party_scripts": 0
} |
| Estado | {
"up": true,
"code": 200,
"timings": {
"dns": 6,
"tls": 112,
"wait": 275,
"connect": 14,
"download": 8
},
"response_ms": 415
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_128_GCM_SHA256",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
80,
443
]
} |
| Carbon | {
"bytes": 12067,
"co2_grams": 0.0004,
"cleaner_than": 68
} |
| Dns server | {
"ns": [
{
"ip": "198.51.44.1",
"host": "dns1.p01.nsone.net"
},
{
"ip": "198.51.45.1",
"host": "dns2.p01.nsone.net"
},
{
"ip": "198.51.44.65",
"host": "dns3.p01.nsone.net"
},
{
"ip": "198.51.45.65",
"host": "dns4.p01.nsone.net"
}
],
"zone": "tornadomixer.org"
} |
| Location | {
"ip": "63.176.8.218",
"asn": "16509",
"org": "Amazon.com",
"city": "Frankfurt",
"country": "DE"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE2",
"subject": "tornadomixer.org"
} |
| Registros DNS | {
"A": [
"35.157.26.135",
"63.176.8.218"
],
"MX": [
"{\"exchange\": \"smtp.google.com\", \"priority\": 1}"
],
"NS": [
"dns1.p01.nsone.net",
"dns4.p01.nsone.net",
"dns3.p01.nsone.net",
"dns2.p01.nsone.net"
],
"SOA": "{\"nsname\": \"dns1.p01.nsone.net\", \"hostmaster\": \"domains+netlify.netlify.com\", \"serial\": 1788884447, \"refresh\": 43200, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 3600}",
"TXT": [
"v=spf1 include:_spf.google.com ~all",
"google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"header": "max-age=31536000",
"message": "HSTS header does not include all subdomains."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": false,
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": false,
"strictTransportPolicy": "max-age=31536000",
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "35.157.26.135",
"family": 4
} |
| Redirects | {
"chain": [
"https://tornadomixer.org"
]
} |
| Ficha de registro | {
"registrar": "Name.com, Inc.",
"created": "2026-09-08T16:20:49Z",
"updated": "2026-09-13T16:21:42Z",
"expires": "2027-09-08T16:20:49Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"dns1.p01.nsone.net",
"dns2.p01.nsone.net",
"dns3.p01.nsone.net",
"dns4.p01.nsone.net"
]
} |
| HTTP headers | {
"headers": {
"server": "Netlify",
"content-type": "text/html; charset=utf-8",
"x-powered-by": "Next.js",
"strict-transport-security": "max-age=31536000",
"x-content-type-options": "nosniff"
}
} |
Cambios fechados conservados por el monitor y los recopiladores de fuentes. Las observaciones más recientes aparecen primero; el estado de una fuente no prueba una retirada.
Desconocido→live_content
content_served
0→1
Accesible
4 community references
Ver fuenteSin amenazas marcadas
Ver fuente1/92 engine detections
Ver fuentePD-20261023-30722B
Page captured
Ver fuentetornadomixer.org
Ver fuenteCompara lo que reciben un navegador y un rastreador, y comprueba si hay enrutamiento de tráfico de Keitaro.
tornadomixer.org
PD-20261023-30722B Recipient: abuse@name.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.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Seleccione 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
Elige los pasos que correspondan a lo que compartiste. Guarda una copia de este informe junto con tus propios registros.
Deja de usar el sitio sospechoso. Abre el servicio real desde su aplicación oficial o una dirección en la que ya confíes.
Guarda los correos originales, recibos, mensajes y capturas de pantalla en un lugar seguro. Una cronología objetiva ayuda a la autoridad receptora a entender lo ocurrido. IC3 evidence guidance ↗
tornadomixer.org)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
Una denuncia no garantiza la recuperación de los fondos ni una investigación, pero unos datos de transacción precisos y aportados con rapidez pueden ayudar a las autoridades y a los proveedores de servicios a rastrear el incidente.
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.
Este informe combina capturas de página guardadas, datos de registro y de red, resultados de escáneres y el historial de denuncias de PhishDestroy. Cada fuente conserva su propia fecha de observación. Abre el informe de una fuente para consultar el resultado original.
El análisis asistido por AI se redactó el . Describe las evidencias disponibles en ese momento; las comprobaciones posteriores de las fuentes pueden variar.
Una captura documenta lo que se mostraba. Un resultado de escáner registra la evaluación de ese proveedor en el momento de su comprobación. Ni un certificado válido ni un resultado sin detecciones garantizan la seguridad.