VirusTotal
14 / 91 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.
フィッシング: dfvvg.christmas — 未検証. 証拠の概要: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1 alert; URLScan malicious verdict…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 91 engine detections
レポートを開く1 threat-system alert
レポートを開く悪意あり
レポートを開く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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | dfvvg.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis as of July 28, 2026 indicates that the domain dfvvg.christmas was registered on June 18, 2026 through the registrar Spaceship, Inc. The domain uses the authoritative name servers launch1.spaceship.net and launch2.spaceship.net, both associated with the same registrar. DNS resolution points to the IPv4 address 47.242.217.10, which remains active at the time of assessment. VirusTotal has recorded detections from seven of ninety‑one scanned security vendors, confirming that multiple detection engines flag the domain as malicious. The domain appears on a single security blocklist and is actively blocked by the PhishDestroy service, reinforcing its classification as a high‑risk phishing infrastructure.
The current operational status is listed as active, and no evidence of takedown or remediation has been observed. The available data do not include SSL certificate details, HTTP response codes, page title, or any observed payloads, leaving the exact phishing landing page content unverified. Consequently, the specific phishing campaign vector, target brand, or credential‑harvesting technique cannot be confirmed at this stage.
Defenders should treat the domain as hostile, enforce network‑level deny rules for the IP address 47.242.217.10, and incorporate the domain into URL filtering and email security policies. Monitoring of the associated name servers and blocklist status is recommended to detect any future changes in hosting or mitigation actions. Given the recent registration date and multiple vendor detections, the domain poses a high likelihood of being used in credential‑stealing operations targeting unsuspecting users.
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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能
14/91 engine detections
View source4 community references
View sourcePD-20260728-E849E0
No threat flag
View sourcePage captured
View sourcedfvvg.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dfvvg.christmas
PD-20260728-E849E0 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 ↗
dfvvg.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.