VirusTotal
2 / 92
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Brew Watches | Brew Watch Co.”
Assessment based on the stored source evidence below. Review sources →
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.
2 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
beancase.shop was first observed on 2026-10-11, and a VirusTotal record from that date contains detection results for the domain. The domain is also referenced in the PhishDestroy internal listing, which documents its catalogue inclusion.
VirusTotal checked beancase.shop on 2026-10-11 and recorded 2 detections from 92 total scanners. OTX referenced the domain with 4 pulses as of 2026-10-12. The domain was added to the PhishDestroy internal listing, and its PageSpeed performance score was measured at 71 on 2026-10-12.
PhishDestroy documents catalogue inclusion, providing a publisher catalogue record for beancase.shop. VirusTotal contains detection counts from multiple scanners, which are technical measurements of the domain's presence in its database. The OTX record describes the domain's appearance in external intelligence pulses, offering a distinct type of reference. These source records allow for comparison of technical and intelligence observations across different dates.
For beancase.shop, retain the VirusTotal detection record and OTX pulse entry for ongoing review. Preserve the PhishDestroy internal listing as a reference for catalogue status. Use the PageSpeed performance score as a technical metric to compare infrastructure changes.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
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.
joel.ns.cloudflare.comLocation describes the IP network.
6a284f17b7b7215d49e9b051eb6ecb18ab8afa4ca8c5bfe5ecc9a9318576ea78Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of beancase.shop · checked Oct 12, 2026
193.162.133.218.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.
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