VirusTotal
15 / 92 engine detections
Abrir informebtcpurelogbtccentrix.com: Phishing, detectado por PhishDestroy el 2026-10-23. Riesgo: crítico (100/100). Registrador: Dynadot. Estado: Último activo conocido. Alojamiento: Omegatech LTD. VirusTotal: 15/92 motores lo marcan. No introduzcas credenciales ni conectes una billetera.
“BTC-PureLog / BTC-Centrix: Algorithmic Trading Platform”
Phishing: btcpurelogbtccentrix.com — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 15/92 (alphaMountain.ai, BitDefender, CRDF, DNS8…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
15 / 92 engine detections
Abrir informeInforme de análisis
Abrir informe4 community references
Abrir informeInforme de análisis
Abrir informeSin amenazas marcadas
Abrir informeCaptura de la página
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 listed btcpurelogbtccentrix.com as a suspicious domain based on automated risk scoring and external detections. The recorded page title was “BTC-PureLog / BTC-Centrix: Algorithmic Trading Platform”. The domain was first seen by PhishDestroy on 2026-10-23 and returned an HTTP 200 response on that date. The recorded title, HTTP status and TLS certificate are historical observations and do not prove current availability.
No specific malicious mechanism was observed on the page, but the combination of malware, phishing and scam tags suggests the site could be used to lure visitors into providing credentials, financial details, or to download malicious payloads. Fake‑exchange pages often promise high‑frequency trading or AI‑driven profits to induce deposits, but without concrete evidence we cannot confirm that behavior here.
VirusTotal scanned the domain on 2026-10-19 and reported 15 detections from 92 engines, including malicious labels from alphaMountain.ai and BitDefender and phishing or suspicious tags from several vendors. Google Safe Browsing checked on 2026-10-23 and did not flag the URL. OTX listed four pulses referencing the domain as of 2026-10-23. PhishDestroy’s internal blocklist marked the domain as blocked on 2026-10-23. Urlscan.io captured the site on 2026-10-23, where its engine verdict scored it malicious with a 99 % confidence score, while its overall community verdict was non‑malicious. Cloudflare Radar also flagged the URL as malicious with a malware category on the same day.
The domain was registered with Dynadot Inc on 2026-06-12, giving it an age of 132 days at the time of observation. It was recorded to resolve to IP 158.94.210.119, which was listed as belonging to Omegatech LTD in the Netherlands. The site used a Let's Encrypt TLS certificate valid from 2026-08-28 to 2026-11-26 and responded on ports 22, 80 and 443.
Visitors should avoid entering any login credentials, personal data or financial information on this site and should change passwords if they suspect they may have been entered. Organizations should block the domain at the firewall, monitor DNS logs for queries to btcpurelogbtccentrix.com, and treat any related traffic as potentially malicious.
Observaciones almacenadas de la página, la red y los escáneres, agrupadas por fuente y hora de observación.
Observado: · Retrieved:
| Uuid | 01a169c3-fe06-7283-a623-8597f4fc7126 |
|---|---|
| Final url | https://btcpurelogbtccentrix.com/ |
| Estado | 200 |
| Redirigido | https-only |
| Redirects | [
{
"to": "https://btcpurelogbtccentrix.com/",
"from": "http://btcpurelogbtccentrix.com/",
"status": 307
}
] |
| Ip | 158.94.210.119 |
| Contacted IP addresses | [
"158.94.210.119"
] |
| Asns | [
"202412"
] |
| Countries | [
"NL"
] |
| Document hash | 5eeb2924731c00d7194a98778e8057e6308d56e1b12f7b5ab44a0e3662e41642 |
| Script hashes | [
"8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
] |
| Globals | [
"__dclq",
"__dclOrig",
"__dclFlush",
"handleResize",
"__smsCheckBeforeSubmit",
"__isSmsEnabled",
"__isSmsVerified",
"intlTelInput",
"navToggle",
"navWrapper",
"mobileLangGrid",
"langToggle",
"langDropdown"
] |
| Cookies | [
"connect.sid"
] |
| Tls | {
"san": [
"btcpurelogbtccentrix.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "btcpurelogbtccentrix.com",
"protocol": "TLS 1.3",
"valid_to": "2026-11-26T12:55:50Z",
"valid_from": "2026-08-28T12:55:51Z"
} |
| Antigüedad del dominio en días | 132 |
| Apex age days | 132 |
| Tls age days | 56 |
| Días de validez TLS | 89 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
} |
Observado: · Retrieved:
| Uuid | b505196a-dec1-488b-a92a-21cb34250d63 |
|---|---|
| Final url | https://btcpurelogbtccentrix.com/ |
| Estado | 200 |
| History | [
{
"url": "https://btcpurelogbtccentrix.com/",
"status": 200
}
] |
| DOM structure hash | 21e0b1417b46b239e1bb4ea336569f9b959ede0a756861626b29cae66f95d6eb |
| Document hash | 3d60202e97464bc5fc911c51f147b53845ac0d59565668c1b701a324ac92f58e |
| Phishing v2 | [
"phishing"
] |
| Url risks | [
"Scam"
] |
| Riesgos del dominio | [
"Scam",
"Security threats",
"Malware",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| Registros DNS | [
{
"name": "btcpurelogbtccentrix.com",
"type": "A",
"value": "158.94.210.119"
}
] |
| DNSSEC válido | false |
| Ip | 158.94.210.119 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Ficha de registro | {
"registrar": "Dynadot Inc",
"created": "2026-06-12T22:25:55Z",
"updated": "2026-08-13T12:24:43Z",
"expires": "2027-06-12T22:25:55Z",
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
Observado: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 11,
"suspicious": 4,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "suspicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"Fortinet": "spam",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "malicious",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrador | Dynadot Inc |
| Creado | 2026-06-12T22:25:55Z |
| Expires | 2027-06-12T22:25:55Z |
| Updated | 2026-08-13T12:24:43Z |
| Visto por primera vez | 2026-06-12T23:08:45Z |
| Registros DNS | [
{
"ttl": 300,
"type": "NS",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "A",
"value": "158.94.210.119"
},
{
"ttl": 300,
"type": "NS",
"value": "ns2.dyna-ns.net"
},
{
"ttl": 300,
"type": "SOA",
"rname": "hostmaster.btcpurelogbtccentrix.com",
"value": "ns1.dyna-ns.net"
}
] |
| Dns at | 2026-10-19T15:51:43Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"btcpurelogbtccentrix.com"
],
"issuer": "Let's Encrypt / YE1",
"serial": "6a28f3bbf44ab1c84a4cbdf4931bee1332f",
"sha256": "cc9869a6af72874bd0822fd85914583bc1cff16e5723b2d20e1213e8c8ee0f4a",
"subject": "btcpurelogbtccentrix.com",
"valid_to": "2026-11-26T12:55:50Z",
"valid_from": "2026-08-28T12:55:51Z"
} |
| Ficha de registro | {
"registrar": "Dynadot Inc",
"registrar_iana_id": "472",
"registrar_url": "http://www.dynadot.com",
"created": "2026-06-12T22:25:55Z",
"updated": "2026-08-13T12:24:43Z",
"expires": "2027-06-12T22:25:55Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-06-12T22:25:55Z",
"last changed": "2026-08-28T08:24:18Z",
"registration": "2026-06-12T22:25:55Z",
"registrar expiration": "2027-06-12T22:25:55Z",
"last update of RDAP database": "2026-10-16T07:15:19Z"
}
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Registros CAA | {
"domain": "btcpurelogbtccentrix.com"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-23T17:19:14Z",
"first": "2026-10-12T05:36:16Z",
"changes": 1,
"days_archived": 2,
"scans_per_day": 0.09,
"avg_page_bytes": 19177
} |
| Crawler rules | {
"agents": [
"*"
],
"present": true,
"sitemaps": [
"https://btcpurelogbtccentrix.com/sitemap.xml"
]
} |
| Sitemap | {
"present": true,
"url_count": 5
} |
| Título de la página y metadatos | {
"title": "BTC-PureLog / BTC-Centrix: Algorithmic Trading Platform",
"robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
"description": "Execute trades with institutional-grade precision. BTC-PureLog / BTC-Centrix delivers an AI-powered trading system across 194+ global markets with empirically validated, real-time performance.",
"canonicalUrl": "https://btcpurelogbtccentrix.com/"
} |
| Trackers | {
"requests": 55,
"trackers": [
{
"name": "Cloudflare",
"company": "Cloudflare",
"country": "US",
"category": "Hosting",
"requests": 1
},
{
"name": "jsDelivr",
"company": "jsDelivr",
"category": "Hosting",
"requests": 4
}
]
} |
| Formularios y contenido mixto | {
"third_party_scripts": 0
} |
| Estado | {
"up": true,
"code": 200,
"timings": {
"dns": 533,
"tls": 76,
"wait": 141,
"connect": 66,
"download": 196
},
"response_ms": 1012
} |
| 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": [
22,
80,
443
]
} |
| Carbon | {
"bytes": 104328,
"co2_grams": 0.0038,
"cleaner_than": 21
} |
| Dns server | {
"ns": [
{
"ip": "162.159.25.5",
"host": "ns2.dyna-ns.net"
},
{
"ip": "162.159.26.92",
"host": "ns1.dyna-ns.net"
}
],
"zone": "btcpurelogbtccentrix.com"
} |
| Cookies | {
"cookies": [
{
"name": "cf-c",
"http_only": true,
"same_site": "Lax"
},
{
"name": "__cf_clicked"
},
{
"name": "ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog",
"secure": true,
"same_site": "Lax"
}
]
} |
| Location | {
"ip": "158.94.210.119",
"asn": "202412",
"org": "Omegatech LTD",
"city": "Amsterdam",
"country": "NL"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "btcpurelogbtccentrix.com"
} |
| Registros DNS | {
"A": [
"158.94.210.119"
],
"NS": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.btcpurelogbtccentrix.com\", \"serial\": 2026082801, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"message": "Site does not serve any HSTS headers."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": "same-origin",
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": false,
"strictTransportPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "158.94.210.119",
"family": 4
} |
| Redirects | {
"chain": [
"https://btcpurelogbtccentrix.com"
]
} |
| Subdominios | {
"count": 1,
"subdomains": [
"www.btcpurelogbtccentrix.com"
]
} |
| Page links | {
"internal_count": 31
} |
| Ficha de registro | {
"registrar": "Dynadot Inc",
"created": "2026-06-12T22:25:55Z",
"updated": "2026-08-13T12:24:43Z",
"expires": "2027-06-12T22:25:55Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
| HTTP headers | {
"headers": {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
}
} |
No. PhishDestroy clasifica btcpurelogbtccentrix.com como Phishing (riesgo: crítico, 100/100); se detectó por primera vez el 2026-10-23. VirusTotal: 15/92 motores lo marcan. Considera el sitio inseguro.
No. No conectes una billetera, no firmes mensajes ni apruebes tokens en btcpurelogbtccentrix.com. 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.
ns1.dyna-ns.netns2.dyna-ns.netLa ubicación corresponde a la red IP.
cc9869a6af72874bd0822fd85914583bc1cff16e5723b2d20e1213e8c8ee0f4abtcpurelogbtccentrix.comMetadatos 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.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.btcpurelogbtccentrix.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — auditoría de rendimiento móvil de btcpurelogbtccentrix.com · checked Oct 23, 2026
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.
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.
Accesible
4 community references
Ver fuenteSin amenazas marcadas
Ver fuente15/92 engine detections
Ver fuentebtcpurelogbtccentrix.com
Ver fuentePage captured
Ver fuenteCompara lo que reciben un navegador y un rastreador, y comprueba si hay enrutamiento de tráfico de Keitaro.
btcpurelogbtccentrix.com
Los dominios de la lista reciben al menos una denuncia de abuso; esta entrada no tiene un historial de notificaciones conservado.
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
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 ↗
btcpurelogbtccentrix.com)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.