VirusTotal
15 / 89 engine detections
Відкрити звіт“cv34f3d.christmas”
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.
фішинг: cv34f3d.christmas — Неперевірений. Зведення доказів: VirusTotal 15/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLQuery 1 alert; URLScan…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
15 / 89 engine detections
Відкрити звіт1 threat-system alert
Відкрити звітШкідливий
Відкрити звітШкідливий
Відкрити звіт4 community references
Відкрити звіт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 | cv34f3d.christmas |
malicious | Sinkholed |
PhishDestroy threat report
On July 28, 2026, analysis of the domain cv34f3d.christmas identified an active generic phishing infrastructure. The domain was registered on July 18, 2026 through Spaceship, Inc., using the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to the IPv4 address 47.242.217.10, which remains reachable as of the report date. The domain is listed on one public security blocklist and has been blocked by the PhishDestroy sinkhole, indicating that at least one defensive platform has observed malicious traffic associated with the host.
VirusTotal records show that the domain was scanned by 91 antivirus and URL‑analysis engines, none of which have raised a detection at the time of scanning. While the lack of detections does not imply benign intent, it confirms that the domain has not yet triggered automated signatures in the examined vendor set. No additional intelligence such as Safe Browsing verdicts, Open Threat Exchange references, SSL certificate details, HTTP response codes, or trust‑score metrics were available for this host. Given the recent creation date, the presence on a blocklist, and active resolution to a public IP, the infrastructure is likely being used to host phishing pages or to relay malicious traffic.
Defenders should add cv34f3d.christmas to URL filtering rules, monitor DNS queries for the two launch*.spaceship.net name servers, and consider network‑level blocking of the associated IP address. Continuous re‑scanning with multi‑engine services is recommended to capture any future changes in detection status. Incident response teams should treat any communications originating from this domain as suspicious and verify user credentials through out‑of‑band channels before proceeding.
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.
cv34f3d.christmas
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Доступний
4 community references
View source15/89 engine detections
View sourcePD-20260728-6D0446
No threat flag
View sourcecv34f3d.christmas
View sourcePage captured
View sourcePD-20260728-6D0446 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 ↗
cv34f3d.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.