跳转到安全报告
⚠️
该域名已被标记为恶意域名
安全引擎报告检测:4。 报告匹配的公共黑名单: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 . It contains 5 outgoing records; the latest is dated . The recorded recipient is complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 3 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
3 months
Reports sent
5
Latest case ID
PD-1776062070-broxus.tw
Current status
HTTP 403 at latest stored check
域安全和威胁情报

broxus[.]tw

broxus.tw 网络钓鱼与安全检查

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

威胁判定 关键 71/100 证据评分
可用性 隐形 · 可达 通过隐形检查观察可达性
风险信号
病毒检测总数:4/94 存储的阻止列表匹配项:2 诈骗类型:Brand Impersonation 最后已知的活跃状态
4/94 VT 2026年4月13日 自 2026年6月6日 起不可用 2 Blocklists 赌徒骗局 Brand Impersonation 5 Reports Sent Cloaking CDN
报告概览

broxus.tw — 隐形 · 可达 (HTTP 403). 诈骗类型:Brand Impersonation. 证据摘要: VirusTotal 4/94 (Gridinsoft, SOCRadar); 2 external blocklist matches (MetaMask, SEAL); cloaking observed; PhishDestroy score 71/100. 注册商: GNAME.COM.

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

证据摘要
重要
Ref
3F78C9EC
评分
71/100

PhishDestroy first observed broxus.tw on Apr 13, 2026. The captured page title is “Broxus: Most Popular Online Crypto Casino Based on Blockchain”. Stored page analysis classifies the content as brand impersonation. Campaign clustering links the hostname to the Gambler Scam kit. Current evidence score: 71/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 4 detections among 94 engines: Gridinsoft, SOCRadar on Jul 18, 2026 at 18:45 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 8, 2026 at 06:20 UTC. Non-positive and contextual checks: Gridinsoft assigned a trust score of 1/100 (Scam); no observation timestamp was retained. Google Safe Browsing returned no flag on Apr 13, 2026 at 07:34 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:08 UTC. PhishStats returned no feed match on Apr 13, 2026 at 07:35 UTC.

Cloaking was recorded with HTTP 403 on Aug 7, 2026 at 22:14 UTC. The cloaking probe recorded status split conditional delivery at 2/100 on Aug 7, 2026 at 01:50 UTC: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial. Registration records for the domain list GNAME.COM as the registrar and Apr 13, 2026 as the creation date. Registration and first observation occurred on the same UTC date. At collection time, the hostname resolved to 188.114.97.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 1 visual capture from PhishDestroy. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Jun 8, 2026; checked Apr 22, 2026 at 23:00 UTC.

The content indicators and 3 positive source findings support the current brand impersonation classification.

VirusTotal
VirusTotal
4 det.
URLScan
URLScan
Gridinsoft
1/100
ScamAdviser
Scamadviser
85/100
TLS 证书
Let's Encrypt
年龄
4 mo
观测状态
隐形 · 可达 403
PhishDestroy
DestroyList
已列入
Reports Sent
5
数据覆盖范围 VirusTotal 4 / 94 URLQuery 未检查 PhishStats checked — no match recorded OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 12 已检查 — 未发现拦截 TLS valid certificate, 56d WHOIS 4 mo old 屏幕截图 外部截图 重定向链 未探查 Gridinsoft 1/100 Scamadviser 85/100
安全信号
GS Gridinsoft Analysis 1 / 100
4 0 2 1 43

威胁响应 Pipeline

发现
Checks
Reports
可用性
16/17
Initial Abuse Report (#1)
Sent to 1 abuse contact at GNAME.COM with forensic evidence
complaint@gname.com
2026年4月13日
ICANN Escalation #2
Escalation #2 sent to 3 recipients including ICANN Compliance — follow-up record after a previous report
complaint@gname.comabuse@twnic.twcompliance@icann.org
2026年4月20日
ICANN Escalation #3
Escalation #3 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
complaint@gname.comabuse@twnic.twcompliance@icann.org
2026年4月22日
ICANN Escalation #4
Escalation #4 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
complaint@gname.comabuse@twnic.twcompliance@icann.org
2026年4月26日
ICANN Escalation #5
Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports
complaint@gname.comabuse@twnic.twcompliance@icann.org
2026年4月28日
5 Reports Filed
5 report records were stored over 117 days; current observed status: 隐形 · 可达

公共封禁名单状态

已保存的截图

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN cloudflare · AS13335 Cloudflare, Inc.
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
注册商 GNAME.COM SG(SG)
IP 地址 188.114.97.3 CDN
地理位置CA Toronto, CA
网络AS13335 · CloudFlare, Inc.
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户;查找源头需要被动 DNS 或证书透明数据。
注册信息创建 2026年4月13日 (117d)
HTTP 状态码403 Forbidden
Cloaking Cloaking Detected Status split · score 2/6
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
server: cloudflare title: Suspected Phishing | Cloudflare provider response: cloudflare phishing interstitial
checked 2026年8月7日
Elapsed Since First Report 10 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 隐形 · 可达.
Minimum notice count 5 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
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.
技术细节DNS、SSL SAN、时间戳
首次发现2026年4月13日
IoC Extractionscanned 2026年8月1日0 wallet · 0 Telegram IoCs
域名服务器sue.ns.cloudflare.com
TLS Fingerprint
TLS Observationvalid from 2026年3月10日scanned 2026年4月23日
Favicon Hash
Case ID
页面标题
Broxus: Most Popular Online Crypto Casino Based on Blockchain
TLS 证书
Valid transport encryption · 颁发者 Let's Encrypt · valid for 56 days
滥用举报历史 · 5 stored reports over 16 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.
5 abuse reports filed over 117 days — latest observed status: 隐形 · 可达
The records name GNAME.COM as a recipient or subject. ICANN Compliance appears in the recipient field for at least one record.
5
reports
117
days
ICANN CC
  1. Report #1 Apr 13, 2026 · 09:34 UTC
    Phishing Abuse Report: broxus[.]tw
    complaint@gname.com
  2. Report #2 ICANN CC 173h still active Apr 20, 2026 · 15:04 UTC
    ESCALATION #2 (173h active): Phishing - broxus[.]tw
    complaint@gname.com abuse@twnic.tw compliance@icann.org
  3. Report #3 ICANN CC 226h still active Apr 22, 2026 · 20:28 UTC
    ESCALATION #3 (226h active): Phishing - broxus[.]tw
    complaint@gname.com abuse@twnic.tw compliance@icann.org
  4. Report #4 ICANN CC 319h still active Apr 26, 2026 · 17:19 UTC
    ESCALATION #4 (319h active): Phishing - broxus[.]tw
    complaint@gname.com abuse@twnic.tw compliance@icann.org
  5. Report #5 ICANN CC 368h still active Apr 28, 2026 · 18:07 UTC
    ESCALATION #5 (368h active): Phishing - broxus[.]tw
    complaint@gname.com abuse@twnic.tw compliance@icann.org
Record scope: the timeline documents outgoing records stored by PhishDestroy. Delivery, acknowledgement, and subsequent action require separate recipient or infrastructure evidence.
所用技术 · 4 identified
Twitter Ads

Conversion and audience tracking pixel for paid campaigns on X (Twitter) — signals that the site runs paid X ads.

business.x.com
Facebook Pixel

Conversion-tracking pixel by Meta — logs page views and custom events to Facebook/Instagram ad accounts.

www.facebook.com
Cloudflare Browser Insights
Analytics RUM

Performance monitoring tool that measures website speed from real users.

www.cloudflare.com
Cloudflare
CDN

Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.

www.cloudflare.com
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

4 / 94 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 2 detections
Gridinsoft
SOCRadar
网站性能分析

Google PageSpeed Insights — mobile performance audit of broxus.tw · checked Apr 13, 2026

52
Needs Work
Performance
FCP
1.21s
First Contentful Paint
LCP
19.35s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
588ms
Total Blocking Time
SI
7.64s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

证据与外部报告

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1776062070-broxus.tw Recipient: complaint@gname.com
URLScan evidence VirusTotal evidence

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

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

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

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

嵌入此报告

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

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