VirusTotal
6 / 92 engine detections
보고서 열기
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 12 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.
coinex.bet — 확인되지 않음. 증거 요약: VirusTotal 6/92 (alphaMountain.ai, BitDefender, ESET, Fortinet, G-Data); URLQuery 2 det.; Spamhaus DBL_SPAM; PhishDestroy score 88/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
6 / 92 engine detections
보고서 열기2 det.
보고서 열기DBL_SPAM
4 community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
coinex.bet is a domain on the PhishDestroy blocklist whose name borrows the word "coinex" and pairs it with a gambling-flavoured .bet ending. That combination should make anyone looking for a crypto exchange stop before trusting it. PhishDestroy first flagged it on 2026-10-06. When last checked on 2026-10-19, the server still answered but no active content was being served through DNS.
The page shows only the title "Loading" and no visible brand or interface. The site's purpose has therefore not been pinned to a specific scheme. Domains like this, built around crypto-sounding names, are commonly used to collect login details, take deposits or prompt wallet connections once real content goes live. The realistic risk is losing account credentials or funds sent to an address you cannot recover. The bare loading title gives no sign of a legitimate service behind it.
Six of 92 engines on VirusTotal flagged the domain as of 2026-10-06: alphaMountain.ai, BitDefender, ESET, Fortinet, G-Data and LevelBlue. That count is modest, but it comes from several unrelated vendors rather than a single source. Spamhaus lists the domain in its DBL as spam. Four AlienVault OTX threat pulses reference it, so other researchers have tied it to suspicious activity. Among blocklists, PhishDestroy is currently the one listing it.
The domain was registered on 2026-04-23 through PDR Ltd. (PublicDomainRegistry.com), about five and a half months before it was flagged. A gap that long suggests the name was registered in advance rather than spun up and used immediately. It resolves to 46.29.26.38, an address announced by the Bangladeshi network M/S Robi Traders but located in Finland. The site uses a free, automatically issued Let's Encrypt certificate, so the padlock in the browser says nothing about who runs it.
Do not create an account, log in, deposit funds or connect a wallet on coinex.bet. If you already entered a password there, change it anywhere you reused it and turn on two-factor authentication. If you sent crypto, record the transaction details and report them to your exchange or wallet provider right away. If you connected a wallet, review and revoke any token approvals you granted. Security teams should block the domain and its IP at DNS and proxy level and watch for related names using the same pattern.
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.
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.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
8992f7187a247802c53df9970db8753d8566b8b682cf630d1e7d1ed7f97bb3c3Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
92100b97-9552-4a8d-b58e-e28157b811a4.coinex.betDomain recordairflow.coinex.betDomain recordapi.coinex.betDomain recordautoconfig.coinex.betDomain recordautodiscover.coinex.betDomain recordbe2f076d-7a48-4e57-a460-3dccda825db8.coinex.betDomain recordclient.coinex.betDomain recordconfirm.coinex.betDomain recordcpanel.coinex.betDomain recordcpcalendars.coinex.betDomain recordcpcontacts.coinex.betDomain recorddev.coinex.betDomain recordftp.coinex.betDomain recordgitlab.coinex.betDomain recordm.coinex.betDomain recordmail.coinex.betDomain recordsitemaps.coinex.betDomain recordwebdisk.coinex.betDomain recordwww.api.coinex.betDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of coinex.bet · checked Oct 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→live_content
content_served
접속 가능
No threat flag
View sourcePD-20261006-1B5012
4 community references
View source6/92 engine detections
View sourcecoinex.bet
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
coinex.bet
PD-20261006-1B5012 Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
coinex.bet)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.