VirusTotal
11 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-contact@sav.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
11 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | comzkdsyrdweb.coinbasegive.com |
malicious | Sinkholed |
| Quad9 DNS | comzkdsyrdweb.coinbasegive.com |
malicious | Sinkholed |
| Cloudflare DNS | comzkdsyrdweb.coinbasegive.com |
malicious | Sinkholed |
| DNS4EU | comzkdsyrdweb.coinbasegive.com |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
comzkdsyrdweb.coinbasegive.com returned HTTP status 200 on 2026-10-01, per the recorded HTTP check. The same domain appears on two external blocklists, MetaMask and SEAL, and carries a phishdestroy internal listing.
The HTTP check on 2026-10-01 recorded status 200 for comzkdsyrdweb.coinbasegive.com. The domain was first observed on 2026-09-01. VirusTotal reported 11 detections across 89 scanners on 2026-09-15. The blocklist check on 2026-10-01 recorded external listings on MetaMask and SEAL. The recorded IP address 76.223.54.146 sits in the US under AWS Global Accelerator (GLOBAL).
The HTTP 200 response describes only the status returned on the check date, not the content served or present availability. The MetaMask and SEAL listings and the VirusTotal detection count are separate source observations, each with its own measurement context. The first observation date and the later check dates give a sequence for ordering records, while the differing dates alone do not show a change.
For comzkdsyrdweb.coinbasegive.com, preserve the HTTP check record and the external blocklist entries for later comparison. Compare the VirusTotal detection record against the blocklist records in separate reviews. Order the retained observations by their recorded dates when reviewing them.
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='comzkdsyrdweb.coinbasegive.com', port=80): Max retries exceeded with url: / (Caused by New
ns1.afternic.comns2.afternic.comLocation describes the IP network.
76.223.54.146.14 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
4 community reports
CategoryPHISHING
Blacklist from EtherAddressLookup Database
“Blacklist from EtherAddressLookup Database”
PD-20260901-91AE55 Recipient: abuse-contact@sav.com 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.
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