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; 5 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.
coshope[.]bet
“Coshope: Most Popular Online Crypto Casino Based on Blockchain”
coshope.bet — Non vérifié. Usurpation de l'identité de la marque : Genericcrypto; Type d'arnaque : Crypto Scam. Résumé des preuves: VirusTotal 16/94 (ADMINUSLabs, alphaMountain.ai, BitDefender, CRDF, CyRadar); URLQuery 2 alerts; URLScan malicious verdict; Spamhaus DBL_PHISH; PhishDestroy score 95/100. Bureau d’enregistrement: PDR.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
This domain, coshope.bet, is flagged for brand impersonation targeting users of crypto gambling platforms. The site presents itself as a legitimate blockchain-based online casino, using the page title 'Coshope: Most Popular Online Crypto Casino Based on Blockchain.' Such impersonation domains typically aim to harvest login credentials, steal cryptocurrency deposits, or distribute malware under the guise of a trusted service. Users may be lured into depositing funds or sharing sensitive information, believing they are interacting with a reputable platform. Analysis indicates the domain was registered on March 05, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, a registrar frequently associated with high-risk domains. Infrastructure analysis reveals the domain resolves to IP address 172.67.189.146, hosted on Cloudflare’s network (AS13335). Security vendor detections on VirusTotal show 17 out of 95 engines flagging the domain as malicious, while it appears on one security blocklist. The SSL certificate, issued by Google Trust Services (WE1), does not mitigate the inherent risk of the domain’s fraudulent intent. If you visited coshope.bet, immediate action is required to mitigate potential compromise. Disconnect the device from the network to prevent further data exfiltration. Revoke any active sessions on crypto wallets or gambling accounts accessed during the visit. Scan the device using updated security tools to detect malware or unauthorized modifications. Monitor financial accounts and crypto wallets for unauthorized transactions, and report any suspicious activity to the relevant platform. Reset passwords for all accounts accessed on the same device, prioritizing those linked to financial services or cryptocurrency exchanges.
Renseignements sur la sécurité réseau
Processus de réponse aux menaces Pipeline
Statut de la liste de blocage publique
Capture enregistrée
Informations sur les domaines
Détails techniquesDNS, SAN SSL, horodatages
ICANN OVERSIGHT
Contexte de l’accréditation et du RAA
Contexte de l’accréditation et du 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.
Historique des signalements d’abus · 11 stored reports over 90 days · click to expand
-
Report #1 Mar 5, 2026 · 01:25 UTCPhishing Abuse Report: coshope[.]betabuse-contact@publicdomainregistry.com
-
Report #2 ICANN CC 33h still active Mar 6, 2026 · 10:37 UTCESCALATION #2 (33h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #3 ICANN CC 180h still active Mar 12, 2026 · 14:02 UTCESCALATION #3 (180h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #4 ICANN CC 515h still active Mar 26, 2026 · 16:14 UTCESCALATION #4 (515h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #5 ICANN CC 1114h still active Apr 20, 2026 · 14:56 UTCESCALATION #5 (1114h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #6 ICANN CC 1168h still active Apr 22, 2026 · 20:26 UTCESCALATION #6 (1168h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #7 ICANN CC 1260h still active Apr 26, 2026 · 17:24 UTCESCALATION #7 (1260h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #8 ICANN CC 1309h still active Apr 28, 2026 · 18:08 UTCESCALATION #8 (1309h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #9 ICANN CC 1466h still active May 5, 2026 · 07:14 UTCESCALATION #9 (1466h active): Phishing - coshope[.]betabuse@identitydigital.com compliance@icann.org
-
Report #10 ICANN CC 1922h still active May 24, 2026 · 06:29 UTCESCALATION #10 (1922h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
-
Report #11 ICANN CC 2154h still active Jun 2, 2026 · 22:50 UTCESCALATION #11 (2154h active): Phishing - coshope[.]betabuse-contact@publicdomainregistry.com abuse@identitydigital.com compliance@icann.org
Casino / Gambling License Verification
Analyse VirusTotal
Preuves archivées
Données factuelles et rapports externes
PD-1772673954-coshope.bet Recipient: abuse-contact@publicdomainregistry.com Ce site vous a-t-il affecté ?
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Signalez-le à vos autorités locales
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Vérifier n'importe quel domaine
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignaler une tentative d'hameçonnage
Signalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerFlux d'alertes en temps réel
Rapports de phishing récents et changements de disponibilité observés
SurveillerRestez informés, restez en sécurité
Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif