跳转到安全报告
分析仪表盘
⚠️
该域名已被标记为恶意域名
安全引擎报告检测：15。 报告匹配的公共黑名单：2。 请格外小心——不要输入凭据或个人信息。
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 . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. 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 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
1
Current status
Observed active at latest stored check
域安全和威胁情报

betbeast[.]cc

威胁判定 关键 100/100 证据评分
可用性 未验证 当前可达性未经验证
风险信号
病毒检测总数：15/93 Spamhaus DBL: DBL_PHISH 存储的阻止列表匹配项：2 诈骗类型：Crypto Gambling
2026年2月8日 1 Report Sent CDN

证据摘要

重要
Evidence score
100/100

The domain betbeast.cc is identified as a high-risk generic phishing site, specifically a gambling scam. It has been taken offline, but users should remain cautious as it has been flagged by 15 of 95 security vendors on VirusTotal, including ADMINUSLabs, alphaMountain.ai, and BitDefender. The domain also appears on three security blocklists: PhishDestroy, MetaMask, and SEAL.

betbeast.cc was registered through Global Domain Group LLC on February 21, 2026. The domain resolves to the IP address 188.114.96.3, which is located in the US and is part of AS13335 Cloudflare, Inc. The SSL certificate for the domain is issued by Internet Widgits Pty Ltd. The site uses Nginx and OpenResty technologies, and the HTTP status code returned is 666, indicating an unusual response.

Users who have interacted with betbeast.cc should take immediate steps to protect themselves. For those who may have entered personal information, it is advised to change passwords and enable two-factor authentication on all affected accounts. Additionally, users should monitor their accounts for any signs of fraud or unauthorized activity. To prevent further spread, individuals can report the domain to their internet service provider, local authorities, and any relevant security blocklists such as PhishDestroy, MetaMask, and SEAL.

已提交证据快照

已发送
台账记录
1
案件 ID
PD-1770574591-betbeast.cc
PDF 文件
PDF 证据
报告历史 1
  1. 报告 1 Phishing Abuse Report: betbeast[.]cc
VirusTotal
VirusTotal
15 det.
TLS 证书
E7
观测状态
未验证
PhishDestroy
DestroyList
已列入
Reports Sent
1

Data Coverage

VirusTotal 15 / 93 URLQuery 报告已存储 — 详细判决待定 PhishStats checked — no match recorded OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 未检查 TLS valid certificate, 89d WHOIS not parsed 屏幕截图 2 captures · 2 sources 重定向链 未探查

威胁响应 Pipeline

发现
Checks
Reports
可用性
11/12

阻止列表覆盖

监控中的外部数据源 10 个 · 已存快照 2026年8月13日

MetaMask 已列入 PhishDestroy 源数据集 SEAL 已列入
监控中的外部数据源 8 个 无匹配
ScamSniffer 无匹配 Polkadot 无匹配 CryptoFirewall 无匹配 OpenPhish 无匹配 Enkrypt 无匹配 Phishunt 无匹配 Codeesura 无匹配 DiscordPhishing 无匹配

检测时间线

  1. 域名状态

    可访问 → 无法访问

  2. Cloudflare Radar

    已存储 Cloudflare Radar 扫描 · 打开扫描

  3. 域名状态

    无法访问 → 可访问

已保存的截图

URLScan capture 2 / 2
查看原图 下载

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN cloudflare · AS13335 CLOUDFLARENET - Cloudflare, Inc., US
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
注册商 Global Domain Group US(US)
滥用举报联系方式abuse@globaldomaingroup.com
ICANN 注册管理机构ICANN官方认证注册商 →
WHOIS查询betbeast.cc 的 ICANN RDAP →
IP 地址 188.114.96.3 CDN
地理位置US San Francisco, US
网络AS13335 · Cloudflare, Inc.
反向 IPviewdns.info → rapiddns.io →
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户；查找源头需要被动 DNS 或证书透明数据。
Elapsed Since First Report 22 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 未验证.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情DNS、TLS 名称和时间戳
首次发现2026年2月8日
DOM Analysisanalyzed 2026年7月28日DOM analysis score 0/100
域名服务器ns4.nameserverhub.com
TLS 指纹
TLS 观测自 2023年12月28日 起有效扫描于 2026年3月15日
Favicon Hash
TLS 证书
Valid transport encryption · 颁发者 E7 · valid for 89 days
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
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

15 / 93 安全供应商标记了该域
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Seclookup
SOCRadar
Sophos

您是否受到本网站的影响？

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

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录
AI辅助草稿——事件详细信息由AI提供商处理 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议

外部工具

GridinsoftGridinsoft 信任评分 1/100打开来源
ChainPatrol URLQuery Google Safe Browsing SSL Labs Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/betbeast.cc"
  title="PhishDestroy threat report for betbeast.cc"
  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>