セキュリティレポートへ移動
分析ダッシュボード
Domain security report
bscbox.xyz favicon

bscbox.xyz

“年会盛典 · 幸运抽奖”

脅威の評決
クリティカルドメイン異議申立て
Assessment sources

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

可用性 未検証 最終的な電流応答は保存されません 観測された · HTTP probe
リスクシグナル
VirusTotal 検出数: 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
ソフォス
サイトパフォーマンス分析

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

探知・回避の分析

クローキングおよびトラフィック分散の確認

まだスキャンされていません クローラーとブラウザの間に違いは見られていない

このホストに関するクローラーとブラウザの観測データの蓄積に加え、ケイタロ式トラフィック分散システム向けのリアルタイムフィンガープリントチェック。

保存されたクローキングフラグ
まだスキャンされていません
前回のクローキングスキャン

スキャナーに関する注記: 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の7つの特徴と、ブラウザーとクローラーへの応答を比較します。ボタンを押したときだけ新しいスキャンを開始します。
手動実行

ライブ確認の結果はまだ保存されていません。

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 ビットディフェンダーURL submission NortonSafe Web Symantecサイトレビュー AviraURL reporting Avast / AVGURL reporting カスペルスキーOpenTIP Dr.WebOnline scanner ネットクラフトAbuse 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 ウェイバック
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アカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ（SMSではない）を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか？

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した（以下を含む） bscbox.xyz)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか？

  • FBI IC3 — インターネット犯罪通報センター（米国連邦政府の通報窓口）
  • ユーロポール — 欧州におけるサイバー犯罪の報告（EU）
  • 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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか？

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する 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/ja/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>