VirusTotal
16 / 91 engine detections
Ouvrir le rapport“首页”
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.
Hameçonnage: dsfvjj.christmas — Non vérifié. Résumé des preuves: VirusTotal 16/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 3…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
16 / 91 engine detections
Ouvrir le rapport3 threat-system alerts
Ouvrir le rapportMalveillant
Ouvrir le rapport4 community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | dsfvjj.christmas |
phishing | Phishing Block |
| Hagezi Threat Feed | dsfvjj.christmas |
malicious | Sinkholed |
| DNS4EU | dsfvjj.christmas |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of the domain dsfvjj.christmas indicates that it was registered on 10 July 2026 through Spaceship, Inc. and is currently using the authoritative name servers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to the single IPv4 address 47.242.217.10, which remains active as of the report date (15 July 2026). The domain is classified as a generic_phishing site and its risk level is listed as under_investigation. No public web content, page titles, or brand references have been observed, and no sandbox or AV scans have been reported. Consequently, the exact lure or target brand cannot be confirmed at this time. The infrastructure—recent registration, use of a dedicated registrar, and a unique IP address—matches patterns seen in other short‑lived phishing campaigns that rely on rapid deployment and low‑cost hosting. Defenders should consider adding the domain and its resolving IP to block lists, monitor DNS queries for the name servers launch1.spaceship.net and launch2.spaceship.net for related activity, and, where possible, sinkhole traffic to prevent credential harvesting. Ongoing observation is advised to capture any future changes in content or additional indicators that could clarify the intended victim population.
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 source16/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcePD-20260715-90BC32
dsfvjj.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dsfvjj.christmas
PD-20260715-90BC32 Recipient: abuse@spaceship.com Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
dsfvjj.christmas)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.