Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
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; 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.
Dga domains Security threats Security Risks DGA Domains New Domains
SSL CertificateInvalid
SSL certificate is invalid or expired. Issuer:
Evidence Summary
Critical
VirusTotal
14/89
OTX
4 community refs
URLScan
Stored capture
The domain bn56gfh.christmas was registered on July 17, 2026 through Spaceship, Inc. and is currently resolving to the IPv4 address 47.242.217.10. Its authoritative nameservers are launch1.spaceship.net and launch2.spaceship.net. As of the report date, July 28, 2026, the site remains active and is listed as under investigation for generic phishing activity. The domain has been added to at least one security blocklist and is actively blocked by the PhishDestroy mitigation service, indicating that threat‑intel feeds have already identified it as malicious.
VirusTotal records show that the domain was scanned by 91 AV vendors, none of which returned a malicious detection at the time of analysis; however, the absence of detections does not constitute confirmation of safety and should be treated as inconclusive. No public information on SSL certificates, HTTP response codes, page titles, or content has been disclosed, leaving the exact phishing payload and targeted brand unknown. The lack of visible page‑level indicators means that investigators cannot yet confirm the specific lure or credential‑harvesting mechanism employed.
Defenders should consider adding bn56gfh.christmas and its resolving IP address 47.242.217.10 to outbound and inbound filtering rules, monitor DNS queries for the domain, and keep the entry on blocklists such as PhishDestroy. Continuous re‑scanning on multi‑engine platforms is recommended to capture any later malicious changes, and any observed traffic should be logged for correlation with potential credential‑theft incidents. The domain’s recent creation date, active resolution, and existing blocklist presence collectively suggest a high likelihood of phishing intent despite the current lack of content‑level evidence.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bn56gfh.christmas', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
DOM Analysisanalyzed Jul 28, 2026score 98/1001 brand signal
Submitted URLhttp://bn56gfh.christmas/
Favicon Hash
Case ID
ICANN OVERSIGHT
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.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 10:26:26 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:17:51 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-08-08 22:14:47 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-08-08 10:10:49 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-07-28 00:30:52 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 47.242.217.10.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
bn56gfh.christmas detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · bn56gfh.christmas
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
