VirusTotal
4 / 91
“Google”
Analysis indicates that the domain s2-quant.network has been taken offline and now returns HTTP 404 for all requests. The page title returned by the server is "Google", which aligns with the SSL certificate issued by Google Trust Services under the WE1 profile. The site was registered through Cloudflare, Inc., and its authoritative name servers are brenna.ns.cloudflare.com and hassan.ns.cloudflare.com. Traffic for the domain resolves to IP address 142.251.40.164, an address owned by Google LLC (AS15169) located in the United States.
The HTTP stack advertises Cloudflare edge services and HTTP/3 support, suggesting that the infrastructure was leveraged to hide malicious hosting behind a reputable CDN. The domain is flagged as a Gmail impersonation, matching the "brand target" field, and was blocked by the PhishDestroy blocklist. VirusTotal scans show that 2 of 95 security vendors recorded detections, and the domain appears on one additional security blocklist. The SSL certificate, while legitimate for Google, does not guarantee the content of the site and may have been obtained through the registrar's default certificate provisioning.
The combination of legitimate cloud infrastructure, a generic "Google" page title, and limited vendor detections suggests a low‑volume, targeted impersonation campaign that has been disrupted. Defenders should continue to monitor DNS queries for the IP 142.251.40.164 and related Cloudflare name servers for any resurgence, enforce strict SPF/DKIM/DMARC checking for Gmail traffic, and ensure that URL filtering solutions block any resolved endpoints associated with s2-quant.network. Given the offline status, immediate remediation is limited to updating blocklists and verifying that no cached copies remain in internal proxies.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://s2-quant.network/; server=cloudflare
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.
brenna.ns.cloudflare.comhassan.ns.cloudflare.comLocation describes the IP network.
9a2a551cafdceca877ea0e1934f3b3ab7f00bff053b7397eafce1828abdffa7aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
18 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 24, 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