Ir al informe de seguridad
⚠️
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 14. Tenga extrema precaución: no ingrese credenciales o información personal.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . It contains 11 outgoing records; the latest is dated . The recorded recipient is abuse-contact@publicdomainregistry.com. The latest stored availability evidence still shows the domain reachable; 6 months 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.

Elapsed since first report
6 months
Reports sent
11
Latest case ID
PD-1770575381-mycas.bet
Current status
Observed active at latest stored check
Seguridad de dominio e inteligencia sobre amenazas

mycas[.]bet

“Mycas: Most Popular Online Crypto Casino Based on Blockchain”

Veredicto de amenaza Crítico Puntuación de evidencia 95/100
Disponibilidad No verificado La accesibilidad actual no está verificada
VirusTotal detecciones: 14/91 Suplantación de marca: Genericcrypto
07/02/2026 Genericcrypto 11 Reports Sent CDN
Resumen del informe

mycas.bet — No verificado. Suplantación de marca: Genericcrypto; Tipo de estafa: Crypto Scam. Resumen de las pruebas: VirusTotal 14/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar); URLQuery 100 det.; URLScan malicious verdict; PhishDestroy score 95/100. Registrador: PDR.

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Resumen de las pruebas
CRÍTICO
Ref.
60B15A42
Puntuación
95/100

This report details the technical assessment of the domain mycas.bet. The site presented itself with the title "Mycas: Most Popular Online Crypto Casino Based on Blockchain," indicating it was a cryptocurrency gambling platform. The site was classified as a "Gambler Scam" and impersonated the brand of a legitimate crypto casino or gambling service. The primary threat posed is a cryptocurrency scam, likely designed to defraud users by soliciting deposits under false pretenses.

Technical analysis reveals the domain was flagged by 16 out of 95 VirusTotal vendors. It was specifically flagged by ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF, and CyRadar. The domain was also present on 1 blocklist. The IP address 104.21.1.234 is hosted in the United States by AS13335 Cloudflare, Inc. The domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com and was created on 2026-02-21. The SSL certificate was issued by Google Trust Services / WE1. The nameservers used were jasmine.ns.cloudflare.com and gordon.ns.cloudflare.com.

The domain mycas.bet is currently DOWN/OFFLINE. Based on the high number of vendor detections, its classification as a cryptocurrency scam, and its offline status, the risk level is assessed as high for any user who may have interacted with the site. The domain should be considered malicious and blocked at the network level.

VirusTotal
VirusTotal
14 det.
URLQuery
URLQuery
100 det.
URLScan
URLScan
Certificado TLS
WE1
Estado observado
No verificado
PhishDestroy
DestroyList
En lista
Reports Sent
11
Cobertura de los datos VirusTotal 14 / 91 URLQuery 100 det. PhishStats checked — no match recorded OTX no community references CF Radar scan completed URLScan capture informe almacenado URLScan verdict malicious Bloqueos de DNS no comprobado TLS valid certificate, 47d WHOIS not parsed Captura de pantalla 2 captures · 2 sources Cadena de redireccionamientos no sondeado

Proceso de respuesta ante amenazas Pipeline

Descubrimiento
Checks
Reports
Disponibilidad
25/26
Initial Abuse Report (#1)
Sent to 1 abuse contact at PDR Ltd. d/b/a PublicDomainRegistry.com with forensic evidence
abuse@publicdomainregistry.com
08/02/2026
ICANN Escalation #2
Escalation #2 sent to 3 recipients including ICANN Compliance — follow-up record after a previous report
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
26/02/2026
ICANN Escalation #3
Escalation #3 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
03/03/2026
ICANN Escalation #4
Escalation #4 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
04/03/2026
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
06/03/2026
ICANN Escalation #6
Escalation #6 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
20/04/2026
ICANN Escalation #7
Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
22/04/2026
ICANN Escalation #8
Escalation #8 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
26/04/2026
ICANN Escalation #9
Escalation #9 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
28/04/2026
ICANN Escalation #10
Escalation #10 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
05/05/2026
ICANN Escalation #10
Escalation #10 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
abuse-contact@publicdomainregistry.comabuse@identitydigital.comcompliance@icann.org
28/05/2026
11 Reports Filed
11 report records were stored over 188 days; current observed status: No verificado

Estado de la lista de bloqueados pública

Captura guardada

Título de la página
Mycas: Most Popular Online Crypto Casino Based on Blockchain
Certificado TLS
Valid transport encryption · Emitido por WE1 · valid for 47 days

Inteligencia de dominios

Dominio
URLScan Verdict Malicioso score 100 Phishing report ↗
Servidor / ASN cloudflare · AS13335 Cloudflare, Inc.
IP Context Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrador PDR IN(IN)
Dirección IP 104.21.1.234 CDN
UbicaciónUS San Francisco, US
RedAS13335 · Cloudflare, Inc.
La IP de origen está oculta detrás de un proxy CDN. Los resultados de IP inversa para la dirección perimetral contienen inquilinos no relacionados; encontrar el origen requiere DNS pasivo o datos de transparencia de certificado.
Elapsed Since First Report 21 days
Qué contabilizamos Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: No verificado.
Minimum notice count 11 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
Qué contiene cada informe Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
ICANN RAA §3.18 The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
Detalles técnicosDNS, SAN de SSL, marcas de tiempo
Primera detección07/02/2026
DOM Analysisanalyzed 10/07/2026score 0/100
IoC Extractionscanned 29/07/20260 wallet · 0 Telegram IoCs
Submitted URLhttps://mycas.bet/
Servidores de nombresgordon.ns.cloudflare.com
TLS Observationvalid from 16/01/2026scanned 15/03/2026
Favicon Hash
Case ID
ICANN OVERSIGHT

Acreditación y contexto RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft No se envía nada automáticamente.
Historial de denuncias de abuso · 11 stored reports over 110 days · click to expand
This timeline is built from stored outgoing report records. It documents timestamps and listed recipients, but does not by itself prove delivery, acknowledgement, or recipient action.
11 abuse reports filed over 188 days — latest observed status: No verificado
The records name PDR Ltd. d/b/a PublicDomainRegistry.com as a recipient or subject. ICANN Compliance appears in the recipient field for at least one record.
11
reports
188
days
ICANN CC
  1. Report #1 Feb 8, 2026 · 18:31 UTC
    Phishing Abuse Report: mycas[.]bet
    abuse@publicdomainregistry.com
  2. Report #2 ICANN CC 435h still active Feb 26, 2026 · 22:28 UTC
    ESCALATION #2 (435h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  3. Report #3 ICANN CC 536h still active Mar 3, 2026 · 02:56 UTC
    ESCALATION #3 (536h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  4. Report #4 ICANN CC 572h still active Mar 4, 2026 · 15:11 UTC
    ESCALATION #4 (572h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  5. Report #5 ICANN CC 616h still active Mar 6, 2026 · 10:53 UTC
    ESCALATION #5 (616h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  6. Report #6 ICANN CC 1697h still active Apr 20, 2026 · 15:00 UTC
    ESCALATION #6 (1697h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  7. Report #7 ICANN CC 1750h still active Apr 22, 2026 · 20:27 UTC
    ESCALATION #7 (1750h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  8. Report #8 ICANN CC 1843h still active Apr 26, 2026 · 17:21 UTC
    ESCALATION #8 (1843h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  9. Report #9 ICANN CC 1892h still active Apr 28, 2026 · 18:18 UTC
    ESCALATION #9 (1892h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  10. Report #10 ICANN CC 2049h still active May 5, 2026 · 07:23 UTC
    ESCALATION #10 (2049h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
  11. Report #10 ICANN CC 2610h still active May 28, 2026 · 18:51 UTC
    ESCALATION #10 (2610h active): Phishing - mycas[.]bet
    abuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
Record scope: the timeline documents outgoing records stored by PhishDestroy. Delivery, acknowledgement, and subsequent action require separate recipient or infrastructure evidence.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

14 / Los proveedores de seguridad de 91 marcaron este dominio
View on VT
Last analyzed Previous stored snapshot: 16 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive

Datos y informes externos

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1770575381-mycas.bet Recipient: abuse-contact@publicdomainregistry.com
URLScan evidence VirusTotal evidence

¿Te ha afectado esta página web?

If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Europol
Encuentre el canal de denuncia oficial para su país de la UE
National police directory
¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países
Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente Revíselo y envíelo usted mismo

Comprobar cualquier dominio

Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público

Escanear ahora

Denunciar un intento de phishing

Envía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad

Denunciar

Flujo de amenazas en tiempo real

Informes de phishing recientes y cambios de disponibilidad observados

Monitorizar

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/mycas.bet"
  title="PhishDestroy threat report for mycas.bet"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>

Una carta de agradecimiento muy sincera

Generador de borradores satíricos

Destinatario
Contexto de las tarifas

Borrador satírico. Las cifras de las tarifas son estimaciones; no se afirma que correspondan exactamente a este dominio.