VirusTotal
17 / 92 engine detections
Abrir informebitqttrade.net: Phishing, detectado por PhishDestroy el 2026-10-23. Riesgo: crítico (100/100). Registrador: Dynadot. Estado: Último activo conocido. Alojamiento: Omegatech LTD. PhishDestroy envió 1 denuncia de abuso. VirusTotal: 17/92 motores lo marcan. No introduzcas credenciales ni conectes una billetera.
“Bitqt”
Phishing: bitqttrade.net — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 17/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, DNS8)…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
17 / 92 engine detections
Abrir informe3 det.
Abrir informeMalicioso
Abrir informe5 community references
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 added bitqttrade.net to its internal blocklist after automated analysis flagged the site as suspicious. The recorded page title was “Bitqt”. The domain was first seen by PhishDestroy on 2026-10-23 and returned an HTTP 200 response on that date. No specific malicious behavior was observed in the page content.
The classification is based on the presence of multiple security‑vendor detections that commonly indicate phishing, malware distribution, or fraudulent financial services. No concrete mechanism such as credential capture or wallet interaction was observed on the page. Consequently, the listing reflects a general risk of a potentially deceptive crypto‑related service rather than a confirmed attack vector.
VirusTotal recorded 14 malicious and 3 suspicious detections from 92 engines on 2026-10-23 (analysis date 2026-10-17), totaling 17 detections. Google Safe Browsing checked on 2026-10-23 and did not flag the domain. urlscan.io’s engine verdict marked the site malicious with a score of 93 on 2026-10-23, while its overall verdict was neutral. Cloudflare Radar flagged the domain as malicious and categorized it under malware on 2026-10-23. OTX listed five pulses mentioning the domain as of 2026-10-23. PhishDestroy’s internal blocklist included the domain, whereas external blocklists returned zero hits on the same day.
The domain was registered with Dynadot Inc on 2026-06-24, giving it an age of about 120 days at the time of observation. The recorded IP was 158.94.210.119 and the associated network name was Omegatech LTD, located in the Netherlands. The certificate check found a Let's Encrypt certificate valid from 2026-09-11 to 2026-12-10 covering the apex and wildcard subdomains. The scan observed open ports 22, 80, and 443, and the authoritative nameservers were ns1.dyna-ns.net and ns2.dyna-ns.net.
Visitors should avoid entering credentials, cryptocurrency addresses, or personal data on the site; if any such information was submitted, change the associated passwords and monitor accounts for unusual activity. Security teams can add bitqttrade.net to their blocklists and review network logs for connections to the recorded IP 158.94.210.119. No wallet‑related remediation is advised because no wallet interaction was observed.
Observaciones almacenadas de la página, la red y los escáneres, agrupadas por fuente y hora de observación.
Observado: · Retrieved:
| Uuid | 01a167e6-3bcf-75a3-a2d0-dfd41b899287 |
|---|---|
| Final url | https://bitqttrade.net/ |
| Estado | 200 |
| Redirigido | https-only |
| Redirects | [
{
"to": "https://bitqttrade.net/",
"from": "http://bitqttrade.net/",
"status": 307
}
] |
| Ip | 158.94.210.119 |
| Contacted IP addresses | [
"158.94.210.119"
] |
| Asns | [
"202412"
] |
| Countries | [
"NL"
] |
| Document hash | b788dd19cdd409563bc02099d15bea6d3936263cbc271908cfedfb7dade32242 |
| Script hashes | [
"8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
] |
| Globals | [
"__dclq",
"__dclOrig",
"__dclFlush",
"__smsCheckBeforeSubmit",
"__isSmsEnabled",
"__isSmsVerified",
"intlTelInput",
"navToggle",
"navMenu",
"langBtn",
"langDropdown"
] |
| Cookies | [
"connect.sid"
] |
| Tls | {
"san": [
"*.bitqttrade.net",
"bitqttrade.net"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "bitqttrade.net",
"protocol": "TLS 1.3",
"valid_to": "2026-12-10T13:48:10Z",
"valid_from": "2026-09-11T13:48:11Z"
} |
| Antigüedad del dominio en días | 120 |
| Apex age days | 120 |
| Tls age days | 41 |
| Días de validez TLS | 89 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 93,
"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 | c38026d5-f7fe-41c3-9aca-14e89444d1e8 |
|---|---|
| Final url | https://bitqttrade.net/ |
| Estado | 200 |
| History | [
{
"url": "https://bitqttrade.net/",
"status": 200
}
] |
| DOM structure hash | b3ef19008dff0fd4889872b774640a6fe9b5cf3f0d2aaa746990764bd8cb9e24 |
| Document hash | 3bd9a3db936e15ade35f9d79bf24391377932e3d5bf6acd9829562e257242a1d |
| Url risks | [
"Scam"
] |
| Riesgos del dominio | [
"Scam",
"Security threats",
"Malware",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| Registros DNS | [
{
"name": "bitqttrade.net",
"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-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
Observado: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 43,
"malicious": 14,
"suspicious": 3,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "suspicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Fortinet": "phishing",
"Netcraft": "malicious",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrador | Dynadot Inc |
| Creado | 2026-06-24T10:39:00Z |
| Expires | 2027-06-24T10:39:00Z |
| Updated | 2026-08-13T12:43:33Z |
| Visto por primera vez | 2026-06-24T11:26:29Z |
| Registros DNS | [
{
"ttl": 300,
"type": "A",
"value": "158.94.210.119"
},
{
"ttl": 300,
"type": "NS",
"value": "ns2.dyna-ns.net"
},
{
"ttl": 300,
"type": "SOA",
"rname": "hostmaster.bitqttrade.net",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "NS",
"value": "ns1.dyna-ns.net"
}
] |
| Dns at | 2026-10-17T11:51:27Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"*.bitqttrade.net",
"bitqttrade.net"
],
"issuer": "Let's Encrypt / YE1",
"serial": "57e8a56990ef7a6893376020c92432bd418",
"sha256": "b7d8c37a21d82f6ab1231b48e3bc05c6647049fa8d73e57b198760e7e0524bee",
"subject": "bitqttrade.net",
"valid_to": "2026-12-10T13:48:10Z",
"valid_from": "2026-09-11T13:48:11Z"
} |
| Ficha de registro | {
"registrar": "Dynadot Inc",
"registrar_iana_id": "472",
"registrar_url": "http://www.dynadot.com",
"created": "2026-06-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-06-24T10:39:00Z",
"last changed": "2026-09-11T14:46:53Z",
"registration": "2026-06-24T10:39:00Z",
"registrar expiration": "2027-06-24T10:39:00Z",
"last update of RDAP database": "2026-10-16T07:18:29Z"
}
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Registros CAA | {
"domain": "bitqttrade.net"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-23T08:38:53Z",
"first": "2026-10-07T11:57:58Z",
"changes": 1,
"days_archived": 2,
"scans_per_day": 0.06,
"avg_page_bytes": 18209
} |
| Crawler rules | {
"agents": [
"*"
],
"present": true,
"sitemaps": [
"https://bitqttrade.net/sitemap.xml"
]
} |
| Sitemap | {
"present": true,
"url_count": 5
} |
| Título de la página y metadatos | {
"title": "Algorithmic Precision & Real-Time Insights | Bitqt",
"robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
"description": "For ambitious investors seeking smarter market moves: Bitqt offers an AI-Powered Trading Platform built to automate analysis and scale your crypto strategy globally.",
"canonicalUrl": "https://bitqttrade.net/"
} |
| Formularios y contenido mixto | {
"third_party_scripts": 0
} |
| Estado | {
"up": true,
"code": 200,
"timings": {
"dns": 283,
"tls": 93,
"wait": 87,
"connect": 69,
"download": 161
},
"response_ms": 693
} |
| 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": 95501,
"co2_grams": 0.0035,
"cleaner_than": 23
} |
| Dns server | {
"ns": [
{
"ip": "162.159.24.5",
"host": "ns2.dyna-ns.net"
},
{
"ip": "162.159.26.92",
"host": "ns1.dyna-ns.net"
}
],
"zone": "bitqttrade.net"
} |
| Location | {
"ip": "158.94.210.119",
"asn": "202412",
"org": "Omegatech LTD",
"city": "Amsterdam",
"country": "NL"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "bitqttrade.net"
} |
| Registros DNS | {
"A": [
"158.94.210.119"
],
"NS": [
"ns2.dyna-ns.net",
"ns1.dyna-ns.net"
],
"SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.bitqttrade.net\", \"serial\": 2026091102, \"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://bitqttrade.net"
]
} |
| Subdominios | {
"count": 1,
"subdomains": [
"www.bitqttrade.net"
]
} |
| Page links | {
"internal_count": 26
} |
| Ficha de registro | {
"registrar": "Dynadot Inc",
"created": "2026-06-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"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 bitqttrade.net como Phishing (riesgo: crítico, 100/100); se detectó por primera vez el 2026-10-23. VirusTotal: 17/92 motores lo marcan. Considera el sitio inseguro.
No. No conectes una billetera, no firmes mensajes ni apruebes tokens en bitqttrade.net. 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.
b7d8c37a21d82f6ab1231b48e3bc05c6647049fa8d73e57b198760e7e0524bee*.bitqttrade.netbitqttrade.netMetadatos 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.bitqttrade.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — auditoría de rendimiento móvil de bitqttrade.net · 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://bitqttrade.net/https://bitqttrade.net/Cache-Control: no-cache, no-store, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8X-Powered-By: Expressh3=":443"; ma=2592000no-cache, no-store, must-revalidategzip416text/html; charset=utf-8Fri, 23 Oct 2026 08:39:40 GMTsame-originAccept-Encoding1.1 CaddynosniffExpressValores 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.
Compara lo que reciben un navegador y un rastreador, y comprueba si hay enrutamiento de tráfico de Keitaro.
alive_content: raw=ok; http=200; via=https_proxy
bitqttrade.net
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
5 community references
Ver fuenteSin amenazas marcadas
Ver fuente17/92 engine detections
Ver fuentePD-20261023-E2020A
bitqttrade.net
Ver fuentePage captured
Ver fuentePD-20261023-E2020A Recipient: abuse@omegatech.sc Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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 ↗
bitqttrade.net)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.