VirusTotal
16 / 89 engine detections
보고서 열기“首页”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
bvn56fg.christmas — 확인되지 않음. 사기 유형: Impersonation. 증거 요약: VirusTotal 16/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLScan malicious verdict; PhishDestroy score 98/100. 등록기관: Spaceship.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
16 / 89 engine detections
보고서 열기악성
보고서 열기checked — no detections recorded
보고서 열기4 community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
The domain bvn56fg.christmas has been observed in a single security blocklist and is actively denied by the PhishDestroy sinkhole. VirusTotal records show that the hostname was submitted to 91 scanning engines; none of the engines returned a malicious classification at the time of analysis. The absence of a positive detection does not constitute a guarantee of benign behavior, especially given the domain’s appearance on a known blocklist. No additional metadata such as registrar information, ASN, hosting IP, SSL certificate details, or HTTP response codes have been disclosed in the current intelligence set, leaving the underlying infrastructure largely opaque.
Consequently, threat actors could be leveraging the domain for credential harvesting, lure pages, or other phishing techniques without leaving typical forensic markers that would trigger automated alerts. Defensive teams should therefore treat bvn56fg.christmas as a suspicious indicator and enforce preventative controls. Recommended actions include adding the hostname to existing web‑filter or DNS‑block policies, monitoring outbound traffic for connections to the domain, and employing heuristic or reputation‑based detection rules that flag any attempted communication.
Continuous re‑query of reputation services such as VirusTotal, passive DNS, and additional blocklist feeds is advised to capture any future changes in classification. Organizations that employ email security gateways should also consider augmenting sender‑policy frameworks to reject messages that reference this domain, as phishing campaigns frequently combine malicious links with deceptive email content. Until further forensic evidence emerges, the domain should remain under active observation and be treated as a potential phishing vector.
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.
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.
launch1.spaceship.netlaunch2.spaceship.netLocation describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
4 community references
View source16/89 engine detections
View sourcePD-20260803-596917
Page captured
View sourceNo threat flag
View sourcebvn56fg.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bvn56fg.christmas
PD-20260803-596917 Recipient: abuse@spaceship.com 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
bvn56fg.christmas)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.