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; 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.
Security analysis of vbkko.christmas covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
Докладний аналіз 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 | vbkko.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of vbkko.christmas, created on July 04, 2026 and registered through Spaceship, Inc., shows the domain is currently active and resolves to IP address 47.242.217.10, which geolocates to Hong Kong. The server returns HTTP 200 without an SSL certificate, indicating unencrypted traffic. The web stack is identified as Nginx hosting a Vue.js application, and the page title retrieved is "首页". VirusTotal reports that 16 of 91 security vendors have flagged the domain, demonstrating a moderate detection consensus across multiple scanners.
The domain is listed on a single external security blocklist and is actively blocked by the PhishDestroy service, reinforcing its malicious classification. Nameservers launch1.spaceship.net and launch2.spaceship.net are consistent with the registrar's infrastructure. While the available data confirm the presence of a phishing infrastructure, the specific payload, targeted brand, or credential‑stealing mechanisms have not been publicly disclosed, leaving the exact victim profile uncertain.
Defenders should immediately block vbkko.christmas and its resolved IP 47.242.217.10 at network perimeters, update URL filtering rules, and add the domain to internal threat‑intel feeds. Continuous monitoring of the IP and associated nameservers is advised, as well as periodic re‑scanning to detect any changes in hosting or content. Organizations using web filtering should ensure the domain is included in both reputation‑based and DNS‑based blocklists to mitigate exposure.
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.
vbkko.christmas
4 community references
View source14/91 engine detections
View sourceNo threat flag
View sourcePD-20260715-208936
vbkko.christmas
View sourcePage captured
View sourcePD-20260715-208936 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 ↗
vbkko.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.