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; 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.
Security analysis of vbuuk.christmas covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
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áoĐộc hại
Mở báo cáochecked — no detections recorded
Mở báo cáo4 community references
Mở báo cáoprovider verdict: clean
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.
PhishDestroy threat report
The domain vbuuk.christmas was registered on July 15, 2026 through Spaceship, Inc. and is currently delegated to the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. DNS resolution returns the single IPv4 address 47.242.217.10, which is the only hosting endpoint observed for this indicator. Early intelligence classifies the site as a generic phishing operation and marks the risk level as under investigation while the status remains active. The domain appears on one public security blocklist and is explicitly blocked by the PhishDestroy filtering service, indicating that at least one downstream protection system has taken remedial action.
VirusTotal has processed the domain in 95 vendor scans, and none of the engines reported a detection at the time of analysis. The absence of detections does not constitute a safety guarantee; the lack of a positive flag may reflect limited coverage of the specific payload or evasion techniques. No additional public reputation sources, such as Safe Browsing or Open Threat Exchange, are cited in the current data set, and no SSL certificate details or HTTP response codes have been published. Because the only observable infrastructure consists of the registrar, name server pair, and the single IP address, defenders should consider immediate containment actions.
Blocking the domain name and the associated IP at perimeter firewalls, DNS resolvers, and endpoint protection tools will prevent accidental user access. Continuous monitoring of the name servers for changes, periodic re‑scanning on VirusTotal or equivalent platforms, and inclusion of the domain in internal blocklists are recommended until a definitive takedown or remediation is confirmed. Analysts should also watch for derivative domains that reuse the same registrar or hosting subnet, as the current infrastructure suggests a low‑cost, rapidly deployed phishing campaign.
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.
vbuuk.christmas
15/91 engine detections
View source4 community references
View sourcePD-20260722-454178
No threat flag
View sourcevbuuk.christmas
View sourcePage captured
View sourcePD-20260722-454178 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 ↗
vbuuk.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.