VirusTotal
5 / 92 engine detections
Abrir informedasco.kz: Suplantación de Facebook, detectado por PhishDestroy el 2026-10-10. Riesgo: crítico (88/100). Estado: Último activo conocido. Alojamiento: Hoster-ALM LLP "Kompaniya Hoster.KZ", KZ. PhishDestroy envió 1 denuncia de abuso. VirusTotal: 5/92 motores lo marcan. No introduzcas credenciales ni conectes una billetera.
“Dasco Group”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hoster.kz.
The latest stored availability evidence still shows the domain reachable; 11 days 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.
Suplantación de Facebook: dasco.kz — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 5/92 (alphaMountain.ai, Forcepoint ThreatSeeker…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
5 / 92 engine detections
Abrir informe2 det.
Abrir informe37 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
dasco.kz is an impersonation phishing page that presents itself under the title "Dasco Group", borrowing that company's identity to win the trust of its customers, partners and anyone searching for it. PhishDestroy first flagged the domain on 2026-10-10. When last checked on 2026-10-19, the site was still online and its content was being served behind a protection layer, so the threat remains active.
Brand-impersonation sites copy the name and look of a real business so that visitors believe they are on the genuine company's portal. Here the "Dasco Group" title does that job. A visitor arriving from a search result, an email or a message is then asked to log in, submit personal or business details, or make a payment. Anything entered goes straight to the operators, who can reuse stolen credentials, run follow-up fraud in the company's name, or keep payments that never reach the real business.
Five of 92 engines on VirusTotal flag the domain as of 2026-10-16: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and URLQuery. That is a modest count, but these vendors work independently of each other and of PhishDestroy, which lists the domain on its own blocklist. The domain also appears in 37 AlienVault OTX pulses, which shows that other researchers are tracking it as a threat indicator.
The site resolves to 93.115.14.8 on the network of Hoster-ALM LLP "Kompaniya Hoster.KZ" in Kazakhstan. Local hosting fits a .kz domain and helps it pass as a domestic company site. It uses a free Let's Encrypt certificate, so the padlock in the browser only means the connection is encrypted. It does not prove the site belongs to Dasco Group.
If you entered a username and password on this page, change that password at once on the real service and on any other account where you reused it, and turn on two-factor authentication. If you sent a payment or card details, contact your bank to dispute the charge and block the card. Verify any invoice or request that came through this site using contact details you already trust. Report the incident to the genuine Dasco Group so it can warn its clients. Defenders should block dasco.kz at DNS, proxy and email gateways, search logs for past visits or form submissions, and treat any credentials tied to those sessions as compromised.
Observaciones almacenadas de la página, la red y los escáneres, agrupadas por fuente y hora de observación.
Observado: · Retrieved:
| Uuid | 01a127d1-136b-7420-92fc-2e8612db2a57 |
|---|---|
| Final url | https://dasco.kz/ |
| Estado | 200 |
| Redirigido | https-only |
| Redirects | [
{
"to": "https://dasco.kz/",
"from": "http://dasco.kz/",
"status": 307
}
] |
| Ip | 93.115.14.8 |
| Ptr | acloud-2.hoster.kz |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.14.94",
"142.250.154.95",
"2a00:1450:4001:c0f::5f",
"93.115.14.8"
] |
| Asns | [
"15169",
"202958"
] |
| Countries | [
"US",
"DE",
"KZ"
] |
| Linked domains | [
"survey.dasco.kz",
"www.youtube.com",
"www.instagram.com",
"kz.linkedin.com",
"t.me",
"www.tiktok.com",
"www.facebook.com"
] |
| Social | [
"https://www.youtube.com/@DASCO_GROUP",
"https://www.instagram.com/dasco.kz",
"https://t.me/dascolight",
"https://www.tiktok.com/@dasco.group",
"https://www.facebook.com/dascoconsulting"
] |
| Document hash | 6eb3c705a6edbb96cc455b1e59bed5d8180a7888b1aaf308ff036d5e3d3c2310 |
| Script hashes | [
"d949f1c3687aedadcedac85261865f29b17cd273997e7f6b2bfc53b2f9d4c4dd",
"35f4f974f4b2bcd44da73963347f8952e341f83909e4498227d4e26b98f66f0d",
"086c56ce48d2e3c5884a54e3c1aa8c65d2c595f0cd634716eda2b91066600bda",
"99aaf7045a5c801db73f65f4108f8ef0893178c0fb726b70d986641845588ec1",
"fc774906082b59dedcfc55b8ef127783b6d056578ff4586a8ebbdb81bbe286f1",
"5083905862c2b7aa8a84c4f2313d359d2288fb25fbe1ff577fa7325eff2ed2d9",
"1110d342a7031617a862f62bca8765ab7d2251db6b9e8541e7aa599d6c93cf69",
"84e6a0541e61f345695c6b5722dad0f4ddfd06ba097699b50ba1bcfe7b2608ce",
"6cb66f61897e852725119ad7b3cfcb032166b540a739658d6233efb76791b7a5",
"82212924a854ca5275b5102be80b5d30417c81a33f8ca2ce034fab05a4fd6009"
] |
| Globals | [
"React",
"ReactDOM",
"ReactJSXRuntime",
"wp",
"Mousetrap",
"moment",
"__wpStyleRuntime",
"jQuery",
"_tpt",
"SR7",
"$us",
"frontend_global_data",
"pow",
"_document",
"_navigator",
"_window",
"$ush",
"EvEmitter",
"imagesLoaded",
"USAnimate",
"usGmapLoaded",
"USHeader",
"pum_vars",
"pum_sub_vars",
"pum_popups",
"PUM",
"PUM_Accessibility",
"PUM_Analytics",
"pm_cookie",
"pm_cookie_json",
"pm_remove_cookie",
"pum_debug_mode",
"ajaxurl",
"pum",
"FormSerializer",
"MagicGrid",
"_smart_filter_object",
"Popper",
"bootstrap",
"Swiper"
] |
| Cookies | [
"pll_language"
] |
| Storage keys | [
"__wpDataTestLocalStorage",
"wpEmojiSettingsSupports"
] |
| Tls | {
"san": [
"*.dasco.kz",
"dasco.kz"
],
"cipher": "AES_256_GCM",
"issuer": "YR1",
"subject": "dasco.kz",
"protocol": "TLS 1.3",
"valid_to": "2026-12-15T16:59:54Z",
"valid_from": "2026-09-16T16:59:55Z"
} |
| Antigüedad del dominio en días | 2907 |
| Apex age days | 2907 |
| Tls age days | 24 |
| Días de validez TLS | 89 |
| Requests | 135 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": -26,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "PleskLin"
} |
Observado: · Retrieved:
| Uuid | 8478ff63-71d9-45e0-ac4e-48ff895e2679 |
|---|---|
| Final url | https://dasco.kz/ |
| Estado | 200 |
| History | [
{
"url": "https://dasco.kz/",
"status": 200
}
] |
| DOM structure hash | eba596a3bb34188f974bd9bbf3b32f4683e619adfa486efc1d6a0bd93e48d92b |
| Document hash | 9502f87f6e1a49701f8189a1270a3039a9cb4ba063e7a46bfced849e284f997e |
| Riesgos del dominio | [
"Business",
"Business & Economy"
] |
| Radar rank | {
"bucket": ">200000"
} |
| Registros DNS | [
{
"name": "dasco.kz",
"type": "A",
"value": "93.115.14.8"
}
] |
| DNSSEC válido | false |
| Ip | 93.115.14.8 |
| Ficha de registro | {
"created": "2018-03-16T11:11:05Z",
"updated": "2018-10-22T18:16:02Z",
"nameservers": [
"ns1.hoster.kz",
"ns2.hoster.kz",
"ns3.hoster.kz"
]
} |
Observado: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 3,
"suspicious": 2,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"SOCRadar": "phishing",
"URLQuery": "suspicious",
"Gridinsoft": "malicious",
"alphaMountain.ai": "malicious",
"Forcepoint ThreatSeeker": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"BitDefender": "porn",
"alphaMountain.ai": "Business/Economy, Malicious (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "compromised websites"
} |
| Popularity | {
"Alexa": 467663,
"Statvoo": 172758
} |
| Visto por primera vez | 2023-10-03T09:50:26Z |
| Registros DNS | [
{
"ttl": 3600,
"type": "NS",
"value": "ns1.hoster.kz"
},
{
"ttl": 3600,
"type": "TXT",
"value": "google-site-verification=WM2_dnkJ51hmuDni-GokuZP4VBfhHBjhUw39NNbJmUM"
},
{
"ttl": 3600,
"type": "MX",
"value": "alt1.aspmx.l.google.com",
"priority": 10
},
{
"ttl": 3600,
"type": "MX",
"value": "alt4.aspmx.l.google.com",
"priority": 15
},
{
"ttl": 3600,
"type": "MX",
"value": "alt2.aspmx.l.google.com",
"priority": 10
},
{
"ttl": 3600,
"type": "NS",
"value": "ns3.hoster.kz"
},
{
"ttl": 3600,
"type": "A",
"value": "93.115.14.8"
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 include:_spf.google.com ~all."
},
{
"ttl": 3600,
"type": "MX",
"value": "alt3.aspmx.l.google.com",
"priority": 15
},
{
"ttl": 3600,
"type": "NS",
"value": "ns2.hoster.kz"
},
{
"ttl": 3600,
"type": "TXT",
"value": "MS=ms62890202"
},
{
"ttl": 3600,
"type": "MX",
"value": "aspmx.l.google.com",
"priority": 5
},
{
"ttl": 3600,
"type": "TXT",
"value": "update_dns_zone"
},
{
"ttl": 3600,
"type": "TXT",
"value": "MS=FCB4B10B1570A011F50B206B47E942C7506A4B1C"
},
{
"ttl": 3600,
"type": "SOA",
"rname": "support.hoster.kz",
"value": "ns3.hoster.kz"
}
] |
| Dns at | 2026-10-20T02:00:37Z |
| Jarm | 29d29d00029d29d00042d42d0000002059a3b916699461c5923779b77cf06b |
| Certificate | {
"san": [
"*.dasco.kz",
"dasco.kz"
],
"issuer": "Let's Encrypt / YR1",
"serial": "5582eebeb48cb65d69ed8506e7be511d8d9",
"sha256": "6b9b543faa4ad65da34e29c1b41b52e76346f0928c196d7b4ccc918b0c53d78e",
"subject": "dasco.kz",
"valid_to": "2026-12-15T16:59:54Z",
"valid_from": "2026-09-16T16:59:55Z"
} |
| Ficha de registro | {
"status": [
"clientDeleteProhibited"
],
"nameservers": [
"ns1.hoster.kz",
"ns2.hoster.kz",
"ns3.hoster.kz"
]
} |
No. PhishDestroy clasifica dasco.kz como Suplantación de Facebook (riesgo: crítico, 88/100); se detectó por primera vez el 2026-10-10. VirusTotal: 5/92 motores lo marcan. Considera el sitio inseguro.
No. No conectes una billetera, no firmes mensajes ni apruebes tokens en dasco.kz. 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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/dascolightStored page referenceIoC extraction recorded 2026-10-11 04:01:16 UTC
ns1.hoster.kzns2.hoster.kzns3.hoster.kzaspmx.l.google.compriority 5alt2.aspmx.l.google.compriority 10alt1.aspmx.l.google.compriority 10alt4.aspmx.l.google.compriority 15alt3.aspmx.l.google.compriority 15La ubicación corresponde a la red IP.
6b9b543faa4ad65da34e29c1b41b52e76346f0928c196d7b4ccc918b0c53d78e*.dasco.kzdasco.kzMetadatos 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.
new.dasco.kzDomain recordsupport.dasco.kzDomain recordsurvey.dasco.kzDomain recordwww.dasco.kzDomain recordwww.new.dasco.kzDomain recordwww.survey.dasco.kzDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — auditoría de rendimiento móvil de dasco.kz · checked Oct 12, 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.
Desconocido→live_content
content_served
protected→live_content
content_served
Desconocido→protected
http_access_restricted · access_restriction
Desconocido→protected
http_access_restricted · access_restriction
Desconocido→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Desconocido→protected
http_access_restricted · access_restriction
live_content→protected
http_access_restricted · access_restriction
Desconocido→live_content
content_served
Desconocido→protected
http_access_restricted · access_restriction
live_content→protected
http_access_restricted · access_restriction
Desconocido→live_content
content_served
protected→live_content
content_served
Desconocido→protected
http_access_restricted · access_restriction
protected→live_content
content_served
Desconocido→protected
http_access_restricted · access_restriction
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Accesible
Sin amenazas marcadas
Ver fuente5/92 engine detections
Ver fuente37 community references
Ver fuentePD-20261010-3C6DA7
dasco.kz
Ver fuentePage captured
Ver fuenteCompara lo que reciben un navegador y un rastreador, y comprueba si hay enrutamiento de tráfico de Keitaro.
dasco.kz
PD-20261010-3C6DA7 Recipient: abuse@hoster.kz 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 ↗
dasco.kz)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.