VirusTotal
4 / 91
“301 Moved Permanently”
bemawin.com returned HTTP status 301 on 2026-10-01, per the recorded HTTP check. The domain was first observed on 2026-09-15, and the PhishDestroy internal listing records it as present.
The HTTP check on 2026-10-01 recorded status 301 for bemawin.com. VirusTotal, checked on 2026-09-29, reported 4 detections across 91 scanners. OTX, checked on 2026-09-23, listed 4 pulses. The registration date is 2026-08-02, with Fewmoretaps OU d/b/a Trustname.com as registrar. The SSL certificate, scanned on 2026-09-21, was issued by Google Trust Services / WE1.
The HTTP 301 response indicates a permanent redirect, but it does not describe the content or destination of the redirect. The VirusTotal and OTX figures come from separate source observations made on their own dates, so they should not be merged into one verdict or trend. The PhishDestroy internal listing is a publisher-owned catalogue entry, distinct from those metrics.
For bemawin.com, preserve the HTTP check record, the VirusTotal result, and the OTX pulses as separate source documents for later comparison. Recheck the HTTP response and the source observations separately, and retain the registration and certificate details alongside the domain's other records.
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://bemawin.com/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
julissa.ns.cloudflare.comLocation describes the IP network.
ca72546406b8a2a134490bf8a11c12ea78495515dea1a852501ee3dc95ba8972Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 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.
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