URLScan verdict
malicious
ReportInterpretation & limits
This is the recorded automated analysis. Completion alone is not a safety verdict.
“Official Online Shop | Billionaire Boys Club”
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.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
checked — no detections recorded
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
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.
bbcicecreamarchive.shop returned an HTTP status 200 on 2026-10-12, documenting a successful response at that time. The domain was also observed in the PhishDestroy internal listing, which is a publisher-owned catalogue entry.
On 2026-10-12, the HTTP status source recorded a 200 response for bbcicecreamarchive.shop. The PhishDestroy internal listing included this domain as of the same date. VirusTotal checked bbcicecreamarchive.shop on 2026-10-11, reporting 0 detections out of 92 total scanners. OTX pulses referenced the domain four times as of 2026-10-12.
The PhishDestroy internal listing contains a record of bbcicecreamarchive.shop, which documents its inclusion in a publisher-managed catalogue. VirusTotal provides a measurement of detections across multiple scanners, offering a perspective on how the domain was assessed by external security tools. The OTX pulses record the domain's appearance in threat intelligence entries, reflecting its presence in external security discussions. These sources together offer a multi-faceted view of the domain's recorded status and technical context.
For bbcicecreamarchive.shop, preserve the HTTP status, PhishDestroy internal listing, and VirusTotal records for future reference. Compare OTX pulse entries and VirusTotal scanner results over time to monitor for any changes in external security intelligence.
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.
ns2.dyna-ns.netLocation describes the IP network.
cee6509ff3fa459e0f13daac4e0b033eeaa6b011684883c3f4111ef00d538678Saved 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 bbcicecreamarchive.shop · checked Oct 12, 2026
194.26.231.102.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