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.
фішинг: mulus.christmas — Неперевірений. Зведення доказів: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 3 alerts; URLScan…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
14 / 91 engine detections
Відкрити звіт3 threat-system alerts
Відкрити звітШкідливий
Відкрити звіт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 |
|---|---|---|---|
| OpenDNS | mulus.christmas |
phishing | Phishing Block |
| Hagezi Threat Feed | mulus.christmas |
malicious | Sinkholed |
| DNS4EU | mulus.christmas |
malicious | Sinkholed |
PhishDestroy threat report
The domain mulus.christmas was registered on July 8 2026 through Spaceship, Inc. and is currently active, resolving to the IPv4 address 47.242.217.10. Its authoritative name servers are launch1.spaceship.net and launch2.spaceship.net. Infrastructure analysis shows a fresh registration and a single‑point hosting configuration typical of short‑lived phishing infrastructure. The threat classification is generic_phishing, and the domain is listed as under investigation with an active status. No public page content, email samples, or victim reports have been disclosed, so the exact phishing lure, targeted brand, or payload remains unknown. Defenders should treat the domain as potentially malicious, incorporate the IP and domain into blocklists, monitor DNS queries for the associated name servers, and consider sink‑hole or traffic analysis if connections are observed. Ongoing observation of any future resolution changes, hosting modifications, or emergence of related indicators is recommended to refine the risk assessment.
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 source14/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcePD-20260715-D733E7
mulus.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
mulus.christmas
PD-20260715-D733E7 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 ↗
mulus.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.