Notification and current-status evidence
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; 13 days 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.
bvn56fg[.]christmas
“首页”
The domain bvn56fg.christmas has been observed in a single security blocklist and is actively denied by the PhishDestroy sinkhole. VirusTotal records show that the hostname was submitted to 91 scanning engines; none of the engines returned a malicious classification at the time of analysis. The absence of a positive detection does not constitute a guarantee of benign behavior, especially given the domain’s appearance on a known blocklist. No additional metadata such as registrar information, ASN, hosting IP, SSL certificate details, or HTTP response codes have been disclosed in the current intelligence set, leaving the underlying infrastructure largely opaque.
Consequently, threat actors could be leveraging the domain for credential harvesting, lure pages, or other phishing techniques without leaving typical forensic markers that would trigger automated alerts. Defensive teams should therefore treat bvn56fg.christmas as a suspicious indicator and enforce preventative controls. Recommended actions include adding the hostname to existing web‑filter or DNS‑block policies, monitoring outbound traffic for connections to the domain, and employing heuristic or reputation‑based detection rules that flag any attempted communication.
Continuous re‑query of reputation services such as VirusTotal, passive DNS, and additional blocklist feeds is advised to capture any future changes in classification. Organizations that employ email security gateways should also consider augmenting sender‑policy frameworks to reject messages that reference this domain, as phishing campaigns frequently combine malicious links with deceptive email content. Until further forensic evidence emerges, the domain should remain under active observation and be treated as a potential phishing vector.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
VirusTotal Analysis
Evidence & External Reports
PD-20260803-596917 Recipient: abuse@spaceship.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive