VirusTotal
15 / 91
“Crypto Blizt”
coinbasecryptoblizt.digital was observed resolving to the Amazon Web Services address 63.176.8.218 located in Germany (AS16509). The domain is registered through Name.com, Inc., and uses the DNS infrastructure of NS1 (dns1.p04.nsone.net through dns4.p04.nsone.net). A DigiCert Global G2 TLS RSA SHA256 2020 CA1 certificate is presented, indicating a valid TLS chain but offering no credibility for the content. The site returned HTTP 404, and the page title reported by scanners is “Crypto Blizt”, which aligns with the classified scam type “Crypto Scam”.
Google Safe Browsing flagged the domain for social engineering, and 13 of 95 VirusTotal scanners labeled it malicious, suggesting a consensus among security vendors that the site is used for credential or asset theft. The domain impersonates Coinbase, a high‑value financial brand, and is listed on at least one public blocklist, with PhishDestroy confirming its takedown. Current status is offline, but the infrastructure—particularly the AWS‑hosted IP and the NSOne name servers—remains reusable for future campaigns.
Uncertainty remains regarding the exact payload or phishing page content, as only the HTTP 404 response and title have been captured. Defenders should continue to block the domain and associated IP, monitor the NSOne name servers for new subdomains, and update detection rules to flag any future resolutions to 63.176.8.218 that reference Coinbase or cryptocurrency‑related keywords. Incident response teams should also consider hunting for artifacts of credential harvesting attempts that may have been directed at Coinbase users during the brief live window.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='coinbasecryptoblizt.digital', port=80): Max retries exceeded with url: / (Caused by NewCon
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.
Edge-IP reputation is not attributed to this domain.
dns4.p04.nsone.netLocation describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
255 stored lookalike domains
Showing 100 of 255
Reported by 1 community member, first seen Sep 10, 2025
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive