VirusTotal
14 / 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.
フィッシング: vcb325df.christmas — 未検証. 証拠の概要: VirusTotal 14/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLScan malicious verdict; CF…
元のフォレンジック記録を保持するため、下の 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.
PhishDestroy threat report
On July 28, 2026, analysis of the domain vcb325df.christmas confirms that it is actively being used in a generic phishing campaign. The domain was registered on July 26, 2026 through the registrar Spaceship, Inc. and delegated to the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to the IPv4 address 47.242.217.10, indicating a single‑host hosting model. The domain appears on one public security blocklist and has been flagged by the PhishDestroy filtering service, confirming that it is already recognized by at least one anti‑phishing platform. VirusTotal reports that one of ninety‑one scanned security vendors has issued a detection for the domain, providing an early indicator of malicious activity despite the limited coverage.
No additional intelligence such as SSL certificate details, HTTP response codes, Safe Browsing status, or content analysis is currently available, leaving the exact content and lure technique of the site undefined. Because no SSL/TLS certificate information has been observed, it is unclear whether the site encrypts traffic, which may affect detection at TLS inspection points. Likewise, the HTTP response status and page title have not been disclosed, preventing verification of any brand impersonation or credential‑capture tactics. The lack of further public observations suggests that the campaign may be in an early stage or that the infrastructure is intentionally low‑profile. Given the recent registration date, the high‑risk classification, and the presence on a blocklist, defenders should proactively block the domain at network perimeter devices and update DNS filtering policies.
Monitoring of the associated IP address 47.242.217.10 for anomalous traffic patterns is also advised, as is the inclusion of the domain in sandbox and email gateway rule sets.
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.
vcb325df.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 sourcePD-20260728-AD515B
No threat flag
View sourcePage captured
View sourcevcb325df.christmas
View sourcePD-20260728-AD515B 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 ↗
vcb325df.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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.