VirusTotal
3 / 89
“Google”
On July 22, 2026 analysts examined ethereal-vote.finance, which was observed hosting a Google brand impersonation campaign. The domain resolved to 142.250.185.100, an address owned by AS15169 Google LLC in the United States, and employed Cloudflare’s network services, including HTTP/3 support. DNS records listed derek.ns.cloudflare.com and maleah.ns.cloudflare.com as authoritative nameservers, confirming registration through Cloudflare, Inc. The site presented a page title of "Google," aligning with the declared target brand, and presented a TLS certificate issued by Google Trust Services under the WE1 designation, suggesting an attempt to masquerade as a legitimate Google endpoint.
VirusTotal scans reported that two of ninety‑five security vendors flagged the domain, indicating partial detection of malicious activity. The domain appeared on a single external blocklist and was actively blocked by the PhishDestroy service, reinforcing its classification as a phishing infrastructure element. Current infrastructure status is offline, implying that the hosting or content has been taken down, though the underlying registration and DNS configuration remain intact.
Uncertainties remain regarding the specific phishing kit or payload used, as no page content beyond the title has been disclosed. Defenders should continue to monitor DNS queries for the domain and its associated IP address, enforce blocklist rules that already flag ethereal-vote.finance, and consider adding the domain to internal URL filtering policies. Additional scrutiny of outbound traffic to the IP may uncover residual command‑and‑control activity, and any future re‑registration of the domain should be treated as high‑risk given its prior abuse of Google branding.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ethereal-vote.finance', port=80): Read timed out. (read timeout=7)
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.
derek.ns.cloudflare.commaleah.ns.cloudflare.comLocation describes the IP network.
65225a488f7337e12afe0445fb51d30553c031bcd7e3cd55b5fb8b03793ff0b3Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
13 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.
Reported by 1 community member, first seen Nov 9, 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