Domain security report

bscbox.xyz

“年会盛典 · 幸运抽奖”

위협 평결

심각도메인 이의신청

Assessment sources

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

90/100

Evidence score

가용성 확인되지 않음 결정적인 현재 응답이 저장되지 않습니다. 관측됨 Oct 16, 22:57 UTC· HTTP probe

위험 신호

VirusTotal 탐지: 12/91 Spamhaus DBL: DBL_PHISH URLQuery threat systems: 1 alert 사기 유형: Impersonation

등록기관: NiceNIC
Resolved IP: 172.67.131.91
Registered: 2026년 8월 12일

Stored captures

3 sources

The capture source is temporarily unavailable.

출처: Primary capture
Collected · UTC: 2026-08-18 19:34 UTC

Open capture

Primary capture

URLScan capture

URLQuery capture

In this reportGet help

보고서 요약

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

12 det.

URLQuery

1 threat alert

OTX references

4 community refs

URLScan

보고서 ↗

TLS 인증서

Expired or unverified dates

Google Trust Services / WE1 · Hostname coverage not recorded

연령

2 mo New

DestroyList

등재됨

Reports Sent

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

2026-08-21 02:52:17 UTC

보고서

Interpretation & limits

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

URLQuery

1 threat-system alert

2026-08-18 20:35:33 UTC

보고서

Interpretation & limits

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

Spamhaus DBL

DBL_PHISH

2026-10-02 06:39:39 UTC

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

2026-10-05 16:25:40 UTC

보고서

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 ↗

2026-08-18 19:34:24 UTC

보고서

Interpretation & limits

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

URLScan verdict

분석 완료

2026-08-18 23:08:16 UTC

보고서

Interpretation & limits

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

Google Safe Browsing

Checked; no threat flag recorded

2026-08-21 21:58:09 UTC

보고서

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

2026-10-16 22:20:02 UTC

세부 정보

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

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:

증거 요약

AI-assisted analysis Stored narrative · generated 2026-10-01 13:45:33 UTC. 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.

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 detections2026-08-21 02:52:17 UTC
URLScan analysis: Automated verdict retained2026-08-18 23:08:16 UTC
URLQuery: 2 · recorded detections / alerts2026-08-18 20:35:33 UTC
Google Safe Browsing: Checked; no threat flag recorded2026-08-21 21:58:09 UTC
OTX publications: 4 · community references2026-10-05 16:25:40 UTC
External blocklists: 0 · external matches2026-10-16 22:20:02 UTC
Cloudflare Radar: 정상Collection time not recorded
Spamhaus DBL: DBL_PHISH2026-10-02 06:39:39 UTC
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 / WE12026-08-18 22:02:04 UTC
Page captures: 3 · retained captures2026-08-18 19:34:24 UTC
Observed indicators: 0 · wallet / Telegram indicators2026-08-19 04:00:32 UTC
Detection & evasion: Stored browser and crawler comparison2026-10-16 22:57:52 UTC
PageSpeed performance: 98/100 · mobile performance2026-08-18 19:40:32 UTC
Response records: 1 · outgoing report records2026-08-18 20:35:43 UTC
Availability history: 71 · stored state changes2026-10-16 11:00:13 UTC
Source observation history: 4 · stored source events2026-09-07 02:31:00 UTC
Chainabuse records: 1 · recorded reports2026-10-16 23:12:09 UTC
IP reputation: Network-level observations2026-10-02 04:00:29 UTC

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.

공개 차단 목록 상태

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) 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 fingerprint

7d0e02dd9756abd0c2504af78034580e45ea6bca06813f30684e961c2902805f

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.91 rapiddns.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

Cloudflare

CDN

HTTP/3

Miscellaneous

Detected via Cloudflare Radar · Wappalyzer engine

이 도메인 신고하기 증거를 제출하고 다른 사람들을 보호하는 데 힘을 보태주세요

VirusTotal 분석

12 / 91 보안 공급업체가 이 도메인에 플래그를 지정했습니다.

View on VT

Last analyzed 2026-08-21 02:52:17 UTC First positive detection 2026-08-18 19:40:07 UTC 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

Good

Performance

FCP

0.93s

First Contentful Paint

LCP

0.93s

Largest Contentful Paint

CLS

Cumulative Layout Shift

TBT

0ms

Total Blocking Time

3.83s

Speed Index

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: 2027-08-12 23:59:59 UTC
Registration observation: 2026-10-16 03:47:24 UTC
Registration source: rdap_status_collector

Availability observations

Last reachable observation: 2026-08-19 22:15:41 UTC
Outcome first observed: 2026-08-20 00:54:05 UTC
Observation window starts: 2026-08-19 22:15:41 UTC
Observation window ends: 2026-08-20 00:54:05 UTC
Estimated change time: 2026-08-19 23:34:53 UTC
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.

탐지 회피 분석

클로킹 및 트래픽 분산 점검

아직 스캔되지 않았습니다 크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다. 2026-10-17 00:57:52 UTC

이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.

저장된 은신 플래그: 아직 스캔되지 않았습니다
마지막 은폐 스캔: 2026-10-17 00:57:52 UTC

스캐너 메모: 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개와 브라우저 및 크롤러 응답을 비교합니다. 버튼을 눌러야 새 검사가 시작됩니다.

요청 시 실행

저장된 실시간 검사 결과가 없습니다.

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.

Domain Status Transition 2026-09-07 02:31:00 UTC
Source: PhishDestroy monitoring
Event details
Domain state transitioned from alive to dead.
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.
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.
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.

2026-10-16 11:00:13 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-16 03:47:24 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-16 02:45:31 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-15 20:22:19 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-15 10:48:32 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive

Earlier observations 70

2026-10-15 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-15 02:32:34 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-14 20:21:26 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-14 10:50:20 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-14 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-14 02:38:46 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-13 20:21:07 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-12 22:57:19 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-12 20:20:57 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-12 11:01:33 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-12 03:47:24 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-11 23:04:35 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-11 20:20:50 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-11 10:45:34 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-11 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-10 22:49:22 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-10 20:20:48 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-10 10:49:48 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-10 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-09 22:50:28 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-09 20:20:42 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-09 10:50:25 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-09 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-09 02:49:19 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-10-08 20:20:32 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-07 10:01:57 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-07 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-06 22:59:03 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

origin_unreachable · http_5xx
2026-10-06 22:13:39 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-06 10:58:26 UTC
Availability monitor · Recorded state
held→알 수 없음

origin_unreachable · http_5xx
2026-10-06 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-05 22:59:09 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

origin_unreachable · http_5xx
2026-10-05 22:13:39 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-10-05 03:47:26 UTC
Availability monitor · Recorded state
dns_inactive→held

registry_server_hold · server_hold
2026-10-04 22:13:35 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-10-04 03:47:28 UTC
Availability monitor · Recorded state
dns_inactive→held

registry_server_hold · server_hold
2026-10-03 16:16:30 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-03 11:06:06 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-10-03 03:47:27 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-02 22:50:36 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

origin_unreachable · http_5xx
2026-10-02 16:16:28 UTC
Availability monitor · Recorded state
알 수 없음→dns_inactive

dns_nxdomain
2026-10-02 10:52:10 UTC
Availability monitor · Recorded state
held→알 수 없음

origin_unreachable · http_5xx
2026-10-02 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-02 02:36:47 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

origin_unreachable · http_5xx
2026-10-01 16:16:25 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-10-01 03:47:27 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-10-01 02:05:23 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

origin_unreachable · http_5xx
2026-09-30 16:14:55 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-30 03:47:27 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-30 02:30:57 UTC
Availability monitor · Recorded state
held→알 수 없음

probe_inconclusive
2026-09-29 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-29 02:45:37 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-09-28 15:52:31 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-28 03:47:26 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-28 02:31:11 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-09-27 15:50:45 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-27 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-27 02:46:49 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-09-26 15:50:39 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-26 03:47:24 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-26 02:30:51 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-09-25 15:49:06 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-25 03:47:25 UTC
Availability monitor · Recorded state
알 수 없음→held

registry_server_hold · server_hold
2026-09-25 02:45:49 UTC
Availability monitor · Recorded state
dns_inactive→알 수 없음

probe_inconclusive
2026-09-24 05:51:28 UTC
Availability monitor · Recorded state
held→dns_inactive

dns_nxdomain
2026-09-24 03:47:29 UTC
Availability monitor · Recorded state
held

registry_server_hold · server_hold
2026-09-07 02:31:00 UTC
Availability monitor · Recorded state
접속 가능→이용 불가
2026-08-21 02:52:17 UTC
VirusTotal · Detection count
11→12
2026-08-19 01:43:47 UTC
VirusTotal · Detection count
11→11
2026-08-18 19:34:24 UTC
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.

Google Safe Browsing Transparency Report

Check whether Google currently lists the URL as unsafe.

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.

웨이백 머신 Historical evidence

Compare archived captures and preserve historical context.

abuse.ch ThreatFox IOC correlation

Look for matching indicators and associated threat records.

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

Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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

커뮤니티 인텔리전스

커뮤니티 신고 1건

범주PHISHING

Blacklist from Phishfort

증거 및 외부 보고서

증권 분석

URLScan Analyzed VirusTotal 12 det. 체인패트롤 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 2026-10-17 01:12:09 UTC

Flagged by PhishFort Detection System on Nov 8, 2022 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).

제출된 증거 스냅샷

Sent: 2026-08-18 20:35:43 UTC Ledger records: 1 Case ID: PD-20260818-65C2EB Recipient: abuse@gen.xyz

Page title stored with report: 年会盛典 · 幸运抽奖

URLScan evidence VirusTotal evidence URLQuery evidence Screenshot 776.4 KB

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

이 사이트로 인해 영향을 받으셨나요?

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

FBI IC3

미국의 인터넷 기반 범죄 신고

Federal tips line1-800-CALL-FBI

Report online

유로폴

EU 국가의 공식 신고 채널 찾기

National police directory

Find your country

액션 프라우드

잉글랜드, 웨일스, 북아일랜드에서 사기 및 사이버 범죄 신고

Contact centre0300 123 2040

Report online

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.

모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
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·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — 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 response FBI IC3 · reports & evidence FTC · recovery scams

모든 도메인 확인

저장된 차단 목록, WHOIS, DNS 및 공개 스캔 증거를 사용한 위협 분석

지금 스캔하기

피싱 신고

의심스러운 도메인을 당사의 위협 데이터베이스에 신고해 주세요 — 커뮤니티를 보호해 주세요

보고서

실시간 위협 정보

최근 피싱 보고서 및 관찰된 가용성 변경 사항

모니터링

이 보고서 정보: 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.

이 목록이 정확하지 않다고 생각되면 항소를 제출하다. 당사의 방법론에 대해 알아보려면 FAQ 페이지를 방문하세요.

HTML · IFRAME

이 보고서 삽입하기

이 위협 정보를 귀하의 웹사이트나 블로그에 공유하세요

embed.html

<iframe
  src="https://phishdestroy.io/ko/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>

bscbox.xyz

Additional indicators at a glance

Source evidence

VirusTotal

URLQuery

Spamhaus DBL

OTX

CF 레이더

URLScan capture

URLScan verdict

Google Safe Browsing

Public blocklists

증거 요약

Assessment

Recorded Evidence

Interpretation

Recommended Actions

공개 차단 목록 상태

Domain details

인증 및 RAA 상황

Registrar accreditation and DNS abuse obligations

Network & certificates

네임서버 2

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

VirusTotal 분석

Registration evidence

Availability observations

클로킹 및 트래픽 분산 점검

Forensic History & Detection Timeline

위협 대응 Pipeline

Public scans, evidence and abuse channels

관련 인프라 및 보고서

공유 Cloudflare 에지에 대한 기타 보고서 1

동일 등록기관: NiceNIC 6

최근 위협 보고서 6

커뮤니티 인텔리전스

증거 및 외부 보고서

이 사이트로 인해 영향을 받으셨나요?

Official reporting routes

지역 당국에 신고하십시오

피해자를 위한 권고 사항 및 조언

모든 도메인 확인

피싱 신고

실시간 위협 정보

최신 정보를 확인하고, 안전을 지키세요