VirusTotal
14 / 89 engine detections
보고서 열기“bn56gfh.christmas”
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.
bn56gfh.christmas — 확인되지 않음. 사기 유형: Impersonation. 증거 요약: VirusTotal 14/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLScan malicious verdict; CF Radar malicious; PhishDestroy score 98/100. 등록기관: Spaceship.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
14 / 89 engine detections
보고서 열기악성
보고서 열기악성
보고서 열기checked — no detections recorded
보고서 열기4 community references
보고서 열기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 bn56gfh.christmas was registered on July 17, 2026 through Spaceship, Inc. and is currently resolving to the IPv4 address 47.242.217.10. Its authoritative nameservers are launch1.spaceship.net and launch2.spaceship.net. As of the report date, July 28, 2026, the site remains active and is listed as under investigation for generic phishing activity. The domain has been added to at least one security blocklist and is actively blocked by the PhishDestroy mitigation service, indicating that threat‑intel feeds have already identified it as malicious.
VirusTotal records show that the domain was scanned by 91 AV vendors, none of which returned a malicious detection at the time of analysis; however, the absence of detections does not constitute confirmation of safety and should be treated as inconclusive. No public information on SSL certificates, HTTP response codes, page titles, or content has been disclosed, leaving the exact phishing payload and targeted brand unknown. The lack of visible page‑level indicators means that investigators cannot yet confirm the specific lure or credential‑harvesting mechanism employed.
Defenders should consider adding bn56gfh.christmas and its resolving IP address 47.242.217.10 to outbound and inbound filtering rules, monitor DNS queries for the domain, and keep the entry on blocklists such as PhishDestroy. Continuous re‑scanning on multi‑engine platforms is recommended to capture any later malicious changes, and any observed traffic should be logged for correlation with potential credential‑theft incidents. The domain’s recent creation date, active resolution, and existing blocklist presence collectively suggest a high likelihood of phishing intent despite the current lack of content‑level evidence.
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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
bn56gfh.christmas
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
이용 불가→접속 가능
접속 가능→이용 불가
접속 가능
4 community references
View source14/89 engine detections
View sourcePage captured
View sourcePD-20260728-EA1E67
No threat flag
View sourcebn56gfh.christmas
View sourcePD-20260728-EA1E67 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 ↗
bn56gfh.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.