VirusTotal
14 / 91 engine detections
Mở báo cáo“首页”
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.
Lừa đảo: bv7ghbv.christmas — Chưa được xác minh. Tóm tắt bằng chứng: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
14 / 91 engine detections
Mở báo cáoĐộc hại
Mở báo cáochecked — no detections recorded
Mở báo cáo4 community references
Mở báo cáoprovider verdict: clean
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis indicates that bv7ghbv.christmas was registered on July 16, 2026 through the registrar Spaceship, Inc., using the authoritative nameservers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points exclusively to the IPv4 address 47.242.217.10. The domain appears on a single security blocklist and is actively blocked by the PhishDestroy feed, confirming that it is being treated as malicious by at least one reputable anti‑phishing service. VirusTotal records show the domain was submitted to 91 scanning engines, none of which returned a detection; this absence of detections does not imply safety and should be interpreted as a lack of current signatures. The only publicly available intelligence is the registration metadata and the blocklist inclusion; no page content, brand targeting, or payload details have been released, leaving the specific phishing vector and victim profile uncertain. Defenders should add bv7ghbv.christmas to outbound URL filtering rules, enforce DNS sinkholing for the associated IP address, and monitor for any new sightings in threat‑intel feeds. Continuous re‑evaluation is advised as additional evidence, such as page screenshots or malware samples, becomes available.
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.
bv7ghbv.christmas
4 community references
View source14/91 engine detections
View sourcePD-20260720-917642
No threat flag
View sourcebv7ghbv.christmas
View sourcePage captured
View sourcePD-20260720-917642 Recipient: abuse@spaceship.com Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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 ↗
bv7ghbv.christmas)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.