VirusTotal
15 / 91 engine detections
Mở báo cáo“首页”
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; 3 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.
Analysis of vbfyyu.christmas shows a newly registered domain (creation date 14 July 2026) hosted by Spaceship, Inc.
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
15 / 91 engine detections
Mở báo cáo3 threat-system alerts
Mở báo cáoĐộc hại
Mở báo cáoĐộc hại
Mở báo cáo4 community references
Mở báo cáo80/100
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | vbfyyu.christmas |
phishing | Phishing Block |
| Hagezi Threat Feed | vbfyyu.christmas |
malicious | Sinkholed |
| DNS4EU | vbfyyu.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of vbfyyu.christmas shows a newly registered domain (creation date 14 July 2026) hosted by Spaceship, Inc. The domain resolves to the IPv4 address 47.242.217.10 and uses the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. VirusTotal reports that two of ninety‑one scanning engines have flagged the domain, indicating a non‑trivial detection rate for malicious activity. The classification in the repository is generic_phishing, and the domain is currently listed as active. No public web content, page title, or targeted brand information has been released, so the specific phishing lure cannot be confirmed. Infrastructure reuse cannot be assessed because the IP address and name servers have not been previously linked to known malicious campaigns. Defenders should treat the domain as high‑risk: block DNS resolution for vbfyyu.christmas, add the IP 47.242.217.10 to network‑level deny lists, and monitor for any outbound connections to that address. Continuous re‑scanning on multi‑engine platforms is advised to capture any emerging detections, and any observed traffic should be logged for correlation with credential‑theft attempts. Until further payload or landing‑page analysis becomes available, the safest posture is to assume the domain is being used to deliver phishing content.
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 source15/91 engine detections
View sourcePD-20260717-B31EDE
Page captured
View sourceNo threat flag
View sourcevbfyyu.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
vbfyyu.christmas
PD-20260717-B31EDE Recipient: abuse@spaceship.com Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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 ↗
vbfyyu.christmas)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.