VirusTotal
13 / 91 engine detections
Buka laporan“首页”
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.
Phishing: cbvdf34d.christmas — Belum terverifikasi. Ringkasan bukti: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
13 / 91 engine detections
Buka laporanBerbahaya
Buka laporanBerbahaya
Buka laporanchecked — no detections recorded
Buka laporan4 community references
Buka laporanNo threat flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, cbvdf34d.christmas, was registered on July 16 2026 using the registrar Spaceship, Inc. The authoritative name servers are launch1.spaceship.net and launch2.spaceship.net, and DNS resolution points to the IPv4 address 47.242.217.10. The domain is currently listed as active and classified as a generic phishing threat. It has been added to one public security blocklist and is blocked by the PhishDestroy sinkhole. A VirusTotal scan involving 95 anti‑malware engines currently shows no detections, but the absence of flags does not confirm benign intent. Intelligence on the payload, landing page content, or targeted brands is not yet available. Defenders should proactively block the domain at perimeter firewalls and DNS resolvers, monitor outbound connections to 47.242.217.10, and consider adding it to internal blocklists. Ongoing investigation should focus on capturing the phishing page content, identifying any credential‑harvesting infrastructure, and correlating network traffic with known malicious activity.
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.
cbvdf34d.christmas
4 community references
View source13/91 engine detections
View sourcePD-20260720-DA9F8C
No threat flag
View sourcecbvdf34d.christmas
View sourcePage captured
View sourcePD-20260720-DA9F8C Recipient: abuse@spaceship.com Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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 ↗
cbvdf34d.christmas)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.