VirusTotal
12 / 90
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Home, Outdoor, Tools & Everyday Essentials”
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.
12 / 90
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone 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.
broadbasketbay.shop returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-08-25, a separate dated observation in the evidence set.
The HTTP check on 2026-10-01 recorded status 403 for broadbasketbay.shop. VirusTotal, checked on 2026-09-06, reported 12 detections across 90 scanners. OTX, checked on 2026-08-30, listed 5 pulses. The domain appeared in the PhishDestroy internal listing, and its registrar was recorded as Sav.com, LLC. The SSL certificate, scanned on 2026-08-26, was issued by Google Trust Services / WE1. PageSpeed on 2026-08-25 recorded a performance score of 65.
These records describe different measurements taken on different dates, so they should be read as separate observations rather than a single combined signal. The HTTP response reflects only the recorded request on its date, not all content served by the domain. The VirusTotal and OTX entries come from independent sources with their own collection methods. The chronology shows the domain was observed before the HTTP check, but the dates alone do not establish a trend.
For broadbasketbay.shop, preserve the HTTP check record, the VirusTotal result, and the OTX pulses as separate source documents. Compare the HTTP response record against the PhishDestroy internal listing in a later review. Retain the PageSpeed and SSL scan records alongside the other observations for reference. Re-check the domain against the same sources and compare any new records with the preserved ones.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
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.
elly.ns.cloudflare.comroute1.mx.cloudflare.netpriority 10route2.mx.cloudflare.netpriority 26route3.mx.cloudflare.netpriority 76Location describes the IP network.
9e50b3a0de5b2ac00907f845b7a8a9122c9a2a3079a6983b84e012a79af3ef54Saved 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 broadbasketbay.shop · checked Aug 25, 2026
188.114.96.3.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