跳转到安全报告
分析仪表盘
Domain security report
bscbox.xyz favicon

bscbox.xyz

“年会盛典 · 幸运抽奖”

威胁判定
关键域名申诉
Assessment sources

Assessment based on the stored source evidence below. Review sources →

可用性 未验证 未存储最终的当前响应 观察到 · HTTP probe
风险信号
病毒检测总数：12/91 Spamhaus DBL: DBL_PHISH URLQuery threat systems: 1 alert 诈骗类型：Impersonation
OTX: 4 refs 2026年8月18日 1 Report Sent CDN
API
注册商
NiceNIC
Resolved IP
172.67.131.91
Registered
2026年8月12日
3 sources
The capture source is temporarily unavailable.
1 / 3
来源
Primary capture
Collected · UTC
Open capture
In this reportGet help
该域名已被标记为恶意域名
安全引擎报告检测：12。 请格外小心——不要输入凭据或个人信息。
报告概览

bscbox.xyz — 未验证. 诈骗类型：Impersonation. 证据摘要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 1 alert; Spamhaus DBL_PHISH; PhishDestroy score 90/100. 注册商: NiceNIC.

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

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
12 det.
URLQuery
URLQuery
1 threat alert
OTX references
4 community refs
URLScan
URLScan
报告 ↗
TLS 证书
Expired or unverified dates
Google Trust Services / WE1 · Hostname coverage not recorded
年龄
2 mo New
PhishDestroy
DestroyList
已列入
Reports Sent
1

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

12 / 91

报告
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

1 threat-system alert

报告
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

报告
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF雷达

provider verdict: clean

Observation time not recorded
报告
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

存储的报告

View stored capture ↗
报告
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

分析完成

报告
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

报告
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

详情
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

网络安全情报 Registrar context
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU bscbox.xyz malicious Sinkholed
Stored URLQuery scan evidence · Aug 18, 2026 20:35 UTC Open source report
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:

证据摘要

关键
VirusTotal
12/91
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

bscbox.xyz returned an HTTP status 502 during a check on 2026-10-01, indicating a recorded server response at that time. The domain is also listed in the PhishDestroy internal catalogue, which is a publisher-maintained record.

Recorded Evidence

A VirusTotal scan on 2026-08-21 found 12 detections out of 91 scanners. OTX recorded 4 pulses for bscbox.xyz on the same date. The domain was registered with NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-08-12. An SSL scan on 2026-08-19 showed the issuer as Google Trust Services / WE1. PageSpeed measured a performance score of 98 on 2026-08-18.

Interpretation

The VirusTotal and OTX records provide insight into how the domain was observed by security and threat intelligence sources. The HTTP 502 response documents a specific server outcome on its check date, while the PhishDestroy listing is an internal catalogue entry. Registration and SSL certificate details supply administrative information relevant to the domain's timeline.

Recommended Actions

For bscbox.xyz, retain the VirusTotal and OTX records as reference points for future checks. Keep the PhishDestroy internal listing and compare it with other catalogue entries. Use the HTTP status and PageSpeed measurements to track changes in server response and performance. Maintain registration and certificate details for context in subsequent reviews.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
12 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
0 · external matches
Cloudflare Radar
无异常Collection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
172.67.131.91 · 2 · nameserversCollection time not recorded
TLS 证书
Google Trust Services / WE1
Page captures
3 · retained captures
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
98/100 · mobile performance
Response records
1 · outgoing report records
Availability history
71 · stored state changes
Source observation history
4 · stored source events
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Page analysis
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • 社区报告
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

公共封禁名单状态

Domain, network & archive

NICENIC INTERNATIONAL GROUP CO., LIMITED · 172.67.131.91 · DNS, TLS and retained responses

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-08activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 NiceNIC RU(RU) PhishDestroy Investigation
滥用举报联系方式abuse@nicenic.net
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询bscbox.xyz 的 ICANN RDAP →
注册信息创建 2026年8月12日 (65d · New) — Expires 2027年8月12日
Elapsed Since First Report 19 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 未验证.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年8月18日
Submitted URLhttps://bscbox.xyz/
Favicon Hash
案件 ID
ICANN OVERSIGHT

认证和 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.

认证是一纸合同，不是安全印章。 核实 ICANN 费用 阅读 RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.131.91
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 2
  • aron.ns.cloudflare.com
  • ricardo.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services / WE1
Valid from
2026-08-14 12:54:41
Valid until
2026-11-12 13:54:40
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-08-18 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7d0e02dd9756abd0c2504af78034580e45ea6bca06813f30684e961c2902805f

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.131.91rapiddns.io

Latest Classified Outcome 2026-10-16 03:47:24 UTC

Primary outcome Registration hold observed reason: Registry serverHold 95% confidence
Attribution actor class: Registry mechanism: Registry serverHold source: Rdap Status Collector
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Registry serverHold
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-16 11:00:13 UTC
RDAP registration Registry serverHold NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765 RDAP HTTP 200 source: Rdap Status Collector clientDeleteProhibitedclientTransferProhibitedserverHold expires 2027-08-12 23:59:59 UTC checked 2026-10-16 03:47:24 UTC
Observed timeline last reachable: 2026-08-19 22:15:41 UTC current episode first observed: 2026-08-20 00:54:05 UTC observed RIP window: 2026-08-19 22:15:41 UTC → 2026-08-20 00:54:05 UTC · 2.64h midpoint estimate ≈ 2026-08-19 23:34:53 UTC · precision high · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

12 / 91 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Lionic
SafeToOpen
SOCRadar
Sophos
网站性能分析

Google PageSpeed Insights — mobile performance audit of bscbox.xyz · checked Aug 18, 2026

98
Good
Performance
FCP
0.93s
First Contentful Paint
LCP
0.93s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details15

Registration evidence

RDAP statuses
clientdeleteprohibited · clienttransferprohibited · serverhold
RDAP response
200
Registrar in registration evidence
NICENIC INTERNATIONAL GROUP CO., LIMITED
Registrar IANA ID
3765
Expiration recorded by RDAP
Registration observation
Registration source
rdap_status_collector

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
2.64
Estimate basis
Bounded by observations
Estimate precision
高

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

探测与规避分析

隐身和流量分配检查

尚未扫描 目前尚未记录到爬虫与浏览器之间的差异

针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
尚未扫描
上次隐形扫描

扫描说明: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bscbox.xyz', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC

TDS指纹识别实时演示
检查七项 Keitaro 特征，并比较浏览器与爬虫的响应。只有点击按钮后才会开始新的扫描。
按需运行

尚未保存实时检查结果。

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-07 02:31:00 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. VirusTotal Detections Update 2026-08-21 02:52:17 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 11 to 12. Added scanner alerts: Forcepoint ThreatSeeker.
  3. VirusTotal Detections Update 2026-08-19 01:43:47 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 11 to 11. Added scanner alerts: SOCRadar. Resolved alerts: ADMINUSLabs.
  4. Threat First Observed 2026-08-18 19:34:24 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.131.91.
Stored observation history75

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  2. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  3. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

Earlier observations 70
  1. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  2. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  5. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  6. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  7. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  9. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  11. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  12. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  13. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  14. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  15. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  16. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  17. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  18. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  19. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  20. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  21. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  22. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  23. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  24. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  25. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  26. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  27. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  28. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  29. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  30. Availability monitor · Recorded state

    held→未知

    origin_unreachable · http_5xx

  31. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  32. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  33. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  34. Availability monitor · Recorded state

    dns_inactive→held

    registry_server_hold · server_hold

  35. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  36. Availability monitor · Recorded state

    dns_inactive→held

    registry_server_hold · server_hold

  37. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  38. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  39. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  40. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  41. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  42. Availability monitor · Recorded state

    held→未知

    origin_unreachable · http_5xx

  43. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  44. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  45. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  46. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  47. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  48. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  49. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  50. Availability monitor · Recorded state

    held→未知

    probe_inconclusive

  51. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  52. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  53. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  54. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  55. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  56. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  57. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  58. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  59. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  60. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  61. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  62. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  63. Availability monitor · Recorded state

    未知→held

    registry_server_hold · server_hold

  64. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  65. Availability monitor · Recorded state

    held→dns_inactive

    dns_nxdomain

  66. Availability monitor · Recorded state

    held

    registry_server_hold · server_hold

  67. Availability monitor · Recorded state

    可访问→不可用

  68. VirusTotal · Detection count

    11→12

  69. VirusTotal · Detection count

    11→11

  70. Availability monitor · First collection record

    可访问

威胁响应 Pipeline

发现
Analysis
Notifications
Monitoring

13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
bscbox.xyz 已检测到并排入队，待进行全面分析
2026年8月18日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年10月2日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年8月18日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
12/91 recorded on VirusTotal
2026年8月21日
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月5日
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年8月18日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月17日
Content Observed Unavailable
监控记录了一个不可用的响应；原因尚未独立确定。
2026年9月7日
VT Detection +1
+1 new detection (11 → 12): Forcepoint ThreatSeeker
2026年8月21日
Sent Report Recorded
Stored outgoing record associated with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED, 1 abuse contact
abuse@nicenic.net
2026年8月18日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2026年8月18日
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

社区情报

1 条社区报告

类别PHISHING

Blacklist from Phishfort

Evidence & investigation tools

Original reports, independent checks and evidence links

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 12 det. ChainPatrol ChainAbuse 1 report URLQuery 1 threat alert SSL 实验室 Hostname coverage not recorded CF雷达 打开报告 OTX 4 refs WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
Third-Party Detection — ChainAbuse
1 report filed for bscbox.xyz · category: Phishing · source checked
Flagged by PhishFort Detection System on Nov 8, 2022 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20260818-65C2EB Recipient: abuse@gen.xyz
Page title stored with report: 年会盛典 · 幸运抽奖
PDF notice generated Notice text archived (416 chars)
Abuse notice text as sent to the provider 
Registrar: NICENIC International Group Co., Limited (Hong Kong (China))
Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown
Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

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

6 evidence signal groups linked 1 stored notification records 未验证
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →
向当地主管部门报告

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

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息？

联邦调查局（FBI）指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 bscbox.xyz)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整，对调查仍有帮助。

我应该向哪里举报这起诈骗？

  • 联邦调查局（FBI）IC3 — 互联网犯罪投诉中心（美国联邦举报渠道）
  • 欧洲刑警组织 — 欧洲网络犯罪报告（欧盟）
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动，也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站，使得欺诈行为更难被察觉

将来我该如何保护自己？

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前，请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

实时威胁动态 对该列表提出异议
Read the evidence in context

关于本报告：bscbox.xyz

该报告提供了 PhishDestroy 可用的最新存储证据。如果有的话，会显示源时间戳；收集后可用性和供应商判断可能会发生变化。

捕获的站点显示页面标题 “年会盛典 · 幸运抽奖”。

截至 2026-08-21 02:52:17 UTC，bscbox.xyz 已检测到 12 安全引擎。

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

如果您认为此列表不准确，提出上诉。要了解我们的方法，请访问 常见问题页面。

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

嵌入此报告

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

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