VirusTotal
15 / 91 engine detections
Bericht öffnen“首页”
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.
Zugangsdaten-Phishing: cvbf56df.christmas — Nicht bestätigt. Zusammenfassung der Beweislage: VirusTotal 15/91 (alphaMountain.ai, BitDefender, Chong Lua Dao…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
15 / 91 engine detections
Bericht öffnen2 threat-system alerts
Bericht öffnenSchädlich
Bericht öffnen4 community references
Bericht öffnenprovider verdict: clean
Bericht öffnenNo threat flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain cvbf56df.christmas was registered on July 25, 2026 through Spaceship, Inc. and is currently resolved to the IPv4 address 47.242.217.10. DNS resolution is served by launch1.spaceship.net and launch2.spaceship.net, indicating the registrar’s default name‑server configuration. Within three days of creation the domain was observed by multiple security services: eight of ninety‑one VirusTotal scanners flagged it, and it appears on a single external blocklist. PhishDestroy has already listed the domain as blocked, confirming that at least one commercial mitigation service is actively preventing client access.
The domain’s risk rating is high, and its operational status remains active as of the report date, July 28, 2026. No additional infrastructure details such as SSL certificate metadata, HTTP response codes, page titles, or targeted brand identifiers are available in the current intelligence set, leaving the exact phishing payload and victim‑targeting tactics unknown. Defenders should immediately add cvbf56df.christmas and its resolving IP 47.242.217.10 to network‑level deny lists and endpoint web‑filtering rules.
Continuous monitoring of the associated name‑servers and blocklist reputation is advised, as the infrastructure could be reused for further credential‑harvesting campaigns. Organizations employing threat‑intel feeds should ensure that the domain is ingested from the existing blocklist and that any automated remediation actions trigger on the eight VirusTotal detections. Given the recent creation date and high‑risk classification, proactive blocking is recommended to prevent exposure before additional malicious content is observed.
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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Erreichbar
15/91 engine detections
View source4 community references
View sourcePD-20260728-4AE315
No threat flag
View sourcePage captured
View sourcecvbf56df.christmas
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
cvbf56df.christmas
PD-20260728-4AE315 Recipient: abuse@spaceship.com Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
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 ↗
cvbf56df.christmas)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
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
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.