VirusTotal
15 / 89
On 2026-10-01, gambwix.com returned an HTTP status code 502 during a recorded check, indicating a specific server response at that time. The domain was first observed on 2026-07-30, and has been listed on several external and internal monitoring sources.
On 2026-10-01, an HTTP check recorded status 502 for gambwix.com. VirusTotal, as of 2026-09-13, reported 15 detections out of 89 scanners for this domain. OTX, checked on 2026-09-13, listed 3 pulses related to gambwix.com. The domain appeared on both the MetaMask and SEAL external blocklists as of 2026-10-01. It is also present on the PhishDestroy internal listing.
The evidence provides a timeline of distinct observations from several independent sources, each capturing a different aspect of gambwix.com. The HTTP status code documents a server response on one date, while VirusTotal and OTX reflect their own scanning and reporting activities on separate days. The inclusion on multiple blocklists and an internal listing highlights that gambwix.com has been noted by various monitoring entities, but each record stands on its own and covers different criteria.
For gambwix.com, retain the HTTP status, VirusTotal, OTX, and blocklist records for future reference and comparison. Evaluate each source's findings separately to monitor for any changes or new listings. Repeat checks using the same sources to track updates over time and to maintain a clear record of all observed evidence.
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='gambwix.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
lana.ns.cloudflare.comLocation describes the IP network.
12 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.
79 stored lookalike domains
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