VirusTotal
12 / 91 engine detections
レポートを開く“NovaBet - HTML Template”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.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.
暗号資産カジノ詐欺: apexbets.casino — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 91 engine detections
レポートを開くchecked — no detections recorded
レポートを開くchecked — no match recorded
23 community references
レポートを開く12 確認済み — ブロックなし
Scan report
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has identified apexbets.casino as an active generic phishing domain targeting users with potentially deceptive tactics. While no specific drainer kit or brand affiliation is associated with the domain, it leverages the allure of the casino gambling niche to lure victims into providing sensitive information or credentials.
From a technical perspective, apexbets.casino scores 1 out of 95 on VirusTotal, indicating minimal but present detection. The domain was created recently on March 23, 2026, and is registered through Spaceship, Inc. It resolves to the IP address 172.67.171.54 and uses a Let's Encrypt SSL certificate to appear legitimate and secure. There are no Google Safe Browsing (GSB) flags publicly noted, and blocklist counts remain unreported, suggesting it may be newly active or under the radar.
Currently, apexbets.casino remains active with an elevated risk level. Users are strongly advised to avoid visiting or interacting with the site, as the phishing threat could lead to credential theft or financial loss. Security teams should monitor this domain for any emerging malicious campaigns, update blocklists accordingly, and educate users about the risks associated with fraudulent gambling-related websites.
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.
Edge-IP の評判はこのドメインに起因しません。
margot.ns.cloudflare.comLocation describes the IP network.
277aa22eb7acbce6b7989ab2e9770d311e5a6d48089eb2c1a2a51fbe6c8f5856Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of apexbets.casino · checked Apr 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
apexbets.casino
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
No threat flag
View source23 community references
View source12/91 engine detections
View sourceapexbets.casino
View sourcePD-20260411-5DBE0F
コミュニティの 1 人が報告・初回確認 2026年4月11日
PD-20260411-5DBE0F Recipient: abuse@spaceship.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
apexbets.casino)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.