koinbaze-pro-logg[.]godaddysites[.]com

Analysis identifies koinbaze-pro-logg.godaddysites.com as infrastructure associated with the generic_phishing threat category. The domain currently has a high risk assessment and is presently offline or taken offline. Historical intelligence indicates that the domain was used within a phishing context and was subsequently blocked by multiple security organizations. The current page title returns "404 Not Found," indicating that the content has been removed, disabled, or otherwise made inaccessible. Despite its offline status, previously observed indicators continue to justify classification as malicious infrastructure.

Technical analysis reveals that the domain was created on February 21, 2026 and registered through GoDaddy.com, LLC. DNS resolution data associates the domain with IP address 76.223.105.230, located in the United States within AS16509 Amazon.com, Inc. The deployed SSL certificate was issued by GoDaddy.com, Inc. through the Go Daddy Secure Certificate Authority - G2 hierarchy. Security telemetry shows that the domain was flagged by 17 of 95 VirusTotal vendors. Google Safe Browsing classified the domain as phishing, while intelligence sources indicate that it appears on 3 security blocklists. Additional blocking actions were recorded by PhishDestroy, MetaMask, and SEAL. The combination of recent domain registration, phishing classification, multiple vendor detections, and blocklist presence supports the assigned high-risk rating.

Current observations indicate that the domain has been taken offline and no active phishing content is presently accessible. However, historical indicators demonstrate prior malicious use and justify continued defensive measures. Security teams should retain the domain within blocklists and monitoring systems to detect possible reactivation or infrastructure reuse. Network administrators should review historical logs for connections to 76.223.105.230 and investigate any authentication events, credential submissions, or user interactions involving the domain. End users should avoid visiting the domain, entering credentials, or trusting communications that reference it. Continued monitoring of associated infrastructure, registration changes, and future DNS activity is recommended because phishing operators frequently recycle domains or redeploy related assets after takedown events.